Provider incident title: “Delayed scaling due to node failure”
Started
Monday, August 10, 2026
09:05 PM UTC
Duration
40m
total
Resolved
09:45 PM UTC
Aug 10, 2026
Scaling decisions were delayed by nearly 1 hour after the controller responsible for emitting queue metrics failed to schedule on a soft-failed node. We have since cordoned and drained the node, and the controller is emitting queue metrics again.
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!
Get alerted next time
Install Tickerr MCP — your agent auto-reports & routes around outages
When Replicate goes down again, your agent reports anonymously and instantly gets a fallback recommendation from the swarm.
Replicate is back online
View current status and uptime history
Replicate 30-day uptime: 100% based on Tickerr's independent monitoring checks.
This incident was sourced from Replicate's official Atlassian Statuspage. Tickerr ingests updates every 10 minutes to surface incidents as they are posted by the provider.
This incident lasted 40m.
Tickerr monitors 90+ AI tools independently. View live Replicate status or all AI tool status.
Get alerted next time Replicate goes down
Tickerr monitors 90+ AI tools. We'll email you when an incident starts or resolves.
Weekly AI pricing & uptime digest
Price drops, new model releases, and incident summaries - every Monday. Free.
Also on Tickerr