Live  /  Cloudflare  /  Incident

Cloudflare: Replicate Issue

Cloudflare · cloudflare.comMinor incidentResolved2026-11-12 11:34 UTC
Public — what happened

Summary

Cloudflare said that customers of its Replicate service might have seen more server errors (500 errors) when requesting predictions, and it labeled the issue minor. The company began investigating at 08:30 UTC on 2026-11-12. About an hour later, at 09:34 UTC, it said the problem had been identified and a fix was being put in place. Cloudflare marked the incident resolved at 11:34 UTC, without describing the cause in detail.

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 230 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.