Skip to main content
down.guideby Sazabi
Providers
Is Replicate down? · AI

Replicate is degraded

DegradedSince : Changes to Cloudflare Workers are not producing Event Subscription events

99.99% uptime, 90 days · 99.99% over 12 monthsLast incident Checked Official status pageHistory

Reports count in aggregate against normal levels; one alone never makes a claim.

Now

Open incidents

What Replicate has posted and not resolved.

  1. ReplicateDegradedOngoing
    Changes to Cloudflare Workers are not producing Event Subscription events
    ongoing for 23h 19mWorkers, Queues
Minor

Minor or regional issues (1)

Open issues confined to one country, region, site, carrier route, asset or slice of customers. Replicate's state, uptime and the Down Index leave them out.

  1. ReplicateDegradedOngoing
    Fedramp Customers have Delayed Purges

    Replicate says a bug in its purge pipeline is delaying purges for FedRAMP customers, so stale content may be served until it expires. Non-FedRAMP customers are not affected. The issue is identified, and the provider says it is still working on a fix.

    ongoing for 4d 7hCDN Cache Purge
Planned

Maintenance

Scheduled or in progress.

  1. ReplicateMaintenanceOngoing
    ARN (Stockholm) on 2026-11-11
    ongoing for 13mStockholm, Sweden - (ARN)eu, us
  2. ReplicateMaintenanceOngoing
    BKK (Bangkok) on 2026-11-10
    ongoing for 8h 13mBangkok, Thailand - (BKK)us
  3. ReplicateMaintenanceOngoing
    MSP (Minneapolis) on 2026-11-05
    ongoing for 5d 17hMinneapolis, United States - (MSP)us
90 days

Daily history

Worst impact each day, from the provider's own incidents.

  1. 2026-08-14: no incidents
  2. 2026-08-15: no incidents
  3. 2026-08-16: no incidents
  4. 2026-08-17: no incidents
  5. 2026-08-18: no incidents
  6. 2026-08-19: no incidents
  7. 2026-08-20: no incidents
  8. 2026-08-21: no incidents
  9. 2026-08-22: no incidents
  10. 2026-08-23: no incidents
  11. 2026-08-24: no incidents
  12. 2026-08-25: no incidents
  13. 2026-08-26: no incidents
  14. 2026-08-27: no incidents
  15. 2026-08-28: no incidents
  16. 2026-08-29: no incidents
  17. 2026-08-30: no incidents
  18. 2026-08-31: no incidents
  19. 2026-09-01: no incidents
  20. 2026-09-02: no incidents
  21. 2026-09-03: no incidents
  22. 2026-09-04: no incidents
  23. 2026-09-05: no incidents
  24. 2026-09-06: no incidents
  25. 2026-09-07: no incidents
  26. 2026-09-08: no incidents
  27. 2026-09-09: no incidents
  28. 2026-09-10: no incidents
  29. 2026-09-11: no incidents
  30. 2026-09-12: no incidents
  31. 2026-09-13: no incidents
  32. 2026-09-14: 1 incident, worst degraded
  33. 2026-09-15: 1 incident, worst degraded
  34. 2026-09-16: no incidents
  35. 2026-09-17: 1 incident, worst degraded
  36. 2026-09-18: no incidents
  37. 2026-09-19: no incidents
  38. 2026-09-20: no incidents
  39. 2026-09-21: no incidents
  40. 2026-09-22: no incidents
  41. 2026-09-23: no incidents
  42. 2026-09-24: 1 incident, worst degraded
  43. 2026-09-25: no incidents
  44. 2026-09-26: no incidents
  45. 2026-09-27: no incidents
  46. 2026-09-28: 1 incident, worst degraded
  47. 2026-09-29: no incidents
  48. 2026-09-30: no incidents
  49. 2026-10-01: no incidents
  50. 2026-10-02: no incidents
  51. 2026-10-03: no incidents
  52. 2026-10-04: no incidents
  53. 2026-10-05: no incidents
  54. 2026-10-06: no incidents
  55. 2026-10-07: no incidents
  56. 2026-10-08: no incidents
  57. 2026-10-09: no incidents
  58. 2026-10-10: no incidents
  59. 2026-10-11: no incidents
  60. 2026-10-12: no incidents
  61. 2026-10-13: no incidents
  62. 2026-10-14: no incidents
  63. 2026-10-15: no incidents
  64. 2026-10-16: no incidents
  65. 2026-10-17: no incidents
  66. 2026-10-18: no incidents
  67. 2026-10-19: no incidents
  68. 2026-10-20: no incidents
  69. 2026-10-21: no incidents
  70. 2026-10-22: no incidents
  71. 2026-10-23: 2 incidents, worst degraded
  72. 2026-10-24: 1 incident, worst degraded
  73. 2026-10-25: no incidents
  74. 2026-10-26: 3 incidents, worst degraded
  75. 2026-10-27: 4 incidents, worst partial outage
  76. 2026-10-28: 1 incident, worst degraded
  77. 2026-10-29: 5 incidents, worst degraded
  78. 2026-10-30: 2 incidents, worst degraded
  79. 2026-10-31: 1 incident, worst degraded
  80. 2026-11-01: 1 incident, worst degraded
  81. 2026-11-02: 3 incidents, worst degraded
  82. 2026-11-03: 6 incidents, worst degraded
  83. 2026-11-04: 2 incidents, worst degraded
  84. 2026-11-05: 1 incident, worst degraded
  85. 2026-11-06: 1 incident, worst degraded
  86. 2026-11-07: no incidents
  87. 2026-11-08: no incidents
  88. 2026-11-09: 2 incidents, worst degraded
  89. 2026-11-10: 4 incidents, worst degraded
  90. 2026-11-11: 1 incident, worst degraded
