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
Angers, Pays de la Loire 1
London, England 2
Noida, UP 3
Jewar, UP 1
Braga, Braga 1
Paris, Île-de-France 2
Prievidza, Nitriansky 1
Farmers Branch, TX 1
Helsinki, Uusimaa 1
Crisfield, MD 2
Nanaimo, BC 1
New York City, NY 1
Istanbul, Istanbul 1
Greater Noida, UP 2
Augsburg, Bavaria 1
Bengaluru, KA 1
Montataire, Hauts-de-France 1
Attleborough, England 1
Colima, COL 1
Leuven, Flanders 1
New Delhi, NCT 1
Mâcon, Bourgogne-Franche-Comté 1
Amsterdam, nh 1
Ashburn, VA 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:

  • Lorenzo__CB
    Lorenzo Castro (@Lorenzo__CB) reported

    @CloudflareDev cloudflare-api codemode mcp auth seems to be down, OAuth flow seems to work but the mcp alway returns "invalid_token". Have tried both codex and cursor clients, same result

  • ItsWelford
    Josh W (@ItsWelford) reported

    Anyone at Cloudflare able to help with an OAuth client? It's still waiting for verification & it makes me think something is wrong, because my other OAuth client verified almost instantly.

  • iam_elias1
    Elias Al (@iam_elias1) reported

    1/ The first thing most people get wrong: they test their speed using their ISP's own tool. Comcast has a speed test. AT&T has one. Spectrum, Verizon, Cox they all do. Never use them. ISP-hosted speed tests measure the connection between your device and the ISP's closest server a special, prioritized pathway that almost always shows flattering results. It's like a restaurant giving you a taste test from the chef's personal plate while everyone else eats from the regular kitchen. Real-world speed what you actually experience on Netflix, Zoom, YouTube, and gaming travels through dozens of servers, routing hops, and third-party networks. None of that is reflected in your ISP's speed test. The fix: Use independent speed tests. These are the 3 the professionals use: 1. fast. com (Netflix's speed test measures what streaming actually gets) 2. speedtest. net (Ookla manually select a non-ISP server for accurate results) 3. speed.cloudflare. com (Cloudflare also measures latency and jitter) Run all 3 at different times of day. The results will almost certainly be different from your ISP's tool. She ran all 3 on a Tuesday evening at 8 PM. ISP's own test: 487 Mbps. fast. com: 94 Mbps. speedtest. net (non-ISP server): 112 Mbps. Cloudflare: 108 Mbps. She was paying for 500. She was getting 100.

  • toptechschool
    Building Real estate AI (@toptechschool) reported

    Cloudflare is the best platform for devs. We replaced vapi with cloudflare, cutting down cost massively.

  • syakirurohman
    Syakir (@syakirurohman) reported

    @jackfriks I have been using cloudflare for my saas. They're so generous in almost every service. Even they give ai credit perday for testing a bunch of models in worker ai. Their worker and image transformation also generous

  • chantastic
    chan (@chantastic) reported

    @datalyncs yeah it’s bad out there. i honestly can’t be bothered to **** with it anymore. my apps are 95% Cloudflare and i could probably get away with raw JS for most UI

  • BilalBudhani
    Bilal @ Supadesk.co (@BilalBudhani) reported

    Cloudflare is down folks. What are you guys up to?

  • aarekaz
    Anurag (@aarekaz) reported

    Is cloudflare down?

  • 8INK5
    🍺 (@8INK5) reported

    @QBCCIntegrity @PaulineHansonOz @OneNationAus Cloudflare has been getting attacked over the past few days, I know there has been problems elsewhere are well so it might not just be ON

  • lexzy07
    whizzy 🎭 (@lexzy07) reported

    🪙 Mastercard Launches AI Agent Payment System Mastercard has introduced Agent Pay for Machines (AP4M), a system enabling automatic payments between AI agents without human involvement. The service targets high-frequency micropayments that agents execute independently in the background. Early adopters include Adyen, Stripe, Coinbase, Cloudflare, OKX, Ripple, and around 20 other companies.

  • EarnWhere
    Aaron Ware (@EarnWhere) reported

    @Cloudflare 's PDF endpoint is so good. I spent hours trying to speed up PDF creation inside of my architecture and did so much hacky **** to achieve a decent-enough UX. Just implemented Cloudflare's endpoint and happily ripped all that out for substantially better results.

  • JayTL00
    Jay.TL (@JayTL00) reported

    Both Visa and Mastercard launched agent payment rails this week. Zero real transactions have cleared through either. Visa Intelligent Commerce gives AI agents tokenized card credentials — your agent gets its own identity on a network processing 300 billion transactions a year. Mastercard's Agent Pay for Machines (AP4M) went further: agents paying other agents, machine-to-machine, no human in the loop. 30+ partners including Stripe, Coinbase, Solana, Polygon, Aave, Cloudflare, Ripple. The optics are undeniable. Two payment networks that move $30 trillion+ annually are building for a world where the buyer isn't human. But the substance is mostly slide deck. Three things the press releases don't mention: 1. Zero production volume. No transaction counts, no throughput benchmarks, no live merchant integrations with actual agent checkout flows. The 30+ AP4M partners are logos on a launch graphic. Every "early adopter" is testing in sandbox. Visa's own CFO Chris Suh said plainly: agentic commerce and stablecoins "won't pay off in the next six months, but could over the next six years." That's not a launch. That's a forward-looking statement with a PR budget. 2. The authority problem has no answer. Payment rails move money. They don't decide who's allowed to move it, when, or how much. When your agent spends $2,000 on cloud compute from another agent, who set that limit? Who audits it? Who's liable when the agent hallucinates a purchase? Visa's model (human-delegated tokens with spending caps) at least has a governance story. Mastercard's machine-to-machine model has a governance vacuum. The "fraud detection" and "spending limits" mentioned in press releases are features that don't exist in production yet. They're on the roadmap — which is where most agent infrastructure lives in 2026. 3. Five competing agent payment protocols launched in 2026. ACP. x402. MPP. AP2. AP4M. Each with different trust models, settlement layers, and identity frameworks. The fragmented landscape is a feature for early experimentation and a disaster for adoption. Merchants won't integrate five agent payment protocols. Agents won't carry five wallets. The consolidation hasn't started because nobody has enough transaction volume to matter. The real signal isn't the technology. It's that the two largest payment networks on Earth decided in the same week that agent commerce is real enough to allocate engineering resources, partner integration teams, and public marketing budgets. They're not building because agents are buying things today. They're building because if agents ever do buy things at scale, whoever owns the rail owns a tax on autonomous commerce. The bet is simple: the marginal cost of building agent payment infrastructure in 2026 is tiny compared to the cost of being locked out of a new transaction layer in 2028. Whether that bet pays off depends on a question none of these announcements address: what happens when the first agent makes a $50,000 mistake at machine speed on a rail designed for that speed? That's not a technology problem. It's a liability problem. And nobody has underwritten that policy yet.

  • David_mduw
    David Hamilton (@David_mduw) reported

    A support email landed at 7:05am. By the afternoon the fix was live in production and the customer had his answer. My total input: one prompt, a plan approval, a deploy approval. The workflow: - Claude reads the email thread (Gmail MCP) - Reads my product docs for context (Obsidian vault) - Queries the live database, read-only. His data was fine. So something was missing, not broken - Traces the codebase and finds the gap - Ships the fix - Deploys to Cloudflare, verifies against production - Drafts the customer reply in my voice. I read it and hit send At some point I'll automate the whole flow. Email lands, agent triages, a draft waits for my review. For now it's one sentence at 7am.

  • AdolfoUsier
    Adolfo 🦀🔺 | OpenCrabs Creator | truelens.tech®️ (@AdolfoUsier) reported

    @HyperTechInvest Cloudflare approach works at scale but self hosted agents sidestep the whole problem. @opencrabs runs on a single VPS with persistent state, free Xiaomi MiMo tokens til June 27 if you want to try it bro

  • LeSussyCat
    Sussycat Bloomberg (@LeSussyCat) reported

    @Cloudflare Put a smile on my face because atleast DDoS is using my ****

Check Current Status