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.
Started today 07:10 UTC · open 30 min+Updated 31 min agoread 1 min ago
Workers AI
Cloudflare has identified an issue whereby customers might experience errors from inference requests to certain models using Workers AI. These are the list of impacted model: @cf/deepseek-ai/deepseek-v4-flash-0731 @cf/deepseek-ai/deepseek-v4-pro-0813 @cf/zai-org/glm-5.2 @cf/zai-org/glm-5.3 @cf/zai-org/glm-5.3-flash We are working to mitigate this problem. More updates to follow shortly.
Around it6 other incidents at the same time · 5 earlier incidents
No material updates to report. We'll share another update when we have more information.
3 earlier updates and 1 change ChangeIntel noticed
today 05:27 UTCInvestigatingNo material updates to report. We are still investigating the root cause.
today 05:10 UTCInvestigatingWe have received reports that some groups on GitLab.com are experiencing HTTP 500 errors because the group is unable to sync with customers.gitlab.com. We are continuing to investigate the issue.
today 04:43 UTCInvestigatingWe're investigating an issue that's stopping pages on customers.gitlab.com from loading. Purchasing, renewing, and managing subscriptions may be affected. GitLab.com itself is not affected.
today 07:41 UTC ChangeIntel noticed a new title; it was "Error loading customers.gitlab.com"
Around it6 other incidents at the same time · 4 earlier incidents · 1 change in the 14 days before
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
14 Oct 20:01 UTC ChangeIntel noticed the text change
Around it6 other incidents at the same time · 5 earlier incidents
Started 13 Oct 10:14 UTC · open 45 h 26 min+Updated 43 h 56 min agoread 1 min ago
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 10 Oct 04:13 UTC · open 5 days+Updated 13 h 52 min agoread 1 min ago
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