‹ Back to incident history

Status page migration

ResolvedMinor incidentReplicate
Thursday, September 10, 2026 20:00 – Friday, September 11, 2026 20:00 (24 hr)
Affected components
Inference and Training / L40S Hardware
API / Streaming API
API / HTTP API
Inference and Training / T4 Hardware
Inference and Training / CPU Hardware
Official Models
Inference and Training / H100 Hardware
Inference and Training / A100 Hardware
Support / Billing
Support / Support Tickets
Replicate Registry (r8.im)
Website / Home Page
Website / Playground
Updates
CompletedFriday, September 11, 2026 12:00

Maintenance has completed

maintenance_in_progressThursday, September 10, 2026 12:05

The migration is complete. If you can read this, it's probably a DNS thing.

maintenance_in_progressThursday, September 10, 2026 12:00

Maintenance has started

maintenance_scheduledWednesday, September 9, 2026 02:25

We are migrating all status page capabilities to cloudflarestatus.com. Redirects should be automatic, but please be sure to update your subscriptions, automations, links, and anything else that may reference replicatestatus.com or status.replicate.com.

Incident data from the Replicate official status page:Read the official incident

About this data

Where does the incident data for Replicate come from?

Data comes from the Replicate official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.

How do I read the component status bars?

Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.

Why is history missing for some services?

Only services with a public official status page are included.

How is duration calculated?

Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.

See the full service list and live status in the status overview