WhatBrokeToday
GTA 6FAQ

Akamai Linode vs Microsoft 365: reliability

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

Side by side, last 60 days

Akamai Linode and Microsoft 365 reliability over the last 60 days
MeasureAkamai LinodeMicrosoft 365
Incidents (60 days)510
Critical or high16
Median time to fix1 min1 min
Longest incident15 min4 days
Never on its status page19
Status page delay (median)1 min1 min
30-day hazard rating3.7 / 107.7 / 10

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

Microsoft 365's worst incidents

Microsoft 365's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
Microsoft 365 and Azure Global Outage Caused by July Fix Software Defect

Cause: A software defect introduced in a July fix caused some servers to stop working, piling pressure on other servers which also failed, leading to elevated load.

critical4 daysnever
Microsoft Server Farm Hit Causing Worldwide Outlook Outagecriticalongoingnot yet
Microsoft 365 Outage Forces Japanese Workers Back to Fax Machineshigh11 hnever
Microsoft Power Platform API Service Principal Disables RoleAssignments.Writehighongoingnot yet
Microsoft 365 and Consumer Services Experience Outageshigh1 minnever
Full Microsoft 365 outage history