WhatBrokeToday
GTA 6FAQ

CircleCI vs Microsoft 365: reliability

In the last 60 days, CircleCI had 14 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

CircleCI and Microsoft 365 reliability over the last 60 days
MeasureCircleCIMicrosoft 365
Incidents (60 days)1410
Critical or high26
Median time to fix1 min1 min
Longest incident1 min4 days
Never on its status page09
Status page delay (median)1 min1 min
30-day hazard rating2.7 / 107.7 / 10

CircleCI's worst incidents

CircleCI's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
CircleCI: Delay in data appearing in UI and APIhigh1 minfirst
CircleCI: Delays in pipelines, workflows, UI data, and notificationshigh1 minfirst
CircleCI: Increased wait time for Machine and Remote Docker jobs

Cause: Increased usage leading to capacity constraints for Machine and Remote Docker jobs.

medium1 minfirst
CircleCI: Delays for gen2 dedicated IP range jobs

Cause: Limited compute availability from the cloud provider

medium1 minfirst
CircleCI: Increased Docker gen2 wait timesmedium1 minfirst
Full CircleCI 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