Root cause
Storage
Object, block or file storage became slow or unavailable.
Incidents per month
October 2025September 2026
Incidents
IncidentStarted (UTC)DurationImpactRoot cause
ElasticAutoOps node metrics temporarily unavailable in some regionsSep 17, 2026, 15:5041mMajorStorage
SupabaseUnresponsive ProjectsSep 10, 2026, 15:2627h 40mMajorStorage
GitHubDisruption with GitHub BillingAug 26, 2026, 23:3720h 7mMinorStorage
GitHubActions delays in starting runsAug 24, 2026, 13:5638mMinorStorage
GitHubDisruption with GHEC Team SyncAug 13, 2026, 16:212h 6mMinorStorage
DigitalOceanBlock Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1Jul 19, 2026, 09:515h 41mMinorStorage
GitHubIncident with WebhooksJun 11, 2026, 19:422h 37mMinorStorage
Grafana LabsOutage for prod-eu-central-0 due to AWS S3 outage.Mar 7, 2026, 20:0736h 52mInformationalStorage
AWSIncreased Error RatesMar 7, 2026, 19:531h 11mMajorStorage
GitHubDegraded Performance in Webhooks API and UI, Pull RequestsFeb 9, 2026, 08:153h 11mMinorStorage
MailgunDelayed Logs in EU RegionNov 28, 2025, 08:2810h 46mMinorStorage
Questions
How common are outages caused by storage?
11 incidents in the last 12 months across the vendors tracked here were traced to storage in the vendors' own words.
How is this cause identified?
From the sentences where the vendor explains why the incident happened, or by hand for landmark postmortems. Symptoms like "elevated error rates" are never counted as a cause.
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.