1. Home
  2. Companies
  3. Cloudflare
  4. Outage Map
Cloudflare

Cloudflare Outage Map

The map below depicts the most recent cities worldwide where Cloudflare users have reported problems and outages. If you are having an issue with Cloudflare, make sure to submit a report below

Loading map, please wait...

The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.

Cloudflare users affected:

Less
More
Check Current Status

Cloudflare is a company that provides DDoS mitigation, content delivery network (CDN) services, security and distributed DNS services. Cloudflare's services sit between the visitor and the Cloudflare user's hosting provider, acting as a reverse proxy for websites.

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
Paris, Île-de-France 1
New York City, NY 1
Manchester, England 1
Angers, Pays de la Loire 1
London, England 1
Check Current Status

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Cloudflare Issues Reports

Latest outage, problems and issue reports in social media:

  • techtitanmb
    Techtitanmb (@techtitanmb) reported

    Cloudflare is reporting an unresolved issue affecting its Berlin location. Have you noticed slower websites or connection problems today?

  • janekm
    Janek Mann (@janekm) reported

    @doodlestein @yzhang390 But that's not really the issue... it's that e.g. Huggingface and Microsoft and Cloudflare and Fireworks can be easily stopped from hosting them with misguided regulation. Literally only harming US companies at the expense of Chinese ones, ultimately.

  • stepherriffic
    Stephanie Hudson (@stepherriffic) reported

    @JamesWelbes Yes! But also... Set up a new @Cloudflare account in their behalf. Add yourself as a delegate. At handover, share the main login with them along with instructions to change email and pw. (They will not, in fact, change it, but at least you did the right thing lol)

  • trishoolai
    Trishool | SN23 (@trishoolai) reported

    AI is at the same inflection point web security hit twenty years ago. The attacks are real, the damage is mounting, and the industry is starting to realise that shipping without a safety layer isn't a risk worth taking. Cloudflare didn't create that shift in web security. It became one of the companies that defined it. We believe the same thing is happening in AI right now. AI agents have deleted production databases, exposed sensitive customer data, and taken actions their creators never intended. As AI systems do more and touch more, the cost of getting safety wrong keeps growing. The internet eventually stopped expecting every company to build its own security infrastructure because the problem outgrew what individual teams could manage. Shared infrastructure became the better answer. AI safety is heading in the same direction. That's the future we're building toward with HaloGuard on Bittensor. Production-ready, peer-reviewed, open weights, and built to protect AI systems across 46 languages, backed by a decentralised network that gets stronger every week. AI safety isn't a problem that gets solved once. It's infrastructure that has to keep learning as the threat landscape evolves. That is what we are building on Bittensor.

  • toolportapp
    Toolport (@toolportapp) reported

    Cloudflare's CTO, Dane Knecht, emailed their entire customer list about running every AI agent through MCP portals, with scoped tool access and a Code Mode they say cuts token costs ~93%. We build Toolport. This is our exact category. A few notes from the small end of the pond. 1. The announcement is two products wearing one trenchcoat. AI Gateway is a model-layer proxy. It routes your OpenAI/Anthropic calls and meters model spend, same lane as OpenRouter or LiteLLM. MCP portals are the tool layer, deciding which servers and tools each agent can touch. Different problems, different failure modes. If you're evaluating either one, don't let the bundle blur that line. 2. Their ~93% Code Mode number lands in the same range we've been measuring with lazy discovery for the past three months. Loading dozens of tool schemas into context on every request was always the wrong default. It's nice that it's no longer just indie gateway builders saying so. 3. The structural difference. Their portals require being a Cloudflare customer and routing agent traffic through their edge. Toolport runs on your own machine and works with Claude Desktop, Cursor, and 25 other clients, with no vendor in the traffic path. When the traffic is your prompts, your credentials, and your tool outputs, where it flows is not a detail. 4. Scoped access is becoming table stakes. The harder question is whether the tool you approved yesterday is the same tool running today. Toolport pins tool integrity, quarantines drift, and scans for injection. A DLP scan on the wire doesn't catch a server that changed underneath you. Watching a giant walk into your category is a strange feeling. It's also the strongest signal yet that this layer needs to exist. We just think it should live on your machine, not in someone else's cloud.

  • WallisDev
    Aiden (@WallisDev) reported

    @thdxr mostly terraform and a custom deploy pipeline that just pushes code directly to the workers. Config changes land through terraform updates It sucks. this stuff and: * No workload identity federation * Their permissions story is simple - too simple hold Cloudflare back for me

  • schwerelosio
    Schwerelos.io (@schwerelosio) reported

    +37% following every tracked call on $ARM since March, 4 scored calls, 50% hit rate. The catalyst is concrete: Arm's AGI CPU, a data center chip built for agentic AI workloads, with Meta as lead co-development partner and OpenAI, Cloudflare, SAP, and SK Telecom already committed. Semiconductors don't usually have this kind of customer list locked in before the chip ships.

  • uasneppy
    Ray 🇺🇦🏳️‍🌈 (@uasneppy) reported

    I’ll try to fix snepclub twitter embedder later today, sorry :( I didn’t know about the new updates and me having to have a burner account, plus deploying it on Cloudflare 💀

  • 80Level
    80 LEVEL (@80Level) reported

    NVIDIA's CEO, Jensen Huang, shared his first post on X/Twitter – a letter to the US government urging it to support open-weight, publicly downloadable AI models. The letter was signed by some of the biggest companies, including Google, AMD, Cloudflare, GitHub, Microsoft, Meta, IBM, and Dell.

  • N3DrGonzo
    Dr. Gonzo (@N3DrGonzo) reported

    @AnisDrawn PSN goes down more often than CloudFlare. And CloudFlare has an outage QUOTA. But yes, please tell me how an all digital ecosystem for a console is a good thing.

  • KnowTechGlobal
    KnowTechGlobal (@KnowTechGlobal) reported

    That difference changes architecture. If your app depends on slow upstreams, the platform that charges less for waiting can look cheaper even when the code is identical. The winner is not "Cloudflare" or "AWS" in the abstract. It is the workload shape.

  • staabse
    haden staab (@staabse) reported

    @Porkbun @baiaphilia Firstly, I never said there was something wrong with you. You’re more than welcome to give us your pitch. Why should I use Porkbun over Cloudflare?

  • joshmanders
    Josh (@joshmanders) reported

    @leodev So if I am understanding this correctly, using Cloudflare email is $21.45 for 50k emails? Honestly that's acceptable to me. Especially if they have good inbox placement and reliability. AWS is saturated with spammers and ****. I'll pay a premium to guarantee my stuff hits inboxes.

  • RyanWycuff
    Ryan Wycuff (@RyanWycuff) reported

    @unusual_whales CloudFlare is cheap as **** and normally riddled with bugs why it goes down and potential takes 1/3r the internet and source repos with it. Dont trust a thing they say.

  • evi77ain
    Eidzoku (@evi77ain) reported

    Apparently Codex Desktop 26.721.4979.0 can self-destruct just from using its built-in browser. Very agentic.💀 At first I thought Cloudflare was the cause. Nope. Perplexity reproduced the exact same failure, and it's already mentioned in one of the related issues. The actual chain is: webpage loads → Chromium GPU crashes (`101457950`) → Windows blocks the bundled `vk_swiftshader.dll` fallback for not meeting Microsoft signing requirements → GPU relaunch fails (`18`) → Codex dies.

Check Current Status