Inngest: Investigating Degraded Performance
Affected components: Function execution
Timeline of updates
- investigating
We are actively investigating degraded performance. We will provider further updates as we identify the cause and resolve the issue.
- investigatingEdited
We have recovered from degraded performance that occurred 11:45 - 11:48 AM PT. We are continuing to investigate.
- resolvedEdited
The incident is now resolved and the system is fully operational.
Changes Rewindex caught on this incident
- Incident updated: Investigating Degraded Performance
- Incident updated: Investigating Degraded Performance
- Incident silently edited: Investigating Degraded Performance
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 these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-09 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
048224f1fd57d5cf…Version 2 captured
In the 2026-11-09 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
9887409a6d5cd3da…Version 3 captured
In the 2026-11-09 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
6e06706cb73f8842…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
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-11-09 19:45 UTC, resolved after 25 min, 3 update(s); edited after publishing.
- Title
- Investigating Degraded Performance
- Vendor
- Inngest
- Date
- URL
- https://rewindex.com/company/inngest/incidents/01M70YQMVWY35JAVNFSTDG2VQ9
Inngest profileRecent Inngest incidentsAll outages on November 9, 2026Inngest in November 2026MarkdownJSON