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
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:
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 |
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:
-
haadi (@mhaadiabu) reported@DhravyaShah honestly cloudflare has really cool infra but it’s always such a pain to work with deploying an app to workers is so frustrating. everyone talks about vercel’s “lock-in” but you don’t need to fight configs to get your deployment up worst case scenario you add a nitro plug-in
-
Akash (@roguesherlock) reported@DhravyaShah I follow all the cloudflare devs and i see passion in their tweets but then i go to try the product and i'm disappointed. every. single. time. It's been like this for as long as i can remember :( vercel folks are awesome and their product is top tier. Every time i use the vercel dashboard i can see the attention to detail that they've put in. It's like someone sat and thought about the user actually using the product day to day. I've never ever had any issue with vercel. Only nags i had with loading skeletons but they've fixed that too this year!
-
Rafael Martins (@rgmcorp) reportedAnyone getting 500 errors from Cloudflare security challenges?
-
John Nigroᵍᵐ (@jn) reported@snipextt @p_naix @spaceship why does everyone shill cloudflare? you cannot change your nameservers. You save 9 cents to have a fundamentally broken domain name.
-
Luis Catacora (@lucatac0) reported@Cloudflare the use case I keep thinking about: self-hosted LLM inference behind a Worker your model output is identical for the same prompt, but now it's cached at the edge and your GPU never sees the repeat request
-
𝐋𝐚𝐤𝐬𝐡 𝐑𝐚𝐠𝐡𝐚𝐯𝐚𝐧 (@laraghavan) reported@Cloudflare Will @beehiiv support this natively? @denk_tweets?
-
vx-underground (@vxunderground) reportedA lot of malware campaigns use CloudFlare to mask their C2 infrastructure. They do this for a few reasons, but the primary reason is that it delays the inevitable of their C2 being taken down. The malware developers using CloudFlare isn't necessarily bad, and it isn't necessarily good, it's just a known thing that people abuse. Yes, CloudFlare did their job. CloudFlare takes down malware infrastructure a lot, despite people saying CloudFlare doesn't take any action, because CloudFlare is inundated with both legitimate and illegitimate takedown requests and reports daily. The daily reports they receive are (probably) in the millions daily. If they didn't want to hide behind CloudFlare, the malware developers could also have used a compromised website (very common), or Discord, or Google docs, or Spotify, or ... basically pick a website and service and it can be abused with enough elbow grease. The easiest, fastest, and easily configurable method is generic host with CloudFlare. When the domain is taken down, or CloudFlare takes it down, they simple spin up new infrastructure with a new CloudFlare account and operations resume as normal.
-
Inference Engine (@iedaily_) reportedAI agents read the web for free. cloudflare just built them a cash register. any website behind cloudflare will soon be able to charge agents money -- per page, per API call. payments settle in under a second, down to fractions of a cent. no account, no checkout page. AWS switched on the same thing two weeks ago. if bots were hammering your site, would you charge them or keep blocking them?
-
FixlyAI (@Fixlyai) reportedAI companies have been stealing the web. Not hacking it. Not paying for it. Just taking it. OpenAI crawls 1,700 pages to send back 1 visitor. Anthropic? 73,000 pages. One referral. Publishers pay the bandwidth. AI companies keep the value. No credit. No payment. No permission. Cloudflare just decided that ends on September 15. Any bot scraping ad-supported pages without permission gets blocked by default. Search crawlers stay. AI training bots don't. "The majority of traffic on the internet is now non-human." The web was never built for this. And now someone is finally doing something about it. Every AI product built on scraped content has 70 days to figure out what comes next. Are you one of them?
-
Stephen Taylor (@stephen_taylor) reported@RealAlbanianPat You should be pre-rendering this data from your database into static geojosn files. Then upload those files to s3 on AWS (or R2 on cloudflare) and put those behind a cache layer like cloudfront (AWS) or… cloudflare. You’re likely paying huge database costs because each request is pulling from memory on a cloud db. Static files are much more efficient. Please let me know if you need any help with this. R2 even has free egress while AWS has a generous free tier.
-
Julian Goldie SEO (@JulianGoldieSEO) reported𝗔𝗴𝗲𝗻𝘁 𝗢𝗦 𝗼𝗻 𝗠𝗼𝗯𝗶𝗹𝗲: 𝗧𝗵𝗲𝗿𝗲'𝘀 𝗮 𝗳𝗿𝗲𝗲 𝘄𝗮𝘆 𝘁𝗼 𝗿𝘂𝗻 𝘆𝗼𝘂𝗿 𝘄𝗵𝗼𝗹𝗲 𝗔𝗜 𝗮𝗴𝗲𝗻𝘁 𝘀𝘆𝘀𝘁𝗲𝗺 𝗳𝗿𝗼𝗺 𝘆𝗼𝘂𝗿 𝗽𝗵𝗼𝗻𝗲. Your agents live on a server. Your phone becomes the remote control. The setup: 1. Run your agent OS on a VPS 2. Connect it with Tailscale (free) or Cloudflare 3. Open it from your phone. Same system. Same memory. Anywhere. Fix a bug from the couch. Kick off research from the school run. Check your agents from anywhere. One community member set this up and it works on mobile AND desktop. Fair warning: opening remote access means thinking about security. Lock it down before you open it up. Your AI team shouldn't be chained to your desk. Want the SOP? DM me. 💬
-
Warya Wayne (@WaryaWayne) reportedI am having a problem with a status check website I made. It is spamming me that the sites are down when they are not and i think it's Cloudflare blocking them do to them checking every 180 secs and notifying me but I have 200 notifications saying it's down and they're up? How?
-
Ferbin (@Ferbin08) reported@Cloudflare For AI startups, it's not infra. It's whether it works when customers actually plug it in. Most never survive that test.
-
Omid Saffari (@omidsaffari) reportedAn AI gateway is not a production badge. It is a control tax. Pay it when a second model, a second provider, or a second engineer touches your LLM calls. Before that, call the provider directly and ship. The moment that line gets crossed, the gateway starts earning its hop. Why? Because the real problem is not "how do we call another model?" It is duplicated retry logic, missing spend attribution, no shared rate limits, inconsistent logs, and a fallback path nobody has tested. My decision rule: Single feature, single model: no gateway. Fast free visibility: Cloudflare. Already on Vercel and want zero token markup: Vercel AI Gateway. Managed governance, RBAC, guardrails, audit path: Portkey. Keys must stay inside your perimeter: LiteLLM, with the operational work that comes with self-hosting. The part teams underestimate is not setup. It is ownership. A fallback only counts if it fails over on real signals: timeouts, 5xx, 429, and invalid response shape. A cost dashboard only helps if every request is tagged by customer, feature, environment, and model. Semantic caching only works if you have measured false hits against real queries. And if you self-host, patching is now your calendar. LiteLLM's 2026 CVE hit CVSS 8.8 on NVD and was fixed in 1.83.7. The lesson is not "avoid LiteLLM." The lesson is that a gateway holds the keys, so it has to be treated like security-critical infrastructure. Add the gateway when it centralizes control. Not because the diagram looks mature.
-
SLeNDeR_KiLLeR | Xeno VTuber (@SLeNDeR_KiLL3R) reported@ChainsawMan4DBD It's not an issue only with me sadly, cloudflare is having issues and I can't see when it's going to be back up