Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 256/260 feeds/APIs · 416/439 docs · checked 15:48 UTC Customize Public modeDiscuss ChangeIntel on Discord

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.

Make this page yours

Choose the providers you depend on and the regions you run in, and what affects you comes first
Providers you depend onall providers
Providers you depend on

None chosen means all.

Regions you run inevery region
Regions you run in

Incidents elsewhere fold away; incidents that name no region always show.

Azure · Americas16
Azure · Europe20
Azure · Asia Pacific18
Azure · Middle East and Africa6
Azure Government6
Azure China6
Azure · Jio2
Azure DevOps8
Cloudflare datacenters6
Google Cloud2
On the overviewincidents that touch my providers and regions
On the overview
Changes apply as you make them.

Public status, not your tenant's health. Providers post only incidents they choose to share with everyone, usually wide ones. An empty list does not mean your services are healthy; for your own resources, check Service Health in the Azure portal or the Microsoft 365 admin center.

Right now

2 ongoing incidents at 2 providers

Operational, as stated:AzureAzure DevOpsMicrosoft 365 admin centerMicrosoft 365 and Copilot for consumersPower Platform admin centerAnthropic (Claude)OpenAICisco MerakiUbiquiti UniFi cloudGitLab.com

No ongoing incident posted:Google Gemini and Vertex AI

Ongoing 2 incidents

Cloudflare Monitoring

Cloudflare Workers API Latency

Started today 15:33 UTC · open 42 min+Updated 13 min agoread 1 min ago

Workers

We are continuing to monitor for any further issues.

1 earlier update
  1. today 15:33 UTCIdentifiedCloudflare is investigating an increased latency when interacting with Workers API and Workers configuration in the dashboard. Customers might experience longer wait times on Workers endpoints, particularly when deploying a script. Workers that are already running in production are not affected. More updates to follow shortly.
Around it2 other incidents at the same time · 5 earlier incidents

Elsewhere at the same time

GitHub Investigating

Errors loading Issues, Pull Requests, and search results

Posted today 15:28 UTCUpdated 9 min agoread 1 min ago

Pull RequestsIssues

Some users continue to experience intermittent errors loading Issues, Pull Requests and search results on github.com. We're investigating and evaluating mitigation options to restore normal service.

2 earlier updates
  1. today 15:33 UTCUpdateSome users may experience intermittent errors loading Issues, Pull Requests and search results on github.com. We're investigating and working to restore normal service.
  2. today 15:28 UTCInvestigatingWe are investigating reports of degraded performance for Actions, Issues and Pull Requests
Around it2 other incidents at the same time · 5 earlier incidents

Elsewhere at the same time

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Oct 15:48 UTC · 256 of 260 readable · 254 fully read · documentation 416/439 current