outages.live
Live
CloudflareIncident ·

Replicate Issue

ResolvedOfficial update
0

Cloudflare Replicate customers saw more 500 errors for predictions in the Replicate component. Cloudflare identified the issue and put a fix in place. The incident is resolved and lasted 3 hours and 4 minutes.

State

Resolved

Started

Lasted

3 h 4 min

Worst impact

Degraded

Timeline

3 updates
08:3009:1610:0210:4811:34
DegradedUpdate postedTimes in UTC

Investigating

1 h 6 min 36%

Identified

1 h 58 min 64%

Updates

Times in UTC

As posted by Cloudflare

Resolved

This incident has been resolved.

Identified

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

Investigating

Cloudflare Replicate customers may see an increase of 500 errors for predictions. More updates to follow shortly.

Affected components

1
Replicate

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

92

Days with an incident

77

Median duration

1 h 26 min

This incident

2.1× 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·DNSSEC Configuration Change Issues

Cloudflare reported degraded DNSSEC Updates. Customers could not enable or disable DNSSEC signing. Cloudflare identified the issue, implemented a fix, and monitored the results. The incident is resolved and lasted 33 minutes.

Resolved

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

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