Inngest incident: Delayed observability of events

1. resolvedSep 26, 2026, 13:58 UTC

   The delay in events observability is now resolved and the system is fully operational.

2. identifiedSep 26, 2026, 13:39 UTC

   Events sent to Inngest are being accepted and processed for function execution normally, but are delayed for viewing by API or dashboard.

What APIStatus.watch saw

• Sep 26, 2026, 13:40 UTCoperational → degraded
• Sep 26, 2026, 14:00 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• OVHcloud: [US-EAST-VA][Storage] - Object Storage incident notificationMajor · Sep 25, 2026, 17:00 UTC
• Akamai: Increased latency during upstream provider maintenance in Singapore, Hong Kong, and JapanMinor · Sep 22, 2026, 00:30 UTC
• Akamai: Origin Server Connectivity Issues with Elevated Errors in APAC RegionMinor · Sep 22, 2026, 14:28 UTC
• Cloudflare: Cloudflare One Clients are incorrectly challenged on some sitesMinor · Sep 22, 2026, 19:23 UTC
• Cloudflare: Network Performance Degradation — Asia-PacificMinor · Sep 23, 2026, 18:42 UTC
• Twilio: SMS Delivery Delays from Twilio to Datora BrazilMinor · Sep 24, 2026, 08:36 UTC
• Twilio: SMS Delivery Receipt Delays from Twilio to MTN CameroonMinor · Sep 24, 2026, 11:13 UTC
• Zoom: Service Degradation Affecting Customer Using Polycom Devices Going OfflineMinor · Sep 25, 2026, 17:45 UTC
• Twilio: MMS Delivery Delays from a Subset of Twilio Long Codes to GCI United StatesMinor · Sep 26, 2026, 03:16 UTC
• Confluent Cloud: Elevated error rates in Azure East USMinor · Sep 26, 2026, 06:40 UTC

How often does Inngest have incidents?

Inngest reported 13 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 1h 37m. See Inngest's uptime and incident history