90 days uptime
100.000%
90 of 90 days clean · 0m total downtime
All windows
Last resolved incident
9 days ago · lasted 1h 13m · None
6/3/2026, 6:02:11 PM · resolved 6/3/2026, 7:15:21 PM · Resolved
5/28/2026, 12:35:25 PM · resolved 5/28/2026, 2:25:18 PM · Resolved
5/21/2026, 9:40:04 PM · resolved 5/21/2026, 11:30:13 PM · Resolved
5/21/2026, 3:10:03 PM · resolved 5/21/2026, 10:10:05 PM · Resolved
1signal across 1 source
synthetic_probe 1
Official status page: https://www.replicatestatus.com (opens in new tab)
Live status pill for Replicate. Updates automatically — no maintenance, no API key.
PREVIEW
Drop into any HTML page — README, docs, vendor homepage. No iframe, no dependencies.
<script src="https://checkupstream.com/embed/badge.js?service=replicate"></script>Self-contained, CSP-friendly. Theme + size are query params; revalidates every 60s.
<iframe src="https://checkupstream.com/embed/replicate" style="border:0;width:260px;height:44px" loading="lazy" title="Replicate status badge"></iframe>GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
[](https://checkupstream.com/reliability/replicate)Useful for status-page composers (Notion, Slab, custom dashboards) that accept image URLs.
https://checkupstream.com/embed/replicate/badge.svgReplicate is currently Operational. CheckUpstream tracks Replicate in real-time across the official status page, RSS / Atom feeds, and community telemetry — refresh this page for the latest reading.
Replicate's last resolved incident started 9 days ago and lasted 1h 13m (an incident).
Looking for the live "is Replicate down" view? See the Replicate Status page.
5/12/2026, 3:30:29 PM · resolved 5/12/2026, 7:50:20 PM · Resolved
Replicate's 30-day customer-perceived uptime is 100.000%. The figure is weighted (full-outage = 1.0, degraded = 0.3) so component blips don't collapse the score the way a raw incident-count would.
Sign up to CheckUpstream and add Replicate to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection — covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Replicate's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.