Dev APIs / Background jobs / Inngest

Inngest

OPERATIONAL

Since Apr 2026 · 25 incidents · status.inngest.com · checked just now

User reportsVisitors who said it's down for them, per hour over 24 hours. Not from the status page. Never counted in grades.
…
CompareAdd to stackStatus page
GradeBLast 90 days
BPRODA+SHIP

Overview

30d90d1y
Admitted uptimeCustomer time not hit, by the provider's own account. Regional and partial incidents count in part.
99.255%Grade B
IncidentsEverything posted on the status page except scheduled maintenance.
60 Sev 1
Fully downMost customers down, by the provider's own account.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
1h 54m
LongestLongest Sev 1–2 incident, start to resolved.
22h 00m
Since lastTime since the last counted incident was resolved.
4d 5h

By area

BProduction
5INCIDENTS
26h 08mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 30d
SEV 2Oct 10, 2026 · 1h 54mDegraded function execution
SEV 2Oct 9, 2026 · 1h 56mDegraded Function Execution
SEV 2Oct 11, 2026 · 22h 00m · some customersIntermittent Degraded Function Execution
17 in the last 6 months.
A+Shipping
0INCIDENTS
0mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 30dNothing.
2 in the last 6 months.
CleanSev 3–4Sev 1–2No data

Trend, last 12 months

24 in the last 6 months.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down5
Sev 3 · Can't shipCan't deploy, build or manage it0
Sev 4 · PapercutDocs, status page, slow dashboard1

When it breaks

Start times, last 12 months, UTC.

What breaks

No components named in the last 12 months.

Communication

Updates eachStatus page updates per incident, on average.
2.9Last 12 months
Update gapMedian time between status page updates during an incident.
45mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 18Sev 1–2

Incident history

Show all 25
Oct 20, 20260mSEV 2
Intermittent Event API Connectivity IssuesEvent API requests failed intermittently due to a downstream database provider's connectivity issues; the text does not say how many customers were hit.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE · BACK AFTER -65M
    Event API requests failed intermittently due to a downstream database provider's connectivity issues; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 13:07 UTC · identified
    We've identified intermittent errors affecting the Event API due to connectivity issues with a downstream database provider. We're investigating the issue.
  2. 13:12 UTC · monitoring
    The connectivity issues with our downstream database provider have subsided, and the Event API is operating normally again. We're continuing to monitor the service while investigating the root cause.
  3. 13:20 UTC · resolved
    The incident is now resolved and the system is fully operational.
Source
Oct 9–12, 20262d 4hSEV 2
Degraded Function Execution2 incidents
  1. Fri, Oct 9 21:33 UTC1h 56mSEV 2
    Degraded Function ExecutionFunction execution was degraded from about 21:05 to 21:49 UTC due to a network outage at Inngest's upstream datacenter provider, Rackspace. Connectivity was restored at 21:56 UTC and the team monitored recovery before resolving the incident.AI-graded
    Why this grade
    1. RULES · SEV 2
      Sev 2 from the incident title (no components listed)
    2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
      Function execution was degraded during an upstream datacenter network outage of about 45 minutes; the text does not say how many customers were hit.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
    4 updates
    1. 21:06 UTC · investigating
      We are actively investigating a network connectivity issue affecting function execution. We will provider further updates as we identify the cause and resolve the issue.
    2. 21:51 UTC · investigating
      We’re actively investigating a network connectivity issue with an upstream infrastructure provider that is affecting function execution. We will provider further updates as we identify the cause and resolve the issue
    3. 21:56 UTC · monitoring
      Connectivity with our upstream infrastructure provider has been restored. We’re monitoring function execution to confirm recovery.
    4. 23:29 UTC · resolved
      One of our datacenter providers, Rackspace, had a network outage from 2:05 pm Pacific to 2:49 pm Pacific (21:05 UTC to 21:49 UTC). This resulted in degraded performance. We apologize for the inconvenience. We're going to keep monitoring and update if anything changes
    Source
  2. Sun, Oct 11 04:26 UTC22h 00mSEV 2
    Intermittent Degraded Function ExecutionSome scheduled cron function runs were delayed or degraded for a subset of customers after database connection poolers ran out of capacity.AI-graded · some customers
    Why this grade
    1. RULES · SEV 2
      Sev 2 from the incident title (no components listed)
    2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
      Some scheduled cron function runs were delayed or degraded for a subset of customers after database connection poolers ran out of capacity.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
    3 updates
    1. 04:26 UTC · investigating
      We are actively investigating an issue with intermittent degraded execution of a subset cron functions. We will provide further updates as we identify the cause and resolve the issue.
    2. 05:30 UTC · monitoring
      Our new database connection poolers ran out of capacity today. We are rerouting traffic through multiple poolers that caused some latency spikes and delayed runs. We'll keep monitoring the system for any anomalies.
    3. 02:26 UTC · resolved
      The system has been operationally stable for the last 22 hours
    Source
