Degraded / minor incident Cloudflare Zero Trust status
cloudflare.com · Official status inherited from Cloudflare
FROM ALL SOURCES
Cloudflare's status page shows “Degraded / minor incident” in Replicate and Workers; the vendor is resolved. User reports haven't spiked, so wide impact isn't visible yet.
confidence: medium Vendor: minor issue · users: normal · routing: no data.
- Vendor status page Degraded / minor incident · 2 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP AS13335: routing data not loaded on this view
- News & network weather 8 active / 9 recent mentions
- Providers it may run on (inferred) status comes from Cloudflare's page
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Replicate, Workers, Queues, AS, AF
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 11 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | 6 h 10 min |
Evidence
- Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
- Vendor stage: resolved on “Errors and stalled predictions on some models”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- 8 active network-weather events mention Cloudflare Zero Trust. Overlap in time is coincidence, not causation. evidence confidence: low
What we don't know: what is happening inside Cloudflare Zero Trust's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: no data. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).
Who depends on whom
Cloudflare Zero Trust may run on Cloudflare (inferred). We don't map other services that depend on Cloudflare Zero Trust. Dependency chains are where single points of failure hide.
Identity & trust lens
When Cloudflare Zero Trust has trouble, people see failed logins, MFA prompts that don't arrive and sessions that drop. That's when phishing pages and “verify your account” texts show up. Only sign in through the official app or site, and don't re-enter credentials from a link someone sends you.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Cloudflare Zero Trust or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Cloudflare Zero Trust. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Errors and stalled predictions on some models
minor resolved · started · resolved
5 updates
- investigating
We are currently investigating this issue. Cloudflare is aware of, and investigating, an issue affecting predictions for some models on Replicate. Customers may see prediction requests return HTTP 500 errors, and some predictions may remain in a processing state without completing. Some API responses are also missing version information, which can cause validation errors in client libraries. We are working to understand the full impact and mitigate this problem.
- identified
The issue has been identified and a fix is being implemented. Current impact: prediction requests for some models may return HTTP 500 errors, and some predictions may stay in a processing state. Customers using the API may also see validation errors on responses.
- identified
The issue has been identified and a fix is being implemented. Current impact: predictions on OpenAI models are back to normal. Predictions on other models may still return HTTP 500 errors or stay in a processing state while we continue to work on a fix.
- monitoring
A fix has been implemented and we are monitoring the results.
- resolved
This incident has been resolved.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.