Root cause
Database
A database failover, overload, corruption or replication fault.
Incidents per month
October 2025September 2026
39
in 12 months
14
major or critical
1h 17m
median duration
most affected
Incidents
IncidentStarted (UTC)DurationImpactRoot cause
SentryIssues performance is degraded in the USAug 26, 2026, 16:174h 19mMinorDatabase
DigitalOceanAccount Registration, Droplets, and Related ServicesAug 8, 2026, 18:576h 3mMinorDatabase
Fly.ioPartial outage in ORDJul 3, 2026, 00:115h 48mMajorDatabase
SnykSnyk Code (SAST) Scan service degradedJun 19, 2026, 20:132hMinorDatabase
MiroMiro is partially downMay 4, 2026, 16:232h 37mMajorDatabase
ExpoElevated EAS Build errorsApr 27, 2026, 13:300mMajorDatabase
LaunchDarklyDelayed processing of Session Replay and Error dataApr 6, 2026, 17:581h 3mMinorDatabase
RenderOhio Services with Disks, Data Persistence failingMar 3, 2026, 00:4120mMajorDatabase
npmIssues publishing and installing packagesApr 11, 2025, 02:4612h 5mMinorDatabase
UpstashRegional AWS eu-west-1 Cluster Performance Degradation IssueFeb 25, 2025, 14:037h 20mMinorDatabase
Questions
How common are outages caused by database?
39 incidents in the last 12 months across the vendors tracked here were traced to database 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.