Is Replicate Down?
Reachable from all 8 checked regions
Average response time: 899ms
Last checked · checks run every 6 hours
Official status page: https://www.replicatestatus.com
Replicate uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 61 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
61-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What Replicate does
Replicate runs machine learning models behind an API, so applications can call image, audio and language models without operating GPUs themselves. Models are packaged as containers and pushed to its registry at r8.im. Products that generate images or transcribe audio often depend on it for a user-facing feature rather than a background job, which makes an outage immediately visible.
What an outage looks like
Calls to create a prediction return errors, or are accepted and then never complete, leaving predictions queued indefinitely. Cold starts stretch well past normal, so a model that usually answers in seconds times out instead. Pushes to the r8.im registry fail during a deploy. The dashboard can load while inference is failing, which hides the problem from a quick check.
What to do about it
Check replicatestatus.com, which separates the API, inference and training, the r8.im registry and the website, so a failing deploy and a failing prediction are told apart. Predictions are asynchronous, so poll rather than assuming a stalled call has failed. Applications calling Replicate on a user-facing path should degrade or fall back rather than hold the request open.
Is it down for everyone, or just you?
If this page says Replicate is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Replicate outage FAQ
Do I get charged for predictions that fail?
Why is the first call after an idle period so slow?
Does an outage affect deploys as well as inference?
Should my app call Replicate synchronously?
How we measure this
- We request Replicate's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Replicate publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when Replicate goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring