Live / Replicate / Incident
Replicate: Replicate Pruna issue
Replicate · replicate.comMinor incidentResolved2026-09-17 21:51 UTC
Public — what happened
Summary
Replicate reported a minor problem on 2026-09-17, beginning at 01:09 UTC, in which certain models from Pruna were unable to add capacity. As a result, those models either had lengthy waits to run or could not be used at all. Replicate said it was collaborating with Pruna on a fix but did not describe a cause. The company marked the issue resolved at 21:51 UTC the same day.
Affected
Replicate
Timeline
- Started — 2026-09-17 01:09 UTC
- Identified — 2026-09-17 01:09 UTC
- Resolved — 2026-09-17 21:51 UTC · 20h 42m 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 39, 2026, our weekly internet health report.