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
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.
We have identified an issue causing delays in publishing organization cost data through the Costs API. A fix is in progress and currently undergoing testing. API and ChatGPT usage are not affected, and other reporting channels remain available. We are continuing work to restore normal data freshness.
1 change ChangeIntel noticed
today 20:01 UTC ChangeIntel noticed the text change
Around it4 other incidents at the same time · 5 earlier incidents
Started today 05:36 UTC · open 15 h+Updated 12 h 22 min agoread just now
Workers
We are continuing to monitor for any further issues.
2 earlier updates
today 07:23 UTCIdentifiedA fix has been identified and is underway
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 · within 12 hours of its start
Started 13 Oct 10:14 UTC · open 34 h 22 min+Updated 32 h 51 min agoread just now
Audit Logs
We are continuing to monitor for any further issues.
1 earlier update
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
Started 13 Oct 07:10 UTC · open 37 h 26 min+Updated 18 h 4 min agoread just now
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
13 Oct 07:59 UTCMonitoringWe are seeing improvements across all services on GitLab.com. We are resuming our investigation on identifying the root cause.
13 Oct 07:48 UTCInvestigatingGeneral GitLab.com service continues to improve. We're now focused on restoring Duo services.
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.
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
Started 10 Oct 04:13 UTC · open 4 days+Updated 2 h 47 min agoread just now
China Network
A fix has been implemented and we are monitoring the results.
4 earlier updates
12 Oct 15:33 UTCIdentifiedWe 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.
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.
10 Oct 05:48 UTCIdentifiedThe issue has been identified and a fix is being implemented.
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