Connect Message Routing Delays - for Connect users only

What to do

• Check whether your product depends on Inngest. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-08-27 16:03 UTC and 2026-08-26 00:31 UTC may need a replay.

• Subscribe to Inngest's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=inngest works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Inngest 1

1. resolvedAug 26, 2026, 12:31 AM UTC

   Between August 26 00:31 to 01:13 UTC, a subset of customers using Inngest Connect experienced delayed and failed function runs due to an internal networking issue that disrupted connectivity between Connect services. We reverted the change and restored service. Although Connect buffers worker responses, stalled internal API calls delayed acknowledgements and subsequent replies. In some cases, request forwarding failed even after a buffered response had been received. We fixed the root cause, improved Connect’s failure handling, and enhanced our internal observability so we can detect and respond more quickly to similar problems in the future. Affected customers should review failed Connect runs during the incident window and replay them after confirming that doing so is safe and idempotent.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.