Lilambd/world-outages-ledger

World Outage Ledger

Incidents that cloud and SaaS providers published on their own official status pages, collected every 2 minutes from each provider's public feed and refreshed here daily. One row per published incident (AWS: one row per posted update, grouped by thread_key = service-region).

Data as of 2026-11-13T03:46Z. 1,649 incidents; 19 were open (not marked resolved by the provider) at that time. Nothing here is estimated, inferred or rated by Lilambd: every value is what the provider published, and url links to the provider's own page for that incident. An empty cell means the provider did not publish that value. Feeds go back as far as each provider keeps them (Statuspage feeds: latest 50 incidents at first load; history grows from 2026-11-12 on).

provider	feed type	incidents	first day	official feed
Anthropic (Claude)	statuspage	50	Thu Aug 13 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.anthropic.com/api/v2/incidents.json
Asana	statuspage	50	Fri Jun 28 2024 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.asana.com/api/v2/incidents.json
Atlassian	statuspage	34	Tue May 07 2019 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.atlassian.com/api/v2/incidents.json
AWS	rss	45	Sun Mar 01 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.aws.amazon.com/rss/all.rss
Bitbucket	statuspage	50	Wed Aug 07 2024 00:00:00 GMT+0000 (Coordinated Universal Time)	https://bitbucket.status.atlassian.com/api/v2/incidents.json
Box	statuspage	50	Sat Jan 03 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.box.com/api/v2/incidents.json
Cloudflare	statuspage	50	Mon Oct 26 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://www.cloudflarestatus.com/api/v2/incidents.json
Cloudinary	statuspage	50	Fri May 30 2025 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.cloudinary.com/api/v2/incidents.json
Coinbase	statuspage	51	Sat Sep 19 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.coinbase.com/api/v2/incidents.json
DigitalOcean	statuspage	50	Tue Apr 28 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.digitalocean.com/api/v2/incidents.json
Discord	statuspage	50	Sat Feb 28 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://discordstatus.com/api/v2/incidents.json
Dropbox	statuspage	50	Mon May 13 2024 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.dropbox.com/api/v2/incidents.json
Elastic Cloud	statuspage	50	Tue Apr 28 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.elastic.co/api/v2/incidents.json
Epic Games	statuspage	50	Thu Feb 26 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.epicgames.com/api/v2/incidents.json
Figma	statuspage	50	Wed Nov 15 2023 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.figma.com/api/v2/incidents.json
GitHub	statuspage	50	Wed Sep 16 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://www.githubstatus.com/api/v2/incidents.json
Google Cloud	gcp	6	Tue Jul 14 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.cloud.google.com/incidents.json
HashiCorp	statuspage	25	Tue Jun 30 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.hashicorp.com/api/v2/incidents.json
HubSpot	statuspage	50	Mon Jan 12 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.hubspot.com/api/v2/incidents.json
Kraken	statuspage	51	Fri Sep 04 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.kraken.com/api/v2/incidents.json
Linear	statuspage	25	Mon May 25 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://linearstatus.com/api/v2/incidents.json
Mailgun	statuspage	50	Thu Oct 17 2024 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.mailgun.com/api/v2/incidents.json
Microsoft 365	rss	8	Thu Nov 12 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.cloud.microsoft/api/posts/mac
Microsoft Azure	rss	0		https://azure.status.microsoft/en-us/status/feed/
Miro	statuspage	25	Mon May 19 2025 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.miro.com/api/v2/incidents.json
MongoDB Cloud	statuspage	50	Sat Feb 28 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.mongodb.com/api/v2/incidents.json
Netlify	statuspage	50	Fri Apr 24 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://www.netlifystatus.com/api/v2/incidents.json
New Relic	statuspage	50	Thu Dec 05 2024 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.newrelic.com/api/v2/incidents.json
npm	statuspage	50	Mon Jun 03 2024 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.npmjs.org/api/v2/incidents.json
OpenAI	statuspage	25	Wed Oct 21 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.openai.com/api/v2/incidents.json
Reddit	statuspage	50	Fri Jun 28 2024 00:00:00 GMT+0000 (Coordinated Universal Time)	https://www.redditstatus.com/api/v2/incidents.json
Sentry	statuspage	50	Tue May 26 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.sentry.io/api/v2/incidents.json
Shopify	statuspage	50	Thu Oct 17 2019 00:00:00 GMT+0000 (Coordinated Universal Time)	https://www.shopifystatus.com/api/v2/incidents.json
Slack	slack	28	Mon May 18 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://slack-status.com/api/v2.0.0/history
Snowflake	statuspage	50	Sun Mar 01 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.snowflake.com/api/v2/incidents.json
Supabase	statuspage	25	Mon Oct 12 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.supabase.com/api/v2/incidents.json
Twilio (incl. SendGrid)	statuspage	51	Mon Oct 12 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.twilio.com/api/v2/incidents.json
Vercel	statuspage	50	Thu May 28 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://www.vercel-status.com/api/v2/incidents.json
Zoom	statuspage	50	Wed Sep 09 2026 00:00:00 GMT+0000 (Coordinated Universal Time)	https://status.zoom.us/api/v2/incidents.json

Quick start

from datasets import load_dataset
ev = load_dataset("Lilambd/world-outages-ledger", "events", split="train").to_pandas()
ev[ev.provider == "GitHub"].sort_values("started_at").tail()

Columns (data/events.csv)

provider, source (feed key), ext_id (provider's incident id), thread_key, title (as published), status and impact (provider's own words: e.g. investigating/identified/monitoring/resolved; none/minor/major/critical; GCP severity), started_at, resolved_at, vendor_updated_at (UTC), duration_min (resolved_at - started_at, only when both were published), components and locations (as published, "; "-separated), url (official incident page), first_seen (when this ledger first saw it).

status = "no longer listed by vendor" means a feed that only lists current issues (Azure, Microsoft 365) stopped listing it; the provider did not necessarily call it resolved.

Other files

• data/daily_by_provider.csv: per UTC day and provider, incidents started, by published impact, and summed published duration.
• data/same_day_microsoft_mentions.csv: incidents from other providers whose published title mentions Microsoft, Outlook, Exchange, Teams, Azure or Office, with the Microsoft incidents of the same day. This is a text match on titles, not a claim about cause.
• data/sources.csv: every feed, its URL and last successful fetch.

Not included

• The full text of providers' incident updates (kept privately as a source record; read it on the provider's page via url).
• Crowd reports, social media, or any third-party "is it down" signals. Only what the provider itself published.
• Tenant-specific Microsoft 365 service health (visible only to each tenant's admins). The public Microsoft feed shows only broad incidents.
• Providers whose feed refused automated reads at collection time (Datadog, Fastly) or that publish no machine-readable feed.

Licence and credit

Incident titles, statuses and times are quoted from each provider's official status page (linked per row); those pages remain the providers' own. This compilation: CC BY 4.0, Lilambd.