WhatBrokeToday
GTA 6FAQ

Microsoft 365 vs Render: reliability

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

Side by side, last 60 days

Microsoft 365 and Render reliability over the last 60 days
MeasureMicrosoft 365Render
Incidents (60 days)1011
Critical or high62
Median time to fix1 min1 min
Longest incident4 days18 min
Never on its status page90
Status page delay (median)1 min1 min
30-day hazard rating7.7 / 104.3 / 10

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

Render's worst incidents

Render's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
Render: Builds, deploys, and queued deploys are not starting in all regionshigh1 minfirst
Render: Build and deploy failures in Oregonhigh1 minfirst
Render: API Performance Issuesmedium18 minfirst
Render: Issues affecting connections to a subset of Postgres Databases

Cause: A configuration change rolled out to a small subset of Postgres instances caused connection failures for databases routing traffic through self-managed PgBouncer instances.

medium1 minfirst
Render: Degraded network performancemedium1 minfirst
Full Render outage history