Live / Replicate / Incident
Replicate: Replicate Issue
Replicate · replicate.comMinor incidentResolved2026-11-12 11:34 UTC
Public — what happened
Summary
Replicate reported a minor issue starting at 08:30 UTC on 2026-11-12, saying customers might see more server errors (500 errors) when running predictions. About an hour later, at 09:34 UTC, the company said it had identified the problem and was putting a fix in place. Replicate marked the incident resolved at 11:34 UTC the same day. Its updates did not describe a specific cause beyond mentioning Cloudflare at the start of the first message.
Affected
Replicate
Timeline
- Started — 2026-11-12 08:30 UTC
- Investigating — 2026-11-12 08:30 UTC
- Identified — 2026-11-12 09:34 UTC
- Resolved — 2026-11-12 11:34 UTC · 3h 04m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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.