Live

Network disruption across multiple colocations in India

0

A network disruption degraded some Cloudflare services in Ahmedabad, Hyderabad, Kanpur, Mumbai, Nagpur, New Delhi, and Patna, India. Cloudflare identified the issue and implemented a fix, then monitored the results. The incident is resolved and lasted 42 minutes.

State

Resolved

Started

Lasted

42 min

Worst impact

Degraded

Timeline

4 updates
08:0408:1508:2508:3608:46
DegradedUpdate postedTimes in UTC

Investigating

20 min 47%

Identified

15 min 36%

Monitoring

7 min 17%

Updates

Times in UTC

As posted by Cloudflare

Resolved

This incident has been resolved.

Monitoring

A fix has been implemented and we are monitoring the results.

Identified

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

Investigating

Cloudflare is investigating a network disruption across multiple datacenters in India, impacting some Cloudflare services in region. We are working to analyse and mitigate this problem. More updates to follow shortly.

Affected components

7
Ahmedabad, India - (AMD)Hyderabad, India - (HYD)Kanpur, India - (KNU)Mumbai, India - (BOM)Nagpur, India - (NAG)New Delhi, India - (DEL)Patna, India - (PAT)

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

116

Days with an incident

83

Median duration

1 h 26 min

This incident

51% shorter than 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

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