Replicate Outage Check
Is Replicate Down Right Now?
✅ Replicate is up and working normally. Checked: 5:10 PM (GMT+8).
Auto-refreshing live data in 60s
| Component | Status |
|---|---|
| A100 Hardware | Operational |
| Billing | Operational |
| CPU Hardware | Operational |
| H100 Hardware | Operational |
| Home Page | Operational |
| HTTP API | Operational |
| L40S Hardware | Operational |
| Official Models | Operational |
| Playground | Operational |
| Replicate Registry (r8.im) | Operational |
| Streaming API | Operational |
| Support Tickets | Operational |
| T4 Hardware | Operational |
99.556%
Uptime
56m
MTTR
6.7
Avg Incidents / Mo
90 Days AgoToday
Replicate API Gateway Timeout and Increased Error Rates
Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.
Duration: 33m
Affected: API Requests, API Portal
Replicate Database Failover and Connection Backlog
A hardware failure on the primary database cluster triggered an automatic failover to the replica.
Duration: 54m
Affected: Core Service, Website
Replicate Database Failover and Connection Backlog
A hardware failure on the primary database cluster triggered an automatic failover to the replica.
Duration: 46m
Affected: Core Service, Website
Replicate Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 1h 8m
Affected: Website, DNS Services
Replicate API Gateway Timeout and Increased Error Rates
Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.
Duration: 43m
Affected: API Requests, API Portal
Are you having problems with Replicate?
Submit your report to help alert other developers.
Downtime Reports: Last 2 Hours
2 Hours AgoNow
Troubleshooting Guide
- 1Hard RefreshBypass cache (Ctrl+F5 or Cmd+Shift+R).
- 2Flush DNSRun
ipconfig /flushdns.
Uptime Alternatives
GitHub
Leading developer platform.
Slack
Real-time team communication.
Yes, Replicate maintains an official status page. However, our real-time tracker aggregates reports faster.
Historical records indicate that the mean time to resolve (MTTR) is approximately 56 minutes.
Outages can happen due to configuration mistakes, database freezes, edge network issues, or infrastructure drops.
You can subscribe to live alerts on this page. We send emails on status updates.
Try bypass caching by executing hard refresh, flush local DNS, or use alternatives listed below.