outages.live
Live
CloudflareIncident ·

Replicate Input Upload Issue

DegradedOfficial update
0

Cloudflare reports that Replicate input uploads are degraded. Model builds and pushes through r8.im do not work. Cloudflare identified the problem and continues to implement a fix.

State

Identified

Started

Ongoing for

13 h 16 min

Worst impact

Degraded

Timeline

3 updates
04:3307:5211:1114:3017:49
DegradedUpdate postedTimes in UTC

Investigating

39 min 5%

Identified

12 h 37 min 95%

Updates

Times in UTC

As posted by Cloudflare

Identified

We are continuing to work on a fix for the issue. Current impact: Input uploads are degraded. Model builds and pushes via r8.im are unavailable.

Identified

The issue has been identified and a fix is being implemented.

Investigating

Cloudflare is investigating issues with Replicate input uploads. We are working to understand the full impact and mitigate this problem. More updates to follow shortly

Affected components

1
Replicate

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

90

Days with an incident

76

Median duration

1 h 26 min

This incident

9.3× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

56 days
median 1 h 26 min
90 days agoToday

Other Cloudflare incidents

All incidents

Cloudflare·Network Performance Degraded

Cloudflare reported network performance degradation near LAX and Western North America. Cloudflare identified the issue, implemented a fix, and monitored the results. The incident is resolved and it lasted 26 minutes.

Resolved

Cloudflare·Workers deployments errors with D1 bindings

Cloudflare has identified and resolved an issue impacting Workers deployments with D1 bindings. Customers may have seen issues deploying their Workers between 12:42 UTC - 13:03 UTC 11th November 2026

Resolved

Cloudflare·SSL Certificate Provisioning Issue

Cloudflare had a problem with SSL Certificate Provisioning that affected the deployment of some custom certificates. Cloudflare advised customers to pause certificate redeployments during the incident. The incident is resolved and lasted 142 minutes.

Resolved

Cloudflare·Elevated number of 5xx errors in Hong Kong

Between 07:30-07:45 UTC customers reaching Hong Kong, may have experienced an elevated number of 5xx errors.

Resolved

Cloudflare·Cloudflare Worker Builds Issue

Cloudflare Worker Builds did not work. The issue affected the Workers, Containers, and Workers Builds components. Cloudflare reports that the incident is resolved. The outage lasted 12 minutes, from 06:29 to 06:41 UTC on 11 November 2026.

Resolved

Follow Cloudflare

Your coding agent knows when Cloudflare is down, and tells you when a failure is theirs, not yours. You can also get Cloudflare incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "cloudflare" and tell me if Cloudflare has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=cloudflare
Slack
/feed subscribe https://outages.live/feed.xml?providers=cloudflare

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane