Is Replicate down?
Right now
No. Replicate is operational.
No incidents reported.
Read from www.cloudflarestatus.com · every 120s
For agents
proceed
Proceed.
GET upbutler.com/status/replicate/status.agent.json
MCP: upstream_status {"service":"replicate"}
Run and fine-tune models through one API. Replicate reports its status on the Cloudflare status page since joining Cloudflare; this page shows only the Replicate component.
What Replicate reports
Operational
Taken as is from Replicate's own status page API. Incident titles and component names below are theirs. Narrowed to what concerns Replicate.
Open www.cloudflarestatus.comUpButler's independent probe
There is no keyless endpoint of Replicate that says anything useful, so UpButler does not probe it. To check your own Replicate account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Replicate components
1 operational
Cloudflare Sites and Services
- ReplicateOperational
Replicate incidents, last 90 days
1 finished incident seen since UpButler started tracking on 2026-10-10.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Replicate Flux Hotswap Models Stuck | minor | 18 min |
Tell your outage from Replicate's
Declare that your project depends on Replicate. When one of your monitors fails while Replicate has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- replicatecurl -s https://upbutler.com/status/replicate/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "replicate",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Replicate down right now?
- No. As of 2026-10-10 05:10 UTC, Replicate is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From Replicate's own status page API at https://www.cloudflarestatus.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Replicate's words. Their page covers more than this page shows; it is narrowed to the parts that concern Replicate.
- How can my agent or app check Replicate status?
- Fetch https://upbutler.com/status/replicate/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"replicate"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Replicate's?
- Add "replicate" to the dependencies of your UpButler workspace. When one of your monitors fails while Replicate has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in ai models and tooling
UpButler is not affiliated with Replicate. Status and incident text belong to Replicate and are read from their public status source; the probe result is UpButler's own measurement.