WhatBrokeToday
GTA 6FAQ

AWS vs GitHub: reliability

In the last 60 days, AWS had 23 incidents (median fix 1 min) and GitHub had 53 incidents (median fix 1 min). AWS broke less often.

Side by side, last 60 days

AWS and GitHub reliability over the last 60 days
MeasureAWSGitHub
Incidents (60 days)2353
Critical or high1520
Median time to fix1 min1 min
Longest incident6 h13 days
Never on its status page1718
Status page delay (median)1 min1 min
30-day hazard rating9.6 / 1010.0 / 10

AWS's worst incidents

AWS's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
AWS Experiencing Outage Reports Across Multiple Servicescriticalongoingnot yet
Unexplained Outages Affecting Systems Across AWS, Microsoft, and FAAcriticalongoingnot yet
Multiple Global Outages Including Microsoft and AWScriticalongoingnever
AWS US-EAST-1 Outage Disrupts Cloud Operationscritical1 minnever
AWS Service Disruption Affecting Multiple Systemscritical1 minnever
Full AWS outage history

GitHub's worst incidents

GitHub's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
GitHub: Incident with Webhookscritical1 hfirst
GitHub: Incident with Git Operations and Pull Requestscritical2 hfirst
GitHub: Incident with Actions and Checks API

Cause: An issue with an upstream model provider caused degraded availability for specific models in Copilot products and IDE surfaces.

critical3 daysfirst
GitHub: Disruption with GitHub servicescritical28 min+28 min
GitHub: Degraded availability for GitHub Actions, GitHub Pages and Webhookscritical3 days+3 days
Full GitHub outage history