WhatBrokeToday
GTA 6FAQ

GitLab vs Microsoft 365: reliability

In the last 60 days, GitLab 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

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

GitLab's worst incidents

GitLab's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
GitLab Backup Procedure Fails Due to PostgreSQL Major Version Mismatch

Cause: A difference in major versions between pg_dump (9.2) and the running PostgreSQL database (9.6) caused pg_dump to produce an error and end the backup.

highongoingnot yet
GitLab: Issues Running Pipelineshigh1 minfirst
GitLab Security Incident: Attempted Exploitation of CVE-2026-97229high1 minnever
GitLab Outagehighongoingnot yet
GitLab: CI/CD Job Delays on GitLab.commedium1 minfirst
Full GitLab 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