Replicate: Delayed scaling due to node failure

Replicate · replicate.comImpact: minorResolved2026-08-10 21:45 UTC

Public — what happened

Summary

All affected models have been scaling correctly for more than 30 minutes at this point, and we see no residual prediction queues. Thank you for your patience!

Timeline

Started — 2026-08-10 21:05 UTC
Last update — 2026-08-10 21:45 UTC
Resolved — 2026-08-10 21:45 UTC

Source of record: provider status page. Mirrored as reported; times in UTC.

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 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 →

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