Skip to content

Outage tracker / Replicate

Is Replicate down?

I'm having a problem

Operationalchecked 8 minutes ago

We reached Replicate from all 10 regions we check.

As of Oct 5, 2026, 8:07 PM UTC, Replicate answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

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

our independent probeslive · checked Oct 5, 2026, 8:07 PM UTC
US-East310 msOperational
US-West262 msOperational
Europe308 msOperational
Asia-Pacific519 msOperational
US-Central400 msOperational
Canada380 msOperational
UK222 msOperational
Southeast Asia398 msOperational
Australia712 msOperational
South America581 msOperational
their status pagetheir claim, not our reading

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

from Replicate's own status page, checked Sep 10, 2026, 3:28 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 (our last read of their page failed, so this is the previous reading)

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

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
406msp95 · latest
500ms250ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 273ms2026-09-07 UTC: p95 291ms2026-09-08 UTC: p95 254ms2026-09-09 UTC: p95 243ms2026-09-10 UTC: p95 250ms2026-09-11 UTC: p95 300ms2026-09-12 UTC: p95 290ms2026-09-13 UTC: p95 422ms2026-09-14 UTC: p95 294ms2026-09-15 UTC: p95 303ms2026-09-16 UTC: p95 455ms2026-09-17 UTC: p95 365ms2026-09-18 UTC: p95 372ms2026-09-19 UTC: p95 389ms2026-09-20 UTC: p95 359ms2026-09-21 UTC: p95 324ms2026-09-22 UTC: p95 368ms2026-09-23 UTC: p95 398ms2026-09-24 UTC: p95 401ms2026-09-25 UTC: p95 373ms2026-09-26 UTC: p95 349ms2026-09-27 UTC: p95 325ms2026-09-28 UTC: p95 445ms2026-09-29 UTC: p95 439ms2026-09-30 UTC: p95 358ms2026-10-01 UTC: p95 444ms2026-10-02 UTC: p95 426ms2026-10-03 UTC: p95 377ms2026-10-04 UTC: p95 347ms2026-10-05 UTC: p95 406ms
Sep 6Sep 20Oct 5
US-West
389msp95 · latest
500ms250ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 227ms2026-09-07 UTC: p95 212ms2026-09-08 UTC: p95 161ms2026-09-09 UTC: p95 199ms2026-09-10 UTC: p95 289ms2026-09-11 UTC: p95 176ms2026-09-12 UTC: p95 338ms2026-09-13 UTC: p95 170ms2026-09-14 UTC: p95 444ms2026-09-15 UTC: p95 417ms2026-09-16 UTC: p95 163ms2026-09-17 UTC: p95 161ms2026-09-18 UTC: p95 173ms2026-09-19 UTC: p95 166ms2026-09-20 UTC: p95 157ms2026-09-21 UTC: p95 169ms2026-09-22 UTC: p95 190ms2026-09-23 UTC: p95 153ms2026-09-24 UTC: p95 203ms2026-09-25 UTC: p95 329ms2026-09-26 UTC: p95 312ms2026-09-27 UTC: p95 247ms2026-09-28 UTC: p95 334ms2026-09-29 UTC: p95 327ms2026-09-30 UTC: p95 289ms2026-10-01 UTC: p95 370ms2026-10-02 UTC: p95 293ms2026-10-03 UTC: p95 305ms2026-10-04 UTC: p95 341ms2026-10-05 UTC: p95 389ms
Sep 6Sep 20Oct 5
Europe
414msp95 · 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-09-06 UTC: p95 598ms2026-09-07 UTC: p95 378ms2026-09-08 UTC: p95 509ms2026-09-09 UTC: p95 475ms2026-09-10 UTC: p95 471ms2026-09-11 UTC: p95 509ms2026-09-12 UTC: p95 555ms2026-09-13 UTC: p95 478ms2026-09-14 UTC: p95 585ms2026-09-15 UTC: p95 526ms2026-09-16 UTC: p95 488ms2026-09-17 UTC: p95 512ms2026-09-18 UTC: p95 519ms2026-09-19 UTC: p95 539ms2026-09-20 UTC: p95 551ms2026-09-21 UTC: p95 486ms2026-09-22 UTC: p95 569ms2026-09-23 UTC: p95 573ms2026-09-24 UTC: p95 676ms2026-09-25 UTC: p95 591ms2026-09-26 UTC: p95 612ms2026-09-27 UTC: p95 525ms2026-09-28 UTC: p95 551ms2026-09-29 UTC: p95 500ms2026-09-30 UTC: p95 502ms2026-10-01 UTC: p95 467ms2026-10-02 UTC: p95 530ms2026-10-03 UTC: p95 489ms2026-10-04 UTC: p95 431ms2026-10-05 UTC: p95 414ms
Sep 6Sep 20Oct 5
Asia-Pacific
649msp95 · 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-09-06 UTC: p95 831ms2026-09-07 UTC: p95 717ms2026-09-08 UTC: p95 769ms2026-09-09 UTC: p95 812ms2026-09-10 UTC: p95 677ms2026-09-11 UTC: p95 850ms2026-09-12 UTC: p95 686ms2026-09-13 UTC: p95 798ms2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 813ms2026-09-16 UTC: p95 625ms2026-09-17 UTC: p95 667ms2026-09-18 UTC: p95 725ms2026-09-19 UTC: p95 761ms2026-09-20 UTC: p95 730ms2026-09-21 UTC: p95 636ms2026-09-22 UTC: p95 728ms2026-09-23 UTC: p95 663ms2026-09-24 UTC: p95 800ms2026-09-25 UTC: p95 639ms2026-09-26 UTC: p95 756ms2026-09-27 UTC: p95 672ms2026-09-28 UTC: p95 741ms2026-09-29 UTC: p95 694ms2026-09-30 UTC: p95 781ms2026-10-01 UTC: p95 691ms2026-10-02 UTC: p95 568ms2026-10-03 UTC: p95 595ms2026-10-04 UTC: p95 743ms2026-10-05 UTC: p95 649ms
Sep 6Sep 20Oct 5
US-Central
455msp95 · 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-06 UTC: p95 529ms2026-09-07 UTC: p95 422ms2026-09-08 UTC: p95 589ms2026-09-09 UTC: p95 569ms2026-09-10 UTC: p95 609ms2026-09-11 UTC: p95 518ms2026-09-12 UTC: p95 422ms2026-09-13 UTC: p95 494ms2026-09-14 UTC: p95 501ms2026-09-15 UTC: p95 496ms2026-09-16 UTC: p95 454ms2026-09-17 UTC: p95 477ms2026-09-18 UTC: p95 450ms2026-09-19 UTC: p95 431ms2026-09-20 UTC: p95 460ms2026-09-21 UTC: p95 515ms2026-09-22 UTC: p95 412ms2026-09-23 UTC: p95 487ms2026-09-24 UTC: p95 450ms2026-09-25 UTC: p95 428ms2026-09-26 UTC: p95 574ms2026-09-27 UTC: p95 663ms2026-09-28 UTC: p95 539ms2026-09-29 UTC: p95 436ms2026-09-30 UTC: p95 551ms2026-10-01 UTC: p95 457ms2026-10-02 UTC: p95 452ms2026-10-03 UTC: p95 527ms2026-10-04 UTC: p95 506ms2026-10-05 UTC: p95 455ms
Sep 6Sep 20Oct 5
Canada
405msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 587ms2026-09-07 UTC: p95 419ms2026-09-08 UTC: p95 468ms2026-09-09 UTC: p95 385ms2026-09-10 UTC: p95 434ms2026-09-11 UTC: p95 522ms2026-09-12 UTC: p95 375ms2026-09-13 UTC: p95 404ms2026-09-14 UTC: p95 448ms2026-09-15 UTC: p95 364ms2026-09-16 UTC: p95 407ms2026-09-17 UTC: p95 509ms2026-09-18 UTC: p95 486ms2026-09-19 UTC: p95 454ms2026-09-20 UTC: p95 462ms2026-09-21 UTC: p95 498ms2026-09-22 UTC: p95 491ms2026-09-23 UTC: p95 480ms2026-09-24 UTC: p95 480ms2026-09-25 UTC: p95 425ms2026-09-26 UTC: p95 427ms2026-09-27 UTC: p95 423ms2026-09-28 UTC: p95 387ms2026-09-29 UTC: p95 437ms2026-09-30 UTC: p95 441ms2026-10-01 UTC: p95 408ms2026-10-02 UTC: p95 428ms2026-10-03 UTC: p95 457ms2026-10-04 UTC: p95 384ms2026-10-05 UTC: p95 405ms
Sep 6Sep 20Oct 5
UK
464msp95 · 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-06 UTC: p95 338ms2026-09-07 UTC: p95 420ms2026-09-08 UTC: p95 476ms2026-09-09 UTC: p95 398ms2026-09-10 UTC: p95 453ms2026-09-11 UTC: p95 367ms2026-09-12 UTC: p95 499ms2026-09-13 UTC: p95 408ms2026-09-14 UTC: p95 474ms2026-09-15 UTC: p95 398ms2026-09-16 UTC: p95 376ms2026-09-17 UTC: p95 424ms2026-09-18 UTC: p95 360ms2026-09-19 UTC: p95 409ms2026-09-20 UTC: p95 449ms2026-09-21 UTC: p95 512ms2026-09-22 UTC: p95 513ms2026-09-23 UTC: p95 515ms2026-09-24 UTC: p95 616ms2026-09-25 UTC: p95 461ms2026-09-26 UTC: p95 546ms2026-09-27 UTC: p95 500ms2026-09-28 UTC: p95 440ms2026-09-29 UTC: p95 587ms2026-09-30 UTC: p95 449ms2026-10-01 UTC: p95 442ms2026-10-02 UTC: p95 546ms2026-10-03 UTC: p95 478ms2026-10-04 UTC: p95 434ms2026-10-05 UTC: p95 464ms
Sep 6Sep 20Oct 5
Southeast Asia
1.1sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.5s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.7s2026-09-23 UTC: p95 1.9s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 845ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 881ms2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
Australia
864msp95 · 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-06 UTC: p95 1.2s2026-09-07 UTC: p95 827ms2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 801ms2026-09-10 UTC: p95 788ms2026-09-11 UTC: p95 918ms2026-09-12 UTC: p95 975ms2026-09-13 UTC: p95 954ms2026-09-14 UTC: p95 884ms2026-09-15 UTC: p95 901ms2026-09-16 UTC: p95 911ms2026-09-17 UTC: p95 948ms2026-09-18 UTC: p95 936ms2026-09-19 UTC: p95 897ms2026-09-20 UTC: p95 888ms2026-09-21 UTC: p95 963ms2026-09-22 UTC: p95 779ms2026-09-23 UTC: p95 715ms2026-09-24 UTC: p95 722ms2026-09-25 UTC: p95 780ms2026-09-26 UTC: p95 774ms2026-09-27 UTC: p95 902ms2026-09-28 UTC: p95 935ms2026-09-29 UTC: p95 956ms2026-09-30 UTC: p95 866ms2026-10-01 UTC: p95 867ms2026-10-02 UTC: p95 788ms2026-10-03 UTC: p95 718ms2026-10-04 UTC: p95 838ms2026-10-05 UTC: p95 864ms
Sep 6Sep 20Oct 5
South America
669msp95 · 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-06 UTC: p95 648ms2026-09-07 UTC: p95 582ms2026-09-08 UTC: p95 609ms2026-09-09 UTC: p95 680ms2026-09-10 UTC: p95 596ms2026-09-11 UTC: p95 619ms2026-09-12 UTC: p95 643ms2026-09-13 UTC: p95 641ms2026-09-14 UTC: p95 627ms2026-09-15 UTC: p95 597ms2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 931ms2026-09-21 UTC: p95 629ms2026-09-22 UTC: p95 564ms2026-09-23 UTC: p95 571ms2026-09-24 UTC: p95 737ms2026-09-25 UTC: p95 671ms2026-09-26 UTC: p95 665ms2026-09-27 UTC: p95 746ms2026-09-28 UTC: p95 714ms2026-09-29 UTC: p95 763ms2026-09-30 UTC: p95 723ms2026-10-01 UTC: p95 758ms2026-10-02 UTC: p95 762ms2026-10-03 UTC: p95 834ms2026-10-04 UTC: p95 763ms2026-10-05 UTC: p95 669ms
Sep 6Sep 20Oct 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

Get an email when we see Replicate go down, and when it is back

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.

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: 310msstatus code: 401checked: Oct 5, 2026, 7:50 PM 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: 262msstatus code: 401checked: Oct 5, 2026, 8:07 PM 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: 400msstatus code: 401checked: Oct 5, 2026, 7:20 PM 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: 380msstatus code: 401checked: Oct 5, 2026, 7:32 PM 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: 581msstatus code: 401checked: Oct 5, 2026, 7:55 PM 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: 308msstatus code: 401checked: Oct 5, 2026, 7:51 PM 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: 222msstatus code: 401checked: Oct 5, 2026, 7:55 PM 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: 519msstatus code: 401checked: Oct 5, 2026, 8:06 PM 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: 398msstatus code: 401checked: Oct 5, 2026, 7:47 PM 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: 712msstatus code: 401checked: Oct 5, 2026, 7:54 PM 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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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.