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
New York City, NY 2
Manchester, England 1
Angers, Pays de la Loire 1
London, England 1
Noida, UP 2
Jewar, UP 1
Braga, Braga 1
Paris, Île-de-France 1
Prievidza, Nitriansky 1
Farmers Branch, TX 1
Helsinki, Uusimaa 1
Crisfield, MD 1
Nanaimo, BC 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:

  • talk2sunder
    Sunder (@talk2sunder) reported

    Our Teams bot went silent. Zero errors. Zero logs. Azure said healthy, Cloudflare said healthy, our servers said healthy. Slack worked fine. Same bot, same endpoint. Gave it to Claude (Fable 5). It pointed the bot's endpoint at a plain webhook listener. Microsoft's messages showed up instantly. So Teams WAS sending — something about our edge was unreachable. One openssl probe later: our CDN required TLS 1.3, and Microsoft's Teams delivery fleet still speaks TLS 1.2. No logs because of handshake failire. Fable 5 rocks.

  • ICPapprentice
    The ICP Apprentice (@ICPapprentice) reported

    $ICP Signal ♾🚨: Cloudflare just admitted the internet's business model is dead. Ads and subscriptions were built for humans who watch and keep paying. AI agents do neither. They grab the content once and leave. So the company sitting in front of a fifth of the web built a "Monetization Gateway." It swaps a 401 Unauthorized for a 402 Payment Required and collects the toll in the middle. The chokepoint just made itself the tollbooth. But here's the tell. Visa and Stripe can't clear a payment worth less than a cent. So how does Cloudflare settle it? Stablecoins. Crypto rails. The exact plumbing Web2 spent a decade calling a scam. The most powerful company in Web2 just built the future of internet payments, and it doesn't run on Web2. On $ICP, the canister ♾ that serves the content is the same thing that charges for it. No gateway. No landlord taking the toll. Cloudflare proved the agentic internet needs native settlement. They built it as a middleman. The other internet already removed the middle. See the signal♾🚨 Full article in comments

  • whatdafuqkyle
    kyle (@whatdafuqkyle) reported

    🚨BREAKING: @x I can sniff a @Cloudflare bed **** from a mile away. platform is currently dumping on iOS.

  • NaorisProtocol
    Naoris Protocol (@NaorisProtocol) reported

    @Weaver_Labs @Cloudflare Fair parallel. Telecom had to retrofit a live network with millions of legacy devices already in the field. A chain built with ML-DSA-87 at genesis skips that coordination problem entirely, there's no fleet of old signers to bring along.

  • dezign_ash
    Ash Designs (@dezign_ash) reported

    @BraedendotTECH We're not as sharp as we were "before AI". We're just one @Cloudflare outage away from realizing how dependent we are on AI.

  • ematt
    Matt Gibbs (@ematt) reported

    Meta gets to scrape our work for free to train its AI. We get the compute bill, engineering cleanup and downtime. Its crawler knocked one of my sites offline in the process. In a 45-minute window, meta-externalagent made ~1,210 requests. 849, roughly 70%, ended as 499s: the crawler opened them, then abandoned them. The burst hit hundreds of long-tail dynamic URLs. At the same time, usage jumped to ~2 CPU cores, memory climbed from under 1 GB to 5.4 GB, V8 exhausted its heap, and four Cloudflare health checks failed. This wasn’t a giant volumetric DDoS, and Cloudflare didn’t fail. Another app on the same server handled 126,000+ edge requests during the same window. The problem was concurrency. Abandoned requests left expensive Redis, Supabase and React rendering work running at the origin. A CDN can cache completed responses. It cannot cancel application work already underway. Our origin should have had stronger backpressure and disconnect cancellation. That’s being fixed. But a weakness in our stack doesn’t make Meta’s crawler behaviour reasonable. Meta gets the AI training material for free. Publishers absorb the compute costs, engineering time and downtime. How is that remotely fair?

  • FREAK0NAUT
    Freak0naut (@FREAK0NAUT) reported

    @VegaVandal i meant to buy crowdstrike after the Microsoft outage 2 years ago. instead a accidentally bought cloudflare.... now up 247% on the trade.

  • im_payam
    Payam (@im_payam) reported

    This is the FASTEST way I've found to ship. Built for coding agents in terminal. Here’s the setup: - Get a cheap VPS (16 or 8GB) - Install Tailscale, block ALL traffic except Tailscale - Install Claude Code on the VPS - get a domain on Cloudflare - grab Cloudflare API token and pass to Claude - ask Claude to connect the domain to the server through Cloudflare's proxy (do not open ports) - Setup your site with Next.js, or vanilla JS + HTML - Use SQLite for database. (it's just a file) - ask claude: "Setup Restic to nightly backup DB and .env to R2" That's it. you are now the fastest and less error prone setup to build real products with agents. - Zero platform lock-in - no crazy bills from Supabase - no timeouts from Vercel - scales to millions with no limits - build it, restart service, it's live! just copy paste this to Claude to get started.

  • Marshal_Seda
    Seda Marshal (@Marshal_Seda) reported

    @DanielNjorogee @truehostcloud I faced this challenge with about 15 domains I wanted to change their nameservers to point to cloudflare. @truehostcloud why did I have to call support to help me do this?

  • gmwacharo
    Gerishon (@gmwacharo) reported

    Follow up. When I enable Cloudflare WARP, the issue immediately disappears and most websites function normally. This strongly suggests a routing or peering issue rather than a local hardware problem. Please investigate the routing affecting Kenyan customers.

  • the_jujukey
    JUJU ☀️· (@the_jujukey) reported

    @fr1ko_eth They didn’t rug …it was a cloudflare issue …what’s Loshmi saying lmao

  • Crypto_Jargon
    Crypto Jargon (@Crypto_Jargon) reported

    💥BREAKING: Every major card network just signed onto a payment protocol built for software to pay software, no human involved. The Linux Foundation confirmed the x402 Foundation is now formally governed by 40 members, and Coinbase's original contribution of the protocol is complete. The list of backers is the real headline: Visa, Mastercard, Amex, Stripe, Ripple, Google, Amazon Web Services, Cloudflare, Circle, and both the Solana and Stellar foundations, among others. Here's the part almost nobody knows. HTTP, the protocol every website runs on, has had a status code sitting unused for thirty years. Code 402, labeled "Payment Required." The web's original architects expected someone would eventually build payments directly into it. Nobody did, because card fees made charging fractions of a cent pointless, so the internet monetized through ads and subscriptions instead. x402 finally uses that code. A server asks for payment, a client sends a stablecoin transfer, usually USDC, and gets the data back in seconds. No account, no card, no prior relationship needed. That's exactly why AI companies care. An autonomous agent can't open a bank account or pass a credit check, but it can sign a transaction. Google already built x402 into its own agent payment system. Cloudflare ships it by default in its agent toolkit. The actual usage is still small, about $24 million moved last month across 75 million payments, averaging 32 cents each. That's nothing next to what Visa or Mastercard move in a single day. But the average payment size is the tell. No card network on earth can process a 32 cent charge profitably. This protocol was built for a kind of commerce that doesn't fit inside the rails these same companies already own, which is exactly why they just joined it instead of competing with it.

  • memselon
    Umut Sevinc (@memselon) reported

    Question for SaaS devs: where do you store your users files? We’re building a Framer plugin for 3D mockups (still in the kitchen). Every user uploads photos/videos to display on device screens. The trap we almost missed: storage costs nothing, it’s the WAY OUT that costs. A 13MB video stored once, but downloaded by every visitor of every landing → terabytes of bandwidth → ~€500/mo on Supabase. Our fix: Supabase keeps the scene (device, color, texture , a few KB), Cloudflare R2 serves the heavy files. R2 charges nothing for outbound bandwidth. Zero. Unlimited. Result: ~$26/mo instead of 500. Would you have done it differently? #buildinpublic

  • Degen_calls_sol
    DegenCalls (@Degen_calls_sol) reported

    GITHUB REPOS YOU SHOULD KNOW ABOUT Most scrapers break for boring reasons. A button moves, a class name changes, Cloudflare gets in the way, or the crawler dies halfway through a long run. Scrapling turns scraping into a more resilient system. Scrapy-style spiders, concurrent crawlers, pause and resume, anti-bot handling, and adaptive element finding in one framework. The detail most people miss: the adaptive selectors are the real unlock. Instead of hard-coding brittle CSS paths and praying the site never changes, the scraper can relocate elements after redesigns. That matters when you are scraping production targets, not toy pages. This is the shift from scripts to infrastructure. A script extracts data once. A scraping framework keeps extracting when the website changes, slows down, blocks, or moves the target. Most people still build scrapers like one-off hacks. The better setup is a crawler that expects failure and keeps going anyway.

  • Alpernoth
    Alpernoth (@Alpernoth) reported

    ok seriously, what's going on with the cloudflare page popping up on X lately and my account continually getting locked? wtf is going on with either this website or Cloudflare? I'm not DOING anything other than enjoying artwork for the most part on this site!

Check Current Status