Is Replicate down?
Replicate status · AI & APIs · checked (1s ago)
We could not reach Replicate's status feed, so its current state is unconfirmed.
According to Replicate's official status page, Replicate was reporting “Status API unreachable (Unexpected token '<', "<!DOCTYPE "... is not valid JSON)” when isuptime last checked at .
What to do while Replicate is down
isuptime cannot fix Replicate, and neither can you. These are the things that are actually worth doing until it comes back.
- Read what Replicate has actually published. Their incident notes say which components are affected and usually carry an estimate, which is more than any third party can tell you. Replicate's status page
- Stop retrying in a loop. If your code calls Replicate, back off exponentially and cap the retries. A retry storm from every client at once is a large part of why outages take as long to clear as they do, and it will exhaust your own quota before the service returns.
- Get told when it clears, instead of refreshing. The bell in the header sets up a browser notification, or a Discord, Slack or Telegram webhook, for the moment Replicate's status changes.
Is Replicate down for you right now?
Everything above is read from Replicate's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Replicate in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
What Replicate is
Replicate runs machine learning models as hosted APIs — image generation, video, audio, language models and anything else pushed as a Cog container. You call a model, it returns a prediction, and Replicate handles the GPUs underneath.
What Replicate's status feed covers
The status page covers the API and the prediction pipeline. The distinctive failure mode is not covered by any indicator: models scale to zero when idle, so the first call after a quiet period pays a cold boot that can run to minutes. That is designed behaviour, not an incident, and it is the single most common reason a Replicate call appears to hang.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
Other services reporting problems right now
10 other services isuptime tracks were also reporting a problem as of the same check, 1s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
CloudflarePartial System Outage- Razorpay1 of 7 services down: Payments API
- ElasticPartial System Outage
GrafanaMinor Service Outage- PlayStation NetworkPlayStation Store affected in Russia
- SalesforceDegraded Performance: 1 active incident
- ScalewayPartially Degraded Service
- SnowflakePartially Degraded Service
Replicate response time trend
Each point is one check of Replicate's status endpoint.
Replicate outage history
Every incident Replicate has published in the last 12 months.
Replicate has not published a single incident in the last 12 months. That is a statement about Replicate's posting habits as much as its reliability — a status page only records what its owner decides to record.
Replicate status — frequently asked
- Is Replicate down right now?
- We could not reach Replicate's status feed, so its current state is unconfirmed. Checked (1s ago).
- What is Replicate's status right now?
- Replicate is reporting “Status API unreachable (Unexpected token '<', "<!DOCTYPE "... is not valid JSON)” on its official status page — Unknown — as of . isuptime reads this from Replicate's own published feed and does not test Replicate independently.
- What is Replicate's uptime?
- isuptime does not measure Replicate's uptime directly — it reads Replicate's own published status feed. isuptime does not have 30 days of history for Replicate yet.
- Is it just me, or is Replicate down for everyone?
- Replicate is reporting a problem on its own status page, so this is affecting other users too, not just you.
Replicate says operational but it is not working for me
Check whether the model you are calling is public and still published — authors can remove or rename versions, which fails per-model while Replicate itself is fine. A prediction stuck in `starting` is a cold boot; a prediction stuck in `processing` past the model's usual time is usually the model, not the platform. GPU capacity for a specific hardware tier can be exhausted without a platform-wide incident being posted.