Oct 10, 20261h 54mSEV 2
Degraded function executionFunction execution was degraded for an unspecified share of customers for about 1 hour 53 minutes; no components were listed.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Function execution was degraded for an unspecified share of customers for about 1 hour 53 minutes; no components were listed.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 15:45 UTC · investigating
    We are actively investigating an issue with function. We will provider further updates as we identify the cause and resolve the issue.
  2. 16:53 UTC · monitoring
    A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
  3. 17:38 UTC · resolved
    The incident is now resolved and the system is full operational.
Source
Sep 26, 202619mSEV 4
Delayed observability of eventsEvent viewing via API and dashboard was delayed for about 19 minutes; events were still accepted and processed normally.AI-graded
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE
    Event viewing via API and dashboard was delayed for about 19 minutes; events were still accepted and processed normally.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 13:39 UTC · identified
    Events sent to Inngest are being accepted and processed for function execution normally, but are delayed for viewing by API or dashboard.
  2. 13:58 UTC · resolved
    The delay in events observability is now resolved and the system is fully operational.
Source
Sep 26, 202618mSEV 2
Delays with function executionFunction execution was delayed for an unspecified share of users for about 19 minutes before the provider marked it resolved.AI-graded
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    Function execution was delayed for an unspecified share of users for about 19 minutes before the provider marked it resolved.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 06:01 UTC · investigating
    We are actively investigating an issue with function execution. We will provider further updates as we identify the cause and resolve the issue.
  2. 06:10 UTC · monitoring
    We're monitoring the system to ensure the system is fully operational.
  3. 06:20 UTC · resolved
    The system is full operational.
Source
Sep 18, 20264h 46mSEV 2
Degraded Function ExecutionInngest reported degraded function execution starting 16:31 UTC on September 18, 2026. A first fix was deployed at 16:52, but further issues surfaced and a second fix was deployed at 18:33. The incident was marked resolved at 21:17 UTC. No cause or scope was given.AI-graded
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    Function execution was degraded for about five hours; the update does not say how many customers or regions were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
5 updates
  1. 16:31 UTC · investigating
    We are actively investigating an issue with function execution. We will provider further updates as we identify the cause and resolve the issue.
  2. 16:52 UTC · monitoring
    A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
  3. 18:05 UTC · identified
    Monitoring revealed additional issues, and we're actively working on further fixes to restore normal system operation.
  4. 18:33 UTC · monitoring
    A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
  5. 21:17 UTC · resolved
    The incident is now resolved and the system is full operational.
Source
Sep 4, 202643mSEV 2
Degraded Function ExecutionInngest function execution degraded starting 18:26 UTC on 2026-09-04. Users saw failed runs and delayed scheduling of runs from incoming events. Cause was identified and the system recovered; failed runs can be replayed in the UI. Resolved at 19:10 UTC.AI-graded
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Function execution had failed runs and delayed scheduling for about 40 minutes; the text does not say how many users were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 18:26 UTC · investigating
    We are actively investigating an issue with function execution. We will provider further updates as we identify the cause and resolve the issue.
  2. 18:28 UTC · investigating
    We are actively investigating an issue with execution. Users may experience failed runs or delayed scheduling of runs from incoming events. We will provider further updates as we identify the cause and resolve the issue.
  3. 19:09 UTC · monitoring
    We have identified the cause of the issue and we're monitoring the system as it is currently recovering. If users experienced any failed runs, you are able to replay failed runs in the UI. More info can be found here: <https://www.inngest.com/docs/platform/replay#how-to-create-a-new-replay>
  4. 19:10 UTC · resolved
    The incident is now resolved and the system is full operational.
