Is Replicate down?
Vendor reports no incidentWhat Replicate reports
Replicate reports no incident on its status page.
As of the last successful poll, 2026-10-22 22:38 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingchecked 4 minutes ago
Our checks of Replicate pass from all 10 regions we check.
As of Oct 22, 2026, 10:41 PM UTC, RealUptime's checks of Replicate passed in all 10 regions that returned a reading.
Replicate reports: Partial outage (“Partial System Outage”)
Replicate's own component breakdown, as they publish it
- Abuse ReportsOperational
- Accra, Ghana - (ACC)Degraded performance
- Adelaide, SA, Australia - (ADL)Operational
- Ahmedabad, India - (AMD)Operational
- Albuquerque, NM, United States - (ABQ)Operational
- Americana, Brazil - (QWJ)Operational
- Amman, Jordan - (AMM)Degraded performance
- Amsterdam, Netherlands - (AMS)Operational
- AccessOperational
- Algiers, Algeria - (ALG)Operational
- Almaty, Kazakhstan - (ALA)Operational
- Anchorage, AK, United States - (ANC)Operational
- Arica, Chile - (ARI)Major outage
- Astara, Azerbaijan - (LLK)Operational
- Athens, Greece - (ATH)Operational
- Auckland, New Zealand - (AKL)Operational
- Account ManagementOperational
- Annaba, Algeria - (AAE)Major outage
- Ashburn, VA, United States - (IAD)Operational
- Asunción, Paraguay - (ASU)Operational
- Baghdad, Iraq - (BGW)Degraded performance
- Barcelona, Spain - (BCN)Operational
- Brisbane, QLD, Australia - (BNE)Operational
- AI GatewayOperational
- Antananarivo, Madagascar - (TNR)Operational
- Atlanta, GA, United States - (ATL)Operational
- Baku, Azerbaijan - (GYD)Degraded performance
- Bangalore, India - (BLR)Degraded performance
- Belgrade, Serbia - (BEG)Operational
- Belém, Brazil - (BEL)Operational
- Canberra, ACT, Australia - (CBR)Major outage
- AI SearchOperational
- Austin, TX, United States - (AUS)Operational
- Bangkok, Thailand - (BKK)Operational
- Basra, Iraq - (BSR)Operational
- Belo Horizonte, Brazil - (CNF)Degraded performance
- Berlin, Germany - (TXL)Operational
- Cape Town, South Africa - (CPT)Operational
- Christchurch, New Zealand - (CHC)Operational
- Always OnlineOperational
- Bandar Seri Begawan, Brunei - (BWN)Major outage
- Bangor, ME, United States - (BGR)Operational
- Beirut, Lebanon - (BEY)Operational
- Bordeaux, France - (BOD)Operational
- Hagatna, Guam - (GUM)Major outage
- AnalyticsOperational
- Bogotá, Colombia - (BOG)Degraded performance
- Boston, MA, United States - (BOS)Operational
- Bratislava, Slovakia - (BTS)Operational
- Dakar, Senegal - (DKR)Operational
- Dammam, Saudi Arabia - (DMM)Operational
- APIOperational
- Brasilia, Brazil - (BSB)Operational
- Brussels, Belgium - (BRU)Operational
- Dar Es Salaam, Tanzania - (DAR)Degraded performance
- Doha, Qatar - (DOH)Operational
- Melbourne, VIC, Australia - (MEL)Operational
- API ShieldOperational
- Bucharest, Romania - (OTP)Operational
- Buenos Aires, Argentina - (EZE)Operational
- Calgary, AB, Canada - (YYC)Operational
- Cebu, Philippines - (CEB)Operational
- Djibouti City, Djibouti - (JIB)Operational
- Dubai, United Arab Emirates - (DXB)Degraded performance
- Noumea, New Caledonia - (NOU)Operational
- Apps MarketplaceOperational
- Budapest, Hungary - (BUD)Operational
- Caçador, Brazil - (CFC)Operational
- Chandigarh, India - (IXC)Operational
- Charlotte, NC, United States - (CLT)Operational
- Durban, South Africa - (DUR)Operational
- Erbil, Iraq - (EBL)Degraded performance
- Perth, WA, Australia - (PER)Operational
- Area 1 - APIOperational
- Campinas, Brazil - (VCP)Operational
- Changde, China - (CGD)Operational
- Chicago, IL, United States - (ORD)Operational
- Chișinău, Moldova - (KIV)Operational
- Gaborone, Botswana - (GBE)Degraded performance
- Haifa, Israel - (HFA)Operational
- Sydney, NSW, Australia - (SYD)Degraded performance
- Area 1 - DashOperational
- Chennai, India - (MAA)Operational
- Cleveland, OH, United States - (CLE)Operational
- Copenhagen, Denmark - (CPH)Operational
- Harare, Zimbabwe - (HRE)Operational
- Jeddah, Saudi Arabia - (JED)Operational
- Tahiti, French Polynesia - (PPT)Operational
- ArtifactsOperational
- Columbus, OH, United States - (CMH)Operational
- Córdoba, Argentina - (COR)Operational
- Dublin, Ireland - (DUB)Operational
- Johannesburg, South Africa - (JNB)Operational
- Kuwait City, Kuwait - (KWI)Operational
- Suva, Fiji - (SUV)Operational
- Chittagong, Bangladesh - (CGP)Operational
- Dallas, TX, United States - (DFW)Operational
- Düsseldorf, Germany - (DUS)Operational
- Kigali, Rwanda - (KGL)Operational
- Manama, Bahrain - (BAH)Degraded performance
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
Check your own site while you wait on Replicate
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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
Email me when Replicate reports an incident on its status page, and again when it reports it resolved.
Get an email when Replicate reports an incident
Email me when Replicate reports an incident on its status page, and again when it reports it resolved. No account, no card.
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 819msstatus code: 401checked: Oct 22, 2026, 10:21 PM UTC0 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-WestChecks passinglatency: 313msstatus code: 401checked: Oct 22, 2026, 10:33 PM UTC0 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-CentralChecks passinglatency: 497msstatus code: 401checked: Oct 22, 2026, 9:47 PM UTC0 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.
- CanadaChecks passinglatency: 101msstatus code: 401checked: Oct 22, 2026, 10:25 PM UTC0 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 AmericaChecks passinglatency: 419msstatus code: 401checked: Oct 22, 2026, 10:33 PM UTC0 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.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 650msstatus code: 401checked: Oct 22, 2026, 10:20 PM UTC0 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.
- UKChecks passinglatency: 690msstatus code: 401checked: Oct 22, 2026, 10:41 PM UTC0 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 PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 893msstatus code: 401checked: Oct 22, 2026, 10:41 PM UTC0 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 AsiaChecks passinglatency: 643msstatus code: 401checked: Oct 22, 2026, 10:30 PM UTC0 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.
- AustraliaChecks passinglatency: 281msstatus code: 401checked: Oct 22, 2026, 10:33 PM UTC0 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 probe events
check 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 check readings and Replicate's own claim at the time, side by side.
Full check history for Replicate: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 serversPut this badge in your README
Live, from this page's own readings.[](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 by RealUptime's checks" height="20"></a>The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
To cite this page: RealUptime, "Is Replicate down?", https://realuptime.io/outages/replicate. The readings change with every check, so give the date you read them.
Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.
What we check
What our check can and cannot see
A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.
Host checked: api.replicate.com