WhatBrokeToday
GTA 6FAQ

GitHub vs Akamai Linode: reliability

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

Side by side, last 60 days

GitHub and Akamai Linode reliability over the last 60 days
MeasureGitHubAkamai Linode
Incidents (60 days)535
Critical or high201
Median time to fix1 min1 min
Longest incident13 days15 min
Never on its status page181
Status page delay (median)1 min1 min
30-day hazard rating10.0 / 103.7 / 10

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

Akamai Linode's worst incidents

Akamai Linode's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
Linode Security Incident Reportedhigh1 minnever
Akamai Linode: Service Issue - Cloud Manager and APImedium15 minfirst
Akamai Linode: Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)medium1 minfirst
Akamai Linode: Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilitiesminor1 minfirst
Akamai Linode: Customer Security Advisory: CVE-2026-98432minor1 minfirst
Full Akamai Linode outage history