ChangeIntelIT change radar
Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 254/255 feeds/APIs · 0/409 docs · checked 12:55 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

5 ongoing incidents at 2 providers

Operational, as stated:AzureAzure DevOpsGitHubMicrosoft 365 admin centerMicrosoft 365 and Copilot for consumersPower Platform admin centerAnthropic (Claude)OpenAICisco MerakiUbiquiti UniFi cloud

No ongoing incident posted:Google Gemini and Vertex AI

Ongoing 5 incidents

Cloudflare Monitoring

Cloudflare Workers - Cron Trigger Activation Issues

Started today 05:36 UTC · open 7 h 32 min+Updated 4 h 55 min agoread 1 min ago

Workers

We are continuing to monitor for any further issues.

2 earlier updates
  1. today 07:23 UTCIdentifiedA fix has been identified and is underway
  2. today 05:36 UTCInvestigatingCloudflare is investigating issues with Workers Cron Triggers. Customers who have recently created or modified a Cron Trigger schedule may find that the schedule is not executing as expected. Pre-existing Cron Trigger schedules that have not been recently modified are not affected. We are working to identify the cause and mitigate this problem. More updates to follow shortly.
Around it6 other incidents at the same time · 5 earlier incidents

Elsewhere at the same time

Earlier incidents in the 14 days before

Cloudflare Monitoring

Audit Logs v2 ingestion is missing multiple Cloudflare products

Started 13 Oct 10:14 UTC · open 26 h 53 min+Updated 25 h 24 min agoread 1 min ago

Audit Logs

We are continuing to monitor for any further issues.

1 earlier update
  1. 13 Oct 10:14 UTCIdentifiedSince 2026-10-12 at 16:57:24 UTC, audit logs from multiple Cloudflare products are not ingested into the audit logs v2 database anymore. V1 audit logs are not affected
Around it6 other incidents at the same time · 5 earlier incidents

Elsewhere at the same time · within 12 hours of its start

Earlier incidents in the 14 days before

GitLab.com Monitoring

Increase of HTTP 50X errors on GitLab.com

Started 13 Oct 07:10 UTC · open 29 h 58 min+Updated 10 h 37 min agoread 1 min ago

WebsiteAPIGit OperationsPackage RegistryContainer RegistryGitLab Duo

Monitoring confirms that GitLab.com services have remained stable. We are continuing to monitor for any recurrence of the issues before marking this incident as resolved.

4 earlier updates
  1. 13 Oct 07:59 UTCMonitoringWe are seeing improvements across all services on GitLab.com. We are resuming our investigation on identifying the root cause.
  2. 13 Oct 07:48 UTCInvestigatingGeneral GitLab.com service continues to improve. We're now focused on restoring Duo services.
  3. 13 Oct 07:30 UTCInvestigatingWe are seeing an improvement in errors rates in our monitoring, starting from 07:14 UTC. We are still identifying the root cause.
  4. 13 Oct 07:10 UTCInvestigatingWe are currently investigating reports of an increase of HTTP 50X errors on GitLab.com
Around it6 other incidents at the same time · 1 earlier incident · 2 changes in the 14 days before

Elsewhere at the same time · within 12 hours of its start

Earlier incidents in the 14 days before

Changed in the 14 days before

Cloudflare Identified

Elevated Errors in China Network Colos

Started 10 Oct 04:13 UTC · open 4 days+Updated 45 h 37 min agoread 1 min ago

China Network

We have identified that increased latency and 5xx errors affecting certain China Network colos are caused by cross-border routing instability in the China network. We are actively working to mitigate impact for affected customers by adjusting traffic routing, and are continuing to work with our network partners on a resolution. Customers experiencing issues may contact Cloudflare Support.

3 earlier updates
  1. 12 Oct 04:23 UTCIdentifiedWe are investigating reports of degraded performance for traffic traversing the public internet between certain cities and provinces in mainland China and origin servers located outside the region. The impact is being reported across multiple ISPs and manifests as slower speeds or intermittent timeouts. While this congestion occurs upstream of Cloudflare's network, our engineering team is actively working to mitigate the effects. Intermittent 524 timeout errors is expected to continue due to ongoing congestion. While there is no fixed timeline for full resolution, as there are dependencies outside our network, we are taking steps to reduce customer impact.
  2. 10 Oct 05:48 UTCIdentifiedThe issue has been identified and a fix is being implemented.
  3. 10 Oct 04:13 UTCInvestigatingWe are investigating a spike in errors observed in our China colos.
Around it3 other incidents at the same time · 5 earlier incidents

Elsewhere at the same time · within 12 hours of its start

Earlier incidents in the 14 days before

Cloudflare Identified

Cloudflare One Clients are incorrectly challenged on some sites

Started 22 Sep 19:23 UTC · open 20 days+Updated 21d agoread 21 h 55 min ago

Cloudflare One Client

The issue has been identified and a fix is being implemented.

1 earlier update
  1. 22 Sep 19:23 UTCInvestigatingCloudflare is investigating an issue where Cloudflare One Client customers are incorrectly challenged while visiting some websites.
Around it4 other incidents at the same time · 5 earlier incidents

Elsewhere at the same time · within 12 hours of its start

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 14 Oct 12:55 UTC · 254 of 255 readable · 253 fully read · documentation 0/409 current