Skip to content

Outage tracker / Replicate

Is Replicate down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Replicate from all 10 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Replicate (since Aug 22, 2026).

our independent probeslive · checked Sep 5, 2026, 2:06 AM UTC
US-East109 msOperational
US-West191 msOperational
Europe155 msOperational
Asia-Pacific514 msOperational
US-Central268 msOperational
Canada312 msOperational
UK201 msOperational
Southeast Asia272 msOperational
Australia868 msOperational
South America618 msOperational
their status pagetheir claim, not our reading

Replicate reports: All systems operational (“All Systems Operational”)

from Replicate's own status page, checked Sep 5, 2026, 1:50 AM UTC
Our probes and Replicate's own status page agree: both show Replicate as reachable right now.

Replicate's own component breakdown, as they publish it

  • A100 HardwareOperational
  • H100 HardwareOperational
  • L40S HardwareOperational
  • BillingOperational
  • Support TicketsOperational
  • Streaming APIOperational
  • HTTP APIOperational
  • Replicate Registry (r8.im)Operational
  • CPU HardwareOperational
  • Home PageOperational
  • PlaygroundOperational
  • T4 HardwareOperational
  • Official ModelsOperational

These are Replicate's components, named and scored by Replicate. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Replicate's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Replicate response time, by region

US-East
396msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 666ms2026-08-23 UTC: p95 1.3s2026-08-24 UTC: p95 1.1s2026-08-25 UTC: p95 1.1s2026-08-26 UTC: p95 1.2s2026-08-27 UTC: p95 859ms2026-08-28 UTC: p95 943ms2026-08-29 UTC: p95 942ms2026-08-30 UTC: p95 980ms2026-08-31 UTC: p95 1.1s2026-09-01 UTC: p95 1.3s2026-09-02 UTC: p95 1.1s2026-09-03 UTC: p95 944ms2026-09-04 UTC: p95 401ms2026-09-05 UTC: p95 396ms
Aug 7Aug 21Sep 5
US-West
500msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 821ms2026-08-23 UTC: p95 450ms2026-08-24 UTC: p95 408ms2026-08-25 UTC: p95 730ms2026-08-26 UTC: p95 528ms2026-08-27 UTC: p95 458ms2026-08-28 UTC: p95 1.1s2026-08-29 UTC: p95 752ms2026-08-30 UTC: p95 786ms2026-08-31 UTC: p95 581ms2026-09-01 UTC: p95 372ms2026-09-02 UTC: p95 378ms2026-09-03 UTC: p95 337ms2026-09-04 UTC: p95 388ms2026-09-05 UTC: p95 500ms
Aug 7Aug 21Sep 5
Europe
204msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 742ms2026-08-23 UTC: p95 827ms2026-08-24 UTC: p95 638ms2026-08-25 UTC: p95 667ms2026-08-26 UTC: p95 617ms2026-08-27 UTC: p95 495ms2026-08-28 UTC: p95 439ms2026-08-29 UTC: p95 378ms2026-08-30 UTC: p95 417ms2026-08-31 UTC: p95 483ms2026-09-01 UTC: p95 434ms2026-09-02 UTC: p95 463ms2026-09-03 UTC: p95 389ms2026-09-04 UTC: p95 385ms2026-09-05 UTC: p95 204ms
Aug 7Aug 21Sep 5
Asia-Pacific
531msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 1.4s2026-08-23 UTC: p95 830ms2026-08-24 UTC: p95 545ms2026-08-25 UTC: p95 878ms2026-08-26 UTC: p95 634ms2026-08-27 UTC: p95 615ms2026-08-28 UTC: p95 858ms2026-08-29 UTC: p95 1.0s2026-08-30 UTC: p95 734ms2026-08-31 UTC: p95 802ms2026-09-01 UTC: p95 737ms2026-09-02 UTC: p95 993ms2026-09-03 UTC: p95 1.0s2026-09-04 UTC: p95 762ms2026-09-05 UTC: p95 531ms
Aug 7Aug 21Sep 5
US-Central
391msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 556ms2026-09-04 UTC: p95 475ms2026-09-05 UTC: p95 391ms
Aug 7Aug 21Sep 5
Canada
421msp95 · latest
500ms250ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 482ms2026-09-04 UTC: p95 482ms2026-09-05 UTC: p95 421ms
Aug 7Aug 21Sep 5
UK
198msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 555ms2026-09-04 UTC: p95 389ms2026-09-05 UTC: p95 198ms
Aug 7Aug 21Sep 5
Southeast Asia
270msp95 · latest
1s500ms0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 894ms2026-09-04 UTC: p95 792ms2026-09-05 UTC: p95 270ms
Aug 7Aug 21Sep 5
Australia
948msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 1.3s2026-09-05 UTC: p95 948ms
Aug 7Aug 21Sep 5
South America
615msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 599ms2026-09-05 UTC: p95 615ms
Aug 7Aug 21Sep 5

