Live  /  Cloudflare  /  Incident

Cloudflare: Cloudflare is currently having an issue with the r8.im registry used for Replicate model publishing and builds is currently restricted

Cloudflare · cloudflare.comMinor incidentResolved2026-11-14 00:51 UTC
Public — what happened

Summary

Cloudflare said a problem with the r8.im registry, which is used for publishing and building Replicate models, was limiting that service; it rated the incident as minor. The company reported at 14:55 UTC on 2026-11-13 that the issue had been identified and a fix was being put in place. At 23:34 UTC it said a fix had been applied and it was watching the results, and it marked the incident resolved at 00:51 UTC on 2026-11-14.

Affected

Replicate

As listed on Cloudflare’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

What SquidGrid measured

SquidGrid measured 252 internet paths into Cloudflare’s network during this incident. None of them ran meaningfully slower than the same paths the day before.

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 see
Customers 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.

The full archive is on the Cloudflare status & history page.

Related: Cloudflare status & history. SquidGrid is not affiliated with Cloudflare.