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
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 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 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:

  • Lord_of_Candy
    Lord of Candy | Kaeos (@Lord_of_Candy) reported

    "But I can’t help build or maintain a path whose purpose is to defeat Cloudflare/Turnstile verification, even if older work crossed that line or framed it as scraping." Did OpenAI get in league with CF to stop bypasses? This is new to me. And stupid. Thanks nan.

  • firesidealpha
    Fireside Alpha (@firesidealpha) reported

    1/ Okay so $NET is officially getting into the payments-tollroad business. The new Monetization Gateway gives clarity, and it's exactly the toll booth for agent traffic sketched last time. Here's an updated look at the numbers, and how MG would actually work. 2/ The math, updated Last time, on @eastdakota's own numbers: 25M txn/s x 31.5M sec/yr = 788T transactions x $0.0003 per txn = $236B of gross volume x 1% take = ~$2.4B of incr. rev, vs a ~$2.2B base. The gateway doesn't break the math. It confirms the rail (stablecoins over x402) and widens the taxable base from crawls alone to any asset, any API, any tool, any agent action. Same toll booth, more roads running through it. The one thing it moves is price mix. The gateway's own examples run cents to dollars per action, like $0.01 per request or $0.99 per resolved support escalation, well above a flat fraction of a penny. So the realized model looks like fewer, higher-value transactions rather than an ocean of sub-cent ones. Push price up and volume down and you land in the same billion-dollar range. The bracket still runs from about $160M at the floor to north of the whole company at the center. And the number that decides where inside that range you actually land was not disclosed, its take rate. 3/ How the gateway actually works It runs on HTTP 402, Payment Required, a status code that has existed since the beginning of the web and almost never gets used. An agent requests something behind Cloudflare. Instead of the content, the server answers with a price. The agent pays in a stablecoin, settled in under a second for a fraction of a cent with no chargebacks, resubmits with proof of payment, and gets what it asked for. The seller sets the price. Cloudflare runs the plumbing in the middle and takes its cut of every settlement. There is no card network in the loop, because a card cannot clear a one-cent charge profitably. That is the whole reason it is built on stablecoins and x402. The agentic web finally gets a way to pay per action, and Cloudflare got its way into the action. _____ Follow @firesidealpha for more business analysis derived from key industry figures in conversations and firesides.

  • threepointone
    sunil pai (@threepointone) reported

    @kitlangton @thdxr @opencode yeah cloudflare went hard into the security angle because we have deep suspicion of llm code, and want to be so particular of what's exposed ot the environment, and not let it take down the parent in any way. not a hard req, and opencode is already a trusted tool when it's used

  • TechPostsEU
    Dave (@TechPostsEU) reported

    Just a/b perf tested Tigris versus Cloudflare R2 and R2 smoked Tigris. Not sure why you'd use it unless you need free egress or something. Performance was genuinely bad, like 700KB/s download over a 500+ Gbps link

  • ReesMorris
    Rees (@ReesMorris) reported

    I just noticed the Cloudflare login flow has a fade transition between pages and it's a really nice touch

  • jeremy_wokka
    Jeremy Shepherd 🔻🇵🇸 (@jeremy_wokka) reported

    @Cloudflare You have to scroll down a LOT to get past the blue check zombies and into the replies from non-mouth breathers who pay for twitter and then you can see how unpopular this is

  • joesadoski
    Joe Sadoski (@joesadoski) reported

    @chythram1 Can you say more about sign in? Is this cloudflare access/ZTNA?

  • cyberforget
    CyberForget (@cyberforget) reported

    @levelsio @Cloudflare I thought you was self hosting your own email service - or have things changed?

  • ma_ynk
    vīra (@ma_ynk) reported

    @Cloudflare @Cloudflare our team has been given 10k in cloudflare credits. But are still receiving a bill with a suspension notice. Have reached out to support twice already but no response. Need urgent support here

  • yaircleper
    Cleper 🌋 (@yaircleper) reported

    so @Cloudflare just did something most of crypto missed. Last week they launched the 𝗠𝗼𝗻𝗲𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗚𝗮𝘁𝗲𝘄𝗮𝘆. Any website, API, or app behind Cloudflare can now charge for resources on a per-request basis in stablecoins. No Stripe. No accounts. No checkout page. An HTTP status code from 1997, 402 𝘗𝘢𝘺𝘮𝘦𝘯𝘵 𝘙𝘦𝘲𝘶𝘪𝘳𝘦𝘥, finally doing its job. Why does this make sense for Cloudflare? Their CEO said it himself: 𝗔𝗜 𝗮𝗴𝗲𝗻𝘁𝘀 𝗮𝗿𝗲 𝗯𝗲𝗰𝗼𝗺𝗶𝗻𝗴 𝘁𝗵𝗲 𝗱𝗼𝗺𝗶𝗻𝗮𝗻𝘁 𝘂𝘀𝗲𝗿𝘀 𝗼𝗳 𝘁𝗵𝗲 𝗶𝗻𝘁𝗲𝗿𝗻𝗲𝘁. Agents don't have credit cards. They pay per request, in milliseconds, or they leave. Cloudflare sits in front of roughly 20% of the web. 𝗧𝗵𝗲𝘆 𝗷𝘂𝘀𝘁 𝗽𝘂𝘁 𝗮 𝗺𝗲𝘁𝗲𝗿 𝗼𝗻 𝗶𝘁. But here is what almost nobody is asking. Every one of those payments settles on a blockchain. Millions of micropayments a day, verified and confirmed on-chain. 𝗧𝗵𝗲 𝗽𝗮𝘆𝗺𝗲𝗻𝘁 𝗿𝗮𝗶𝗹 𝗶𝘀 𝗼𝗻𝗹𝘆 𝗮𝘀 𝘁𝗿𝘂𝘀𝘁𝘄𝗼𝗿𝘁𝗵𝘆 𝗮𝘀 𝘁𝗵𝗲 𝗶𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝘁𝗵𝗮𝘁 𝗿𝗲𝗮𝗱𝘀 𝗶𝘁. Ten weeks ago we watched $292𝗠 𝗱𝗶𝘀𝗮𝗽𝗽𝗲𝗮𝗿 𝗳𝗿𝗼𝗺 𝗞𝗲𝗹𝗽𝗗𝗔𝗢 because a verification network trusted the wrong data source. One more thought. 𝗔𝗱𝘀 𝗳𝘂𝗻𝗱𝗲𝗱 𝘁𝗵𝗲 𝗶𝗻𝘁𝗲𝗿𝗻𝗲𝘁 𝘄𝗲 𝘀𝗰𝗿𝗼𝗹𝗹. In an 𝘪̲𝘯̲𝘵̲𝘦̲𝘳̲𝘧̲𝘢̲𝘤̲𝘦̲𝘭̲𝘦̲𝘴̲𝘴̲ ̲𝘪̲𝘯̲𝘵̲𝘦̲𝘳̲𝘯̲𝘦̲𝘵̲, nobody sees a banner. 𝘗𝘢𝘺𝘮𝘦𝘯𝘵𝘴 𝘵𝘢𝘬𝘦 𝘵𝘩𝘦𝘪𝘳 𝘱𝘭𝘢𝘤𝘦, 𝘢𝘯𝘥 𝘵𝘩𝘦 𝘷𝘢𝘭𝘶𝘦 𝘧𝘭𝘰𝘸𝘴 𝘣𝘢𝘤𝘬 𝘵𝘰 𝘵𝘩𝘦 𝘶𝘴𝘦𝘳𝘴 𝘵𝘩𝘦𝘪𝘳 𝘢𝘨𝘦𝘯𝘵𝘴 𝘸𝘰𝘳𝘬 𝘧𝘰𝘳. What do you think, is the settlement layer ready for internet-scale payments?

  • jasoki
    Jason (@jasoki) reported

    @Cloudflare @Newsweek @StatistaCharts Cloudflare is killing it. I'm a happy customer

  • Slav636
    Svyatoslav Pidgorny 🇺🇦🇦🇺 (@Slav636) reported

    @ryanyates1990 What’s the problem with Cloudflare?

  • skooookum
    skooks (@skooookum) reported

    @sally124445 Most web traffic becomes agents (already happening to some degree). Ad model breaks down further. Cloudflare becomes the clearinghouse for a machine-driven web economy. Price per view probably gets bundled into AI subscriptions. Content quality hinges on what you’ll pay.

  • kenny_alves
    Kenny Alves (@kenny_alves) reported

    @Cloudflare Any plans to add support for Bitcoin payments?

  • whotooksooraj
    Sooraj (@whotooksooraj) reported

    TIL Cloudflare uses Google chat instead of slack, wtf?

Check Current Status