Public mode

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

Some sources or documents need attention: 258/260 feeds/APIs · 416/439 docs · checked 14:46 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

1 ongoing incident at 1 provider

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 1 incident

GitHub Investigating

Incident with Actions Results

Posted today 14:18 UTCUpdated 14 min agoread 4 min ago

Actions

We’re seeing recovery, and repository update processing has returned to normal. Delays affecting GitHub Actions workflow and step results are continuing to clear as we scale processing capacity; the remaining backlog is expected to take about 20 minutes to drain.

3 earlier updates
  1. today 14:35 UTCUpdateRepository update processing has recovered. We’re continuing to work on delays affecting GitHub Actions workflow and step results. We’ll share another update as we make progress.
  2. today 14:19 UTCUpdateWe’re investigating delays in processing GitHub Actions workflow and step results, along with some repository updates.
  3. today 14:18 UTCInvestigatingWe are investigating reports of degraded performance for Actions
Around it5 earlier incidents
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 14:46 UTC · 258 of 260 readable · 256 fully read · documentation 416/439 current