outages.live
Live
CloudflareMaintenance ·

NRT (Tokyo) on 2026-11-13

MaintenanceOfficial update

Maintenance will begin soon as scheduled.

The latest update from Cloudflare.

State

Scheduled

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Cloudflare

Scheduled

Maintenance will begin soon as scheduled.

Affected components

1
Tokyo, Japan - (NRT)

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

96

Days with an incident

78

Median duration

1 h 33 min

This incident

Not comparable

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

56 days
median 1 h 33 min
90 days agoToday

Other Cloudflare incidents

All incidents

Cloudflare·Cloudflare is seeing an issue with Workers API availability

Cloudflare Workers API availability is degraded. Customers can see more 5xx errors when they deploy Workers or do other API actions. Cloudflare identified the issue, implemented a fix, and now monitors the results.

Degraded

Cloudflare·Cloudflare is currently having an issue with the r8.im registry used for Replicate model publishing and builds is currently restricted

Cloudflare reports an issue with the r8.im registry. This restricts Replicate model publishing and builds. Cloudflare identified the issue and is implementing a fix.

Degraded

Cloudflare·Elevated error rate for workers startup

Cloudflare Workers startup had an elevated error rate. The problem affected Workers and Developer Services - Workers, mainly for Workers that use large amounts of memory. Cloudflare resolved the incident after 82 minutes.

Resolved

Cloudflare·Durable Objects increased error rates in North America

Cloudflare Durable Objects had increased error rates in North American colos. Cloudflare reports that the incident is resolved. The incident lasted about 5 hours and 5 minutes.

Resolved

Cloudflare·Replicate Issue

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.

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