sevanalysis

Q4 2026: 1,537 incidents on public status pages

Preview. This covers October 1 to 2026-10-22 07:07 UTC, and every figure changes until the quarter ends on December 31. The published report will be a frozen snapshot.

Vendors with an incident
251 of 368
Vendor said why
27%
Named a major cloud or AI provider
6%
At AI vendors (23% of those tracked)
20%

How long incidents lasted

Tier Incidents Median per vendor Median to mitigation Median to resolution p95 to resolution
Infrastructure (78 tracked) 386 3 50m 1h 47m 44h 23m
Apps and SaaS (206 tracked) 851 2 1h 5m 2h 27m 2d 12h
AI (84 tracked) 300 1 28m 22m 10h 38m

Mitigation is the first "monitoring" update, and only counts for vendors whose pages have that stage.

What failed

1461 incidents tagged by deepseek/deepseek-v4.1-flash from their updates. "Not enough information" means the vendor described symptoms only.

Why, when the vendor said

Knock-on incidents

Longest incidents

Read this with care

Every figure comes from what vendors chose to post. A vendor that posts every blip will show more incidents than one that posts only big outages, so this report does not rank vendors. The vendor list was built to cover AI providers widely, so the AI share of incidents follows that list and is not an industry-wide figure; compare tiers by the median incidents per vendor instead, since a few vendors post far more than the rest. AI failures inside other products rarely reach a status page at all.

For 4 vendors, the recorded history starts after October 1, because their status pages no longer show earlier incidents. Azure posts reviews days after an incident, so its latest incidents arrive late. A vendor posting the same title again within an hour counts once. See the methodology for the rest.

Download the 1,537 incidents in this report (CC BY-NC 4.0).

Get the quarterly report by email

One email a quarter when a report is published. Reply to it to unsubscribe.