WhatBrokeToday
GTA 6FAQ

AWS vs Microsoft 365: reliability

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

Side by side, last 60 days

AWS and Microsoft 365 reliability over the last 60 days
MeasureAWSMicrosoft 365
Incidents (60 days)2310
Critical or high156
Median time to fix1 min1 min
Longest incident6 h4 days
Never on its status page179
Status page delay (median)1 min1 min
30-day hazard rating9.6 / 107.7 / 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

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