AWS vs GitHub
Cloud Infrastructure vs Developer Tools — 30 days of community outage reports and detected incidents. We don't probe either domain continuously; this is what users report.
aws.amazon.com
No active incident
github.com
No active incident
Frequently asked
Which is more reliable, AWS or GitHub?
Both AWS and GitHub have similar community-reported activity over the past 30 days (0 reports for AWS, 0 for GitHub; 0 vs 24 detected incidents). We don't probe either site continuously, so we report what users tell us — not a synthetic uptime score.
How does WebsiteDown compare AWS and GitHub?
We aggregate two real signals for each side: user-submitted "down" / "working" reports tracked in 24-hour, 7-day, and 30-day windows, and detected incidents (continuous spikes flagged by our snapshot pipeline when reports cross a 3× baseline threshold). We don't fabricate uptime percentages or response times for sites we don't continuously probe.
Has AWS or GitHub had any major outages recently?
GitHub has had more detected incidents in the last 30 days. Detected incidents are anomalous spikes in user reports — typically a 3× baseline spike sustained for at least 15 minutes. The /is-github-down permalink shows the full timeline; the recent incident table on each side's status page lists each one.
Where does this comparison data come from?
Two sources: (1) community reports submitted via the Report issue / Working buttons across our status pages, stored in our outage_reports table; (2) detected incidents from our snapshot pipeline, which flags anomalous spikes. We don't probe aws.amazon.com or github.com from multiple regions on a schedule — continuous monitoring is a paid product for sites you own. This page reflects user-perceived issues only.