Source
Aug 27, 20260mSEV 2
Connect Message Routing Delays - for Connect users onlyFor about 42 minutes on August 26, a subset of Inngest Connect customers saw delayed and failed function runs caused by an internal networking issue between Connect services. The change was reverted and a root-cause fix followed. Affected customers should review failed runs from the window and replay them only if safe and idempotent.AI-graded · some customers
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Function runs for a subset of Inngest Connect customers were delayed or failed for about 42 minutes due to an internal networking issue.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
1 update
  1. 00:31 UTC · resolved
    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.
Source
Aug 25, 20260mSEV 2
Connect Message Routing Delays - for Connect users onlyAn internal networking issue disrupted Inngest Connect between 23:38 and 00:08 UTC on August 24. Some customers saw delayed and failed function runs. The change was reverted and a root-cause fix followed. Affected customers were told to review failed runs and replay them if safe and idempotent.AI-graded · some customers
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Connect function runs were delayed and failed for a subset of customers for about 30 minutes due to an internal networking issue.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
1 update
  1. 20:38 UTC · 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.
Source
Aug 20, 202650mSEV 4
We are currently experiencing a delay with function runs being visible in the dashboard and have scaled up processing to work through the backlog.Function run history was delayed in the dashboard for under an hour; execution itself was not reported as affected.AI-graded
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · GLOBAL · MEDIUM CONFIDENCE
    Function run history was delayed in the dashboard for under an hour; execution itself was not reported as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 21:44 UTC · monitoring
    A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
  2. 22:35 UTC · resolved
    Run history delay has caught up and the incident is now resolved.
Source
Aug 19–20, 202634h 10mSEV 2
Delayed function executions for a subset of customers2 incidents
  1. Wed, Aug 19 04:54 UTC0mSEV 2
    Delayed function executions for a subset of customersFunction executions were delayed by seconds to a couple of minutes for a subset of customers on one shard, due to memory pressure.AI-graded · some customers
    Why this grade
    1. RULES · SEV 2
      Sev 2 from the incident title (no components listed)
    2. CLAUDE · SEV 2 · SUBSET · HIGH CONFIDENCE · BACK AFTER -13M
      Function executions were delayed by seconds to a couple of minutes for a subset of customers on one shard, due to memory pressure.
    3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
    2 updates
    1. 02:10 UTC · 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.
    2. 04:41 UTC · resolved
      Execution latencies are back to normal across all customers, and the incident is now resolved.
    Source
  2. Thu, Aug 20 13:44 UTC1h 19mSEV 2
    Delays in Function ExecutionFunction execution was delayed for an unstated set of customers for about 80 minutes before a fix was deployed.AI-graded
    Why this grade
    1. RULES · SEV 2
      Sev 2 from the incident title (no components listed)
    2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
      Function execution was delayed for an unstated set of customers for about 80 minutes before a fix was deployed.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
    3 updates
    1. 13:00 UTC · identified
      We are actively investigating an issue with delays with function execution. We have a fix that has been released and are monitoring the system.
    2. 13:47 UTC · monitoring
      A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
    3. 15:04 UTC · resolved
      The incident is now resolved and the system is full operational.
    Source
Aug 10, 20260mSEV 2
Delayed function execution for 15 minutesFunction execution was delayed for about 15 minutes on several nodes during emergency disk maintenance; no failures were reported.AI-graded · one location
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Function execution was delayed for about 15 minutes on several nodes during emergency disk maintenance; no failures were reported.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
1 update
  1. 22:30 UTC · resolved
    We observed temporary function execution delays for a period of 15 minutes as we performed emergency maintenance to manage disk capacity to several nodes.
