Status updated

All Systems Operational
Replicate logo

Replicate down?

This is the public status page for Replicate, the cloud platform that lets developers run and fine-tune machine learning models through a simple API. The page shows the current operational status of Replicate's services, such as the API, model predictions, training, the website and GPU capacity. It posts updates about ongoing incidents, degraded performance and planned maintenance, along with a history of past events. Developers building AI features on Replicate use it to verify whether errors or slowdowns come from the platform and to subscribe to notifications.

Replicate status preview image

I have a problem with Replicate

Select the type of problem you're facing to help us and other users.

Recent User Report Trends for Replicate

Aggregated reports in the last 48 hours.

What is Replicate's current status?

All systems are operational

No active incidents reported.

Incident history: past 7 days

times in UTC

Today

No incidents reported.

Yesterday

No incidents reported.

Oct 30, 2026

No incidents reported.

Oct 29, 2026

No incidents reported.

Oct 28, 2026

No incidents reported.

Oct 27, 2026

No incidents reported.

Oct 26, 2026

No incidents reported.

User Reports for Replicate

Recent issues reported by users from around the world.

Experiencing an issue? Add your report:

Stop refreshing this page

We'll email you the moment Replicate goes down — and again when it's back.

How to fix Replicate not working

Replicate runs machine learning models through an API, so a failing prediction can stop an AI feature in your product. Start by checking whether Replicate has an incident. Then check your own token, your API calls and your model settings. Each list starts with the quickest check.

Jump to what you are seeing

API Down

Calls to the Replicate API fail or time out. The status code tells you whether the problem is your token or Replicate.

  1. A 401 or 403 means your token is wrong or lacks permission. Check the token is set and has not been revoked.
  2. A 429 means too many requests. Wait, then retry with a growing delay.
  3. A 5xx means a platform-side problem. Check replicatestatus.com for an active API incident.
  4. If calls fail only from one place, check your network and any proxy between your system and the API.

Models Not Running

A prediction is queued for a long time or does not start. The model may still be starting, or capacity may be limited.

  1. Check whether the model is still starting. The first run after a quiet period can take longer.
  2. Check replicatestatus.com for a capacity or prediction incident.
  3. Check the model name and version you call. A wrong or removed version will not run.
  4. If the same model fails only for you, send the model name, version and prediction ID to support.

Website Down

The Replicate website or dashboard does not load. Your API calls may still work.

  1. Open the site in a private window and on another network.
  2. Check replicatestatus.com for a website incident.
  3. Test your app's AI feature. If it still works, the problem is only with the website.

Slow Predictions

Predictions take much longer than normal. The usual causes are capacity, a large input or a busy model.

  1. Check replicatestatus.com for performance or GPU capacity incidents.
  2. Try a smaller input, such as shorter text or a smaller image, to see whether size is the cause.
  3. Retry later, since busy periods can slow predictions.
  4. If slowness continues with no incident on the page, send the prediction IDs and times to support.

Login Failed

Sign-in to the Replicate account is refused.

  1. If the message says the password is wrong, reset it and check spam for the email.
  2. If you sign in with another account provider, use that same route.
  3. Check which account or workspace you are signing in to, if you belong to more than one.

CLI Errors

The Replicate command line tool fails or reports an error.

  1. Update the command line tool to the latest version, since an old one can fail after a platform change.
  2. Check your token is set in the environment the tool reads, and that it is the right token.
  3. Run the command again and copy the full error text, not only the last line.
  4. If the error mentions a model or version, check the spelling of the name and version.

Billing Issues

A charge looks wrong, a payment fails, or predictions stop because the account has no balance left.

  1. Check the billing page for the current balance and the payment method on file.
  2. If a payment failed because the bank declined it, update the payment method and try again.
  3. Check the usage records for the time of the charge to see what was billed.
  4. If a charge is wrong, contact Replicate support with the account name and the charge date.

Still not working?

If it still does not work, contact Replicate support through the help option on the Replicate website. Have your account or workspace name, the model name and version, the prediction ID, the exact status code or error, and the time it started with your time zone. Live incident updates are on replicatestatus.com.

Many AI feature problems come from a token, a model version or a busy period, and they clear once that one detail is corrected. This status page shows live incidents, so you can see whether the problem is on Replicate's side.

Frequently asked questions about Replicate

Is Replicate down right now?

No. Based on the latest status data on this page, Replicate (replicatestatus.com) is up and running normally. The most recent incident, "A100 hardware partial outage", was resolved (last update Aug 27, 2026).

What should I do if Replicate is not working for me?

First rule out your side: reload the page, try another browser or device, clear the cache and cookies for replicatestatus.com, flush your DNS cache and turn off any VPN or proxy. Then compare with this page: if the status shows an incident, or many users reported problems in the last 48 hours, the issue is on the service's end and usually clears up without any action from you. The troubleshooting steps on this page go through each check in order.

What was the most recent Replicate incident?

The most recent incident on record is "A100 hardware partial outage", last updated on Aug 27, 2026. It has been resolved.

How do I report a problem with Replicate?

Use the report buttons at the top of this page, or describe the problem in the user reports section. Every report is counted in the 48-hour trend chart and helps other people see whether the problem is widespread.

Where is the official Replicate status page?

The official status page for Replicate is replicatestatus.com.

Advanced Domain Info Unavailable

We couldn't load advanced domain and security information for replicatestatus.com at this time. Please try again later.