Inngest: Delayed function executions for a subset of customers
Affected components: Function execution
Timeline of updates
- identified
We’re investigating execution slowness affecting a subset of customers, where steps may be delayed by a few seconds to a couple of minutes in the worst cases, caused by elevated memory usage on one of our shards.
- resolved
Execution latencies are back to normal across all customers, and the incident is now resolved.
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.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
1864e83d53409cf6…
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: minor) posted by Inngest, started 2026-08-19 02:10 UTC, resolved after 2.5 h, 2 update(s).
- Title
- Delayed function executions for a subset of customers
- Vendor
- Inngest
- Date
- URL
- https://rewindex.com/company/inngest/incidents/01M0C5WYW4C2F1E0A9TDXX60PR
Inngest profileRecent Inngest incidentsAll outages on August 19, 2026Inngest in August 2026MarkdownJSON