Live / Cloudflare / Incident
Cloudflare: Replicate Model Registry Unavailable
Cloudflare · cloudflare.comMinor incidentResolved2026-11-13 01:44 UTC
Public — what happened
Summary
Cloudflare said it began investigating problems with Replicate on 2026-11-11 at 04:33 UTC, first involving uploads of inputs. By 05:11 UTC it said the issue had been identified and a fix was being worked on, and later updates described input uploads as degraded and model builds and pushes through r8.im as unavailable. On 2026-11-12 at 22:55 UTC Cloudflare said a fix had been put in place and it was watching the results, and the incident was not yet marked resolved.
Affected
Replicate
Timeline
- Started — 2026-11-11 04:33 UTC
- Investigating — 2026-11-11 04:33 UTC
- Identified — 2026-11-11 05:11 UTC (3 updates)
- Monitoring — 2026-11-12 22:55 UTC
- Resolved — 2026-11-13 01:44 UTC · 45h 11m after it started
What SquidGrid measured
SquidGrid measured 258 internet paths into Cloudflare’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Cloudflare against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Cloudflare: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Cloudflare report →
More from Cloudflare
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.