Is it Replicate, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Replicate -- it cannot diagnose Replicate's own systems.

What we measured, function by function

Replicate answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 109msstatus code: 401checked: Sep 5, 2026, 2:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Replicate normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 191msstatus code: 401checked: Sep 5, 2026, 2:01 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Replicate normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 268msstatus code: 401checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Replicate normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 312msstatus code: 401checked: Sep 5, 2026, 2:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Replicate normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 618msstatus code: 401checked: Sep 5, 2026, 1:34 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Replicate normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 155msstatus code: 401checked: Sep 5, 2026, 1:42 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Replicate normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 201msstatus code: 401checked: Sep 5, 2026, 1:39 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Replicate normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 514msstatus code: 401checked: Sep 5, 2026, 1:45 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Replicate normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 272msstatus code: 401checked: Sep 5, 2026, 1:12 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Replicate normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 868msstatus code: 401checked: Sep 5, 2026, 2:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Replicate normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Replicate, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Replicate yet, which is not evidence that nothing is wrong.

Recent outages

A100 hardware partial outage, 3h 8mdeclared on their status page2026-08-26
Delayed scaling due to node failure, 40mdeclared on their status page2026-08-10
Significant degradation, 2h 4mdeclared on their status page2026-08-05
API degraded for A100s, 9mdeclared on their status page2026-08-02
Degraded scale-out due to failed setups pulling from huggingface, 2h 15mdeclared on their status page2026-07-31
Hitting GPU Capacity for H100s creating large queue times for some models, 26h 29mdeclared on their status page2026-07-22
HuggingFace download issues, 7h 33mdeclared on their status page2026-07-16
H100 GPU shortage resulting in high queue times, 25h 1mdeclared on their status page2026-07-13

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Replicate since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Replicate covering any window you pick, with our measurements and Replicate's own claim at the time, side by side.

Full availability history for Replicate: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Replicate, and again when they can reach it again. That is our own measurement from ten regions, not Replicate's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Replicate uptime measured by RealUptimeLive, from this page's own readings.
[![Replicate uptime measured by RealUptime](https://realuptime.io/outages/replicate/badge.svg?days=30)](https://realuptime.io/outages/replicate)
<a href="https://realuptime.io/outages/replicate"><img src="https://realuptime.io/outages/replicate/badge.svg?days=30" alt="Replicate uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Replicate's SLA implies, from our measurement

At or above your target

We measured none of downtime for Replicate over the 338h 7m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Replicate's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.replicate.com/v1/models
secondary
https://replicate.com/
secondary
https://www.replicatestatus.com/api/v2/status.json
RealUptime is not affiliated with Replicate; the name identifies what we measured, and nothing here speaks for Replicate's own team. We send a single web request to Replicate from 10 regions on our own schedule and time the response. We do not see inside Replicate's systems, do not use an account or real transaction, and are not the same signal Replicate's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Replicate is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.