Service status
What Microsoft, GitHub, Cloudflare, Ubiquiti, Cisco Meraki, Palo Alto Networks, GitLab, OpenAI, Anthropic, and Google post on their public status pages, read every 5 minutes while something is open. Each incident shows what else was happening and what changed in the same products just before.
Choose the providers you depend on and the regions you run in, and what affects you comes first Now 2 Ended 53
53 incidents · newest first All53 OpenAI18 Cloudflare15 Azure DevOps5 GitHub5 Anthropic (Claude)4 Azure3 Microsoft 365 admin center3 Yesterday1
Azure DevOps
Service maintenance is in effect
last seen 23:13 UTC
unknown Posted 8 Oct 16:36 UTC Updated 9 h 23 min ago
Core services
Around it 4 other incidents at the same time · 1 earlier incident Elsewhere at the same time
Earlier incidents in the 14 days before
Tue 6 Oct1
Azure DevOps
Investigating a service disruption
last seen 18:51 UTC
unknown Posted 6 Oct 16:17 UTC Updated 2d ago
Other services
Around it 3 other incidents at the same time · 1 earlier incident Elsewhere at the same time
Earlier incidents in the 14 days before
Mon 5 Oct1
Azure DevOps
Investigating a service disruption
last seen 20:54 UTC
unknown Posted 5 Oct 19:28 UTC Updated 3d ago
Other services
Around it 4 other incidents at the same time · 1 earlier incident Elsewhere at the same time
Earlier incidents in the 14 days before
Fri 2 Oct2
Azure DevOps
Investigating a service disruption
last seen 23:22 UTC
unknown Posted 2 Oct 21:43 UTC Updated 6d ago
Other services
Around it 3 other incidents at the same time · 1 earlier incident Elsewhere at the same time
Earlier incidents in the 14 days before
Azure DevOps
Investigating a service disruption
last seen 07:10 UTC
unknown Posted 2 Oct 06:44 UTC Updated 6d ago
Other services
Around it 2 other incidents at the same time · 1 earlier incident Elsewhere at the same time
Earlier incidents in the 14 days before
What went wrong in major incidents and what Microsoft is changing
Azure public incident reviews · 30 Sep 2026 · Azure Tracking ID: 7Q30-010
Azure public incident reviews · 29 Sep 2026 · Azure Tracking ID: 7QL5-Z50
Azure public incident reviews · 23 Jul 2026 · Azure Tracking ID: ZJV6-SGG
How this page is built. Each provider's own public status source is read: Azure's status feed, the Azure DevOps health API, Microsoft's status posts for the Microsoft 365 and Power Platform admin centers, the incident history feeds and status pages of GitHub, Anthropic, Ubiquiti, Cisco Meraki and Palo Alto Networks, Cloudflare's status API, GitLab's status.io status, OpenAI's status feed and summary, and Google Cloud's incident list narrowed to Gemini and Vertex AI. Where a feed lists only ongoing incidents, disappearance is recorded between the last observation and the next successful check; no provider resolution time is inferred. Renames and rewrites are what ChangeIntel saw change between reads. "Possibly related" means the same region or product at the same time, never a confirmed cause; changes shown before an incident are context.