Live  /  Providers  /  Replicate

Replicate

replicate.comNo open incidents

Independent assessment — SquidGrid is not affiliated with Replicate. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

AI · SquidGrid tracks Replicate’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Replicate is reporting

Current & recent incidents

Resolved

Replicate Flux Hotswap Models Stuck

Minor impact · 2026-09-28 20:28 UTC

Resolved

Intermittent 500 errors for backend services on Replicate

Minor impact · 2026-09-24 22:34 UTC

Resolved

Replicate Pruna issue

Minor impact · 2026-09-17 21:51 UTC

Resolved

Some Replicate models are failing to start

Minor impact · 2026-09-15 14:06 UTC

Resolved

A100 hardware partial outage

Major impact · 2026-08-27 00:25 UTC

Resolved

Delayed scaling due to node failure

Minor impact · 2026-08-10 21:45 UTC

Resolved

Significant degradation

None impact · 2026-08-05 11:33 UTC

Resolved

API degraded for A100s

None impact · 2026-08-02 16:18 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what Replicate has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Replicate runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Replicate is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Replicate.