rewindex

CompaniesInngestIncidents

Inngest: Connect Message Routing Delays - for Connect users only

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.inngest.com (opens in new tab)

Timeline of updates

  1. resolved

    Between August 24 at 23:38 UTC and August 25 at 00:08 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.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on status.inngest.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Inngest, started 2026-08-24 20:38 UTC, resolved after 0 min, 1 update(s).

Title
Connect Message Routing Delays - for Connect users only
Vendor
Inngest
Date
URL
https://rewindex.com/company/inngest/incidents/01M0V4X9VC2F65AQTFDDS419P8

Inngest profileRecent Inngest incidentsAll outages on August 24, 2026Inngest in August 2026MarkdownJSON