90 days agoToday

Daily history for the 12 components with the most incident days. Every component's current state is in the Markdown copy.

Reliability

Last 90 days in numbers

From the provider's own posts, including history read from its archive.

Uptime
99.99%12 months
Incidents
61on 22 days
Median duration
1h 33m
Longest
18d 8h
Postmortem rate
n/apartial and major outages
Reports

People reporting problems

Hourly counts, last 24 hours.

No reports in the last 24 hours.

Follow Replicate incidents

Following several providers? Check your stack to get one feed for all of them.

https://down.guide/feed?provider=replicate
Open feed

In Slack, install the RSS app and run /feed subscribe https://down.guide/feed?provider=replicate in a channel. In Discord, add a feed bot such as MonitoRSS and give it this URL. Or paste it into Feedly or any RSS reader.

https://down.guide/feed?provider=replicate&format=atom
Open feed

The same entries as Atom, for readers that prefer it.

https://down.guide/feed?provider=replicate&format=json
Open feed

The same entries as JSON Feed 1.1, each with the full incident under _down_guide, for scripts.

https://down.guide/api/v1/incidents?provider=replicate
Open feed

Pages of 30 incidents, newest first. Pass the response's next_cursor as cursor for the next page.

History

Recent incidents

The last 90 days.

All history
  1. ReplicateDegraded
    Network Performance Issues in St. Louis, USA

    Replicate says network performance issues in St. Louis, USA are affected, and the incident is in monitoring status. The provider says Cloudflare identified the issues in the St. Louis (STL) location, a fix has been implemented, and results are being monitored.

    lasted 2h 20mSt. Louis, United States - (STL)us
  2. ReplicateDegraded
    Prediction issue on OpenAI models via Replicate
    lasted 31mReplicate
  3. ReplicateMaintenance
    SYD (Sydney) on 2026-11-10
    lasted 6h 2mSydney, Australia - (SYD)au, us
  4. ReplicateMaintenance
    SLC (Salt Lake City) on 2026-11-10
    lasted 4h 2mSalt Lake City, United States - (SLC)us
  5. ReplicateMaintenance
    SJC (San Jose) on 2026-11-10
    lasted 6h 2mSan Jose, United States - (SJC)us
  6. ReplicateDegraded
    Account Analytics Filter Issue
    lasted 43mAnalytics
  7. ReplicateMaintenance
    EWR (Newark) on 2026-11-10
    lasted 1h 31mNewark, United States - (EWR)us
  8. ReplicateMaintenance
    BOG (Bogotá) on 2026-11-10

    Replicate says scheduled maintenance at its BOG (Bogotá) datacenter began on 2026-11-10 at 05:00 UTC and is in progress, with a planned window of 05:00 to 11:00 UTC. Traffic may be re-routed, so latency may slightly increase for end-users in the region, and PNI/CNI customers may see traffic fail over elsewhere.

    lasted 6h 2mBogotá, Colombia - (BOG)us
  9. ReplicateMaintenance
    LHR (London) on 2026-11-10
    lasted 3h 1mLondon, United Kingdom - (LHR)eu, us
  10. ReplicateMaintenance
    VIE (Vienna) on 2026-11-10
    lasted 6h 1mVienna, Austria - (VIE)us
  11. ReplicateMaintenance
    DFW (Dallas) on 2026-11-09
    lasted 4h 41mDallas, United States - (DFW)us
  12. ReplicateDegraded
    Network Performance Issues in Eastern North America
    lasted 3h 38mNetworkus
  13. ReplicateDegraded
    Changes made to Workers may be delayed or disrupted

    Replicate says creating, editing and deleting Workers is affected, so changes to Workers may be delayed or disrupted. Workers that are already deployed are unaffected. The current status is monitoring, and the provider says it is continuing to monitor for further issues.

    lasted 9h 31mWorkers
  14. ReplicateDegraded
    Spectrum Availability issues
    lasted 5mSpectrum
  15. ReplicateMaintenance
    PDX (Portland) on 2026-11-09
    lasted 1h 1mPortland, United States - (PDX)us

Replicate status: questions

Is Replicate down right now?

Replicate reports degraded performance (checked 2026-11-11 01:12 UTC from Replicate's official status page). Open: Changes to Cloudflare Workers are not producing Event Subscription events.

What is Replicate's uptime?

99.99% over the last 90 days and 99.99% over 12 months, from the incidents Replicate posted on its own status page. A major outage counts in full and a partial outage as 30% of its time, per component.

When was Replicate's last outage?

Network Performance Issues in St. Louis, USA, starting 2026-11-10 22:50 UTC and lasting 2h 20m: https://down.guide/DWN-dd756bec4d

How do I get alerts when Replicate goes down?

Subscribe to https://down.guide/feed?provider=replicate (RSS; add format=atom or format=json). In Slack, install the RSS app and run /feed subscribe with that URL; in Discord, give it to a feed bot such as MonitoRSS. No account needed.

Where does down.guide get Replicate's status?

From Replicate's official status page, https://www.cloudflarestatus.com, read every minute. Replicate's words are quoted verbatim and linked.