Live  /  Replicate  /  Incident

Replicate: Replicate Model Registry Unavailable

Replicate · replicate.comMinor incidentResolved2026-11-13 01:44 UTC
Public — what happened

Summary

Replicate said it began dealing with a problem at 04:33 UTC on 2026-11-11, which it titled as its model registry being unavailable and rated minor. The company said Cloudflare was looking into trouble with input uploads, and later reported that uploads were degraded while building and pushing models through r8.im was unavailable. Replicate said it identified the issue at 05:11 UTC and kept working on a fix through the following day. As of 22:55 UTC on 2026-11-12, it said a fix was in place and it was monitoring the results, so the incident was not yet marked resolved.

Affected

Replicate

As listed on Replicate’s status page.

Timeline

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

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Replicate 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 Replicate: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Replicate report →

More from Replicate

Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.

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

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