Source
Jul 23, 20261h 07mSEV 2
Function processing delaysStarting function runs after events arrived was delayed from about 14:03 UTC. A publishing issue to a new Kafka topic caused it. The team isolated the topic, scaled consumers, and worked through the backlog. No events were dropped, all functions were scheduled, but late.AI-graded
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Function runs were delayed from starting after events arrived; no events were dropped, but the affected share is not stated.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 14:17 UTC · investigating
    We are actively investigating an issue with function execution that is leading to delays starting function runs after events are received. We will provider further updates as we identify the cause and resolve the issue.
  2. 14:41 UTC · identified
    We have identified the cause of the issue - the team has deployed a fix and is scaling to catch up on function delays.
  3. 15:06 UTC · monitoring
    New function execution has resumed and nearly caught up from the incurred backlog. Wait for event and cancel on handlers are still in a backlog and are catching up with processing. No events were dropped during this issue, all functions will be executed, but with delays. The root cause has been confirmd and changes are underway to prevent reoccurrence.
  4. 15:24 UTC · resolved
    The incident is now resolved and the system is full operational. Delays began around 14:03 UTC caused by an issue publishing to a new Kafka topic. Recovery began around 14:40 UTC as the team was able to isolate this topic. The consuming services which schedules new function runs was scaled out and began to consume the backlog. No events were dropped during this incident, all functions were scheduled, but with delays during this time window. No action is needed for manual recovery.
Source
Jul 16, 20261h 37mSEV 4
Metrics Data DelaysInngest's UI metrics were not up to date or unavailable from about 15:45 to 21:07 UTC. The provider confirmed function executions were working normally throughout. A fix was deployed and metrics were restored.AI-graded
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · GLOBAL · HIGH CONFIDENCE
    Dashboard metrics were stale or unavailable for about five hours; function execution and core platform stayed normal.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 17:52 UTC · investigating
    We are actively investigating an issue with our metrics service. Metrics displayed in the Inngest UI may not be up to date, but core platform functionality is unaffected and function execution is operating normally. We will provide further updates as we identify the cause and resolve the issue.
  2. 18:15 UTC · monitoring
    A fix has been deployed and we're monitoring the system to ensure the system is fully operational. We confirmed all executions were functioning as expected, so this only impacts the metrics on the dashboard.
  3. 19:29 UTC · resolved
    Metrics in the UI are now restored. Users may notice metrics data continue to be unavailable during the time of the incident, from the timeframe 7/16/26 15:45 UTC until approximately 7/16/26 21:07 UTC
Source
Jul 16, 20261h 12mSEV 2
Latency and Execution ErrorsInngest saw increased latency and execution errors. Some operations hit more errors and retries, causing backlogs and some failed checkpoints or signals. Mitigation raised throughput, and the incident was resolved about 70 minutes after the first monitoring update. A post-mortem is in progress.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Function execution latency and errors, with some checkpoints and signals failing and backlogs forming; the affected share of customers is not stated.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 09:45 UTC · investigating
    We are actively investigating an issue with latency and execution errors. We will provider further updates as we identify the cause and resolve the issue.
  2. 12:35 UTC · monitoring
    We identified issues in the system and have deployed changes to mitigate the issues. Throughput has increased across the system. We continue to monitor latency as well as we expect it to reduce with the throughput increases. We are continuing to investigate for any additional issues that may have occurred.
  3. 12:57 UTC · resolved
    Throughput and latency have recovered and the system should be fully operational again. The core issue is related to the part of the system that persists run state. Some operations experienced and increase in errors and retries, causing a backlog in some parts of the system and some failed operations like checkpoints or signals. We are continuing a thorough post-mortem investigation to prevent reoccurrance.
Source
Jul 10, 20263d 2hSEV 2
Issues Affecting Function Triggering from EventsEvents were delayed or failed to trigger functions for some users starting July 10, a partial outage. Throughput was improved, the backlog processed, and affected users may need to replay events. Resolved July 13.AI-graded
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Partial outage delayed or skipped function triggering from incoming events for affected users; scope not stated.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 15:50 UTC · investigating
    We are investigating a partial outage affecting function triggering from incoming events. Some events may experience delays before triggering functions, or functions may not trigger as expected. Our team is actively investigating and will provide updates as more information becomes available.
  2. 17:41 UTC · monitoring
    We've made updates to the system, and function throughput is continuing to improve for users affected. The backlog is actively being processed, and we're closely monitoring recovery to ensure processing returns to normal.
  3. 18:23 UTC · monitoring
    We are continuing monitoring the system. Users affected by this incident may need to replay impacted events to ensure their associated functions are executed.
  4. 19:44 UTC · resolved
    The incident is now resolved and the system is full operational.
