Public mode

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

Some sources or documents need attention: 271/271 feeds/APIs · 464/464 docs · 4/4 advisories · checked 15:50 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

3 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 3 incidents

Cloudflare Identified

Network connectivity issues affecting services in North America

Started today 15:47 UTC · open 26 min+Updated 10 min agoread 4 min ago

Network

We have identified a connectivity provider outage causing network congestion and degraded performance for some customers in North America. Affected customers may experience increased latency, packet loss, and intermittent errors across multiple services. Our network team is rerouting traffic away from affected paths, and we are working directly with our provider on restoration.

1 earlier update and 1 change ChangeIntel noticed
  1. today 15:47 UTCInvestigatingWe are investigating degraded network performance affecting some traffic between our Ashburn and Atlanta data centers. Some customers may see increased latency, packet loss, or intermittent errors on Workers and other services in the Eastern US. Our network team is actively working on mitigation.
  2. today 16:08 UTC ChangeIntel noticed a new title; it was "Degraded network performance affecting some traffic between Cloudflare data centers"
Around it2 other incidents at the same time · 5 earlier incidents

Elsewhere at the same time

Cloudflare Investigating

Delayed, missed, and duplicated Workers Cron Triggers

Started today 15:27 UTC · open 46 min+Updated 5 min agoread 4 min ago

Workers

We are investigating reports that some Workers Cron Triggers are running late, being skipped, or running more than once. Affected customers may see scheduled Workers invocations that do not run on time or run more than once. We will post an update as we learn more.

Around it2 other incidents at the same time · 5 earlier incidents

Elsewhere at the same time

GitHub Investigating

Disruption with Dependabot Alerts

Posted today 14:58 UTCUpdated 6 min agoread 4 min ago

GitHub

We’re continuing to investigate delays in some Dependabot alerts closing after affected repositories are updated. Alert processing remains backed up, and additional processing capacity is rolling out to help reduce the backlog. We’re monitoring the rollout and will share another update as we learn more.

3 earlier updates
  1. today 15:39 UTCUpdateWe’re scaling alert processing capacity to reduce the backlog causing delays in some Dependabot alerts closing after affected repositories have been updated. We’re continuing to monitor and will share another update as more information becomes available.
  2. today 15:00 UTCUpdateWe’re investigating delays in some Dependabot alerts closing after affected repositories have been updated to address a vulnerability. Alert processing is backed up. We’ll share more information as it becomes available.
  3. today 14:58 UTCInvestigatingWe are investigating reports of impacted performance for some GitHub services.
Around it2 other incidents at the same time · 5 earlier incidents

Elsewhere at the same time

Earlier incidents in the 14 days before

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 23 Oct 15:50 UTC · 271 of 271 readable · 269 fully read · documentation 464/464 current