Source
Jul 7, 202616h 35mSEV 2
Degraded function execution performanceFunction execution performance was degraded for an unspecified set of customers for about 25 hours; no components were named.AI-graded
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    Function execution performance was degraded for an unspecified set of customers for about 25 hours; no components were named.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 23:03 UTC · investigating
    We are actively investigating degraded function execution performance. We will provider further updates as we identify the cause and resolve the issue.
  2. 00:05 UTC · monitoring
    A fix has been deployed and we're monitoring the system to ensure the system is fully operational.
  3. 15:38 UTC · resolved
    The incident is now resolved and the system is full operational.
Source
Jul 7, 20260mSEV 2
Function execution down for a small subset of customersFunction execution failed for a subset of customers when one queue shard went down; the shard was recovered about 40 minutes later.AI-graded · some customers
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Function execution failed for a subset of customers when one queue shard went down; the shard was recovered about 40 minutes later.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 06:16 UTC · identified
    We’ve identified that one of the queue shards is down and are currently working to recover it. Only a subset of customers is affected.
  2. 06:33 UTC · monitoring
    We’ve recovered the queue shard and it is now operational. We’re continuing to monitor it closely.
  3. 06:45 UTC · resolved
    The incident is now resolved and the system is full operational.
Source
Jun 19, 20261h 34mSEV 4
Support Portal UnavailableThe Inngest support portal was unavailable for about 1.5 hours; the core API and product were not reported affected.AI-graded
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · GLOBAL · HIGH CONFIDENCE
    The Inngest support portal was unavailable for about 1.5 hours; the core API and product were not reported affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 11:34 UTC · investigating
    We are currently investigating an issue causing the Inngest support portal to be unavailable. Our team is working on a fix, and in the meantime, any support questions can be emailed directly to [[email protected]](mailto:[email protected]).
  2. 13:07 UTC · resolved
    The Support Portal is now available.
Source
May 26, 20262h 15mSEV 3
Downstream provider causing dashboard loading errorsDashboard loading errors caused by a downstream auth provider blocked console access for about two hours; app execution not described as affected.AI-graded
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Dashboard loading errors caused by a downstream auth provider blocked console access for about two hours; app execution not described as affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 21:31 UTC · identified
    We have identified the cause of the issue and are waiting for the downstream provider to implement their fix
  2. 22:07 UTC · monitoring
    A fix has been deployed via Clerk and we're monitoring the system to ensure the system is fully operational.
  3. 23:46 UTC · resolved
    The incident is now resolved.
Source

Peers, 90 days

Compare
MailerSendGrade A+100.00% up0 incidentsMTTR –PaddleGrade A+100.00% up3 incidentsMTTR 47mLoopsGrade A+100.00% up1 incidentMTTR 1h 34mKindeGrade A+99.99% up2 incidentsMTTR 1h 12mCloudinaryGrade A99.97% up5 incidentsMTTR 1h 47mAblyGrade A99.97% up7 incidentsMTTR 7mMailgunGrade A99.95% up9 incidentsMTTR 42mPusherGrade A99.96% up2 incidentsMTTR 3h 45mInngestGrade B99.59% up14 incidentsMTTR 43mMapboxGrade C99.91% up2 incidentsMTTR 12h 38mResendGrade C98.67% up25 incidentsMTTR 24mClerkGrade C99.90% up10 incidentsMTTR 3h 26mStytchGrade C99.79% up7 incidentsMTTR 57mWorkOSGrade C99.34% up21 incidentsMTTR 1h 05mPlaidGrade F98.13% up18 incidentsMTTR 3h 38mTwilioGrade F96.32% up57 incidentsMTTR 7h 26m

README badge

Inngest's live grade, for your README.

Inngest grade badge
[![inngest on downagain.dev](https://downagain.dev/badge/inngest.svg)](https://downagain.dev/p/inngest)