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 |
|---|---|
| Ann Arbor, MI | 1 |
| Palermo, Sicily | 1 |
| New York City, NY | 3 |
| Los Angeles, CA | 1 |
| Paris, Île-de-France | 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:
-
saint (@thetronchguy) reportedaws, cloudflare, google, meta literally all have such ******* hostile ui it’s genuinely physically ******* painful to have to go spelunking thru the cave of mysteries just to get any ******* thing done no reason why having to use these dashboards genuinely leaves me wanting to fight someone EVERY single time man like how does it benefit you that your users would rather eat a ******* tire than use your **** dashboard??
-
Krishna Singh (@krishnasinghdev) reported@tapasadhikary @Namecheap I never liked namecheap / godaddy, don't know why people choose it over simple providers like cloudflare where they charge same amount for 1 or 10 years
-
Nick Gray (@nickgraynews) reportedupdate: ok the results are in - I tested 7 models on the real spam that got past my programatic checks The test set was 6 real spam submissions (two SEO agencies, a travel booking site, an astrology app, a music software company) plus 4 legit personal websites Each model reads their /friends page and the homepage, then answers two questions: is this a personal website? And is this a real friends page? Here are the results: * Gemini 3.5 Flash Lite: 10/10, 0.7 seconds * GLM-5.3-Flash: 10/10, 2.3 seconds ultimately * Gemma 4 26B: 10/10, 6.7 seconds * GPT-OSS 20B: 9/10, 3 seconds * Llama 3.2 3B: 9/10, 0.5 seconds (!) * Llama 3.1 8B: 8/10, 3.3 seconds Two things I learned: 1. You CAN speed up GLM-5.3-Flash I thought that thinking was forced on. But Cloudflare forwards a flat reasoning_effort: "low" param that the config shapes don't use or something. That took it from 17 seconds down to about 2, still 10/10. The catch is that cold starts still spike to 13 seconds sometimes. 2. The tiny Llama 3.2 3B beat the 8B on both speed and accuracy. It gave results in half a second, about 10 cents per 1,000 checks which is obviously nothing. Also the major unlock was feeding the homepage text along with the /friends page. Spammers dress up the friends page to get past my checks, but is unlikely they will edit the home page. I'll end up doing daily or weekly checks to make sure they don't edit the home just to pass the checks too, that's why I sort of want a super-cheap check. Anyhow: all this to say that I'm sticking with Gemini 3.5 Flash-Lite. It's 0.7 seconds, about 50 cents per 1,000 checks, and it never missed once I'm going these checks instead of manual approvals because I want people to submit their site and see it go live instantly. also it only cost me about $1 to run hundreds of these tests on Cloudflare Workers AI any suggestions appreciated!
-
Reyansh Bahl (@reyanshbahl) reported@wongmjane @Cloudflare One of the big issues I had with the current worker previews was not being able to deploy durable objects per preview, hope this fixes it
-
SoccerGuy (@SoccerGuyUS) reported@levelsio @Cloudflare Namecheap is awful. Anyone looking for a better Google Domains (since they rug pulled) alternative: Porkbun.
-
Deyder Cintron (@deydercintron) reported@levelsio @Cloudflare Full API surface that lets you register and manage without handoffs is the real unlock. Anything that forces a browser click or support ticket re-introduces the bottleneck.
-
Theo Ephraim 🧙♂️ (@theozero) reported@dbmikus @ericclemmons last I tried last on cloudflare sandboxes it was quite slow. Couldnt quite just restore the vm in its running state and many hoops to jump through.
-
lasan (@las_nish) reportedComparisons of Free Trial Abuse Prevention Services If you're running a SaaS with a free trial or focusing on PLG, authentication and abuse prevention are not the same problem. - WorkOS: If you're already using WorkOS, WorkOS Radar is probably the first thing I'd look at. For a WorkOS stack, WorkOS AuthKit + Radar makes the most sense. You don't need to bolt another authentication system onto your app just to get abuse signals. - Auth0, Supabase Auth, Better Auth: These are primarily identity/authentication platforms. Integrating only these can't prevent free trial abuse. - Custom: Like the previous options, you need a custom way to prevent free trial abuse. Most free trial abuse methods involve disposable emails, Google dot variations, Google/Gmail domain variations, and plus addressing. That's why even when you block bots via Cloudflare Turnstile or CAPTCHA, you can still get these abusers. The industry standards: - Block free trial abuse using lists hosted on GitHub: This is a pain in the ***. If you don't want to pay money, you can use a service that offers a generous free tier. - WorkOS Radar: This is mainly used at the enterprise level. They focus more on WorkOS-related integrations rather than integrations with other providers. - ZeroBounce, NeverBounce, MillionVerifier, DeBounce: These are mainly used to clean/validate emails. There are 100s of alternatives, and most are similar with minor differences. They all have disposable email checking APIs. - UserCheck: This is also an email validation API, but they focus on blocking fake email addresses. It's better than a basic email verification API. - Autheona: This is in the same category as WorkOS Radar and UserCheck, but with more features. It also focuses on fake user detection and is growing with a real user base. Now, pricing: - WorkOS Radar: First 1,000 checks free, then $100 per 50 checks. No application-specific logic changes. Easy to integrate and manage. - ZeroBounce: 100 free validations in the free tier, then pay-as-you-go, starting at 2,000 for $39, and so on. - NeverBounce: No free trial or use case, $8 per 1,000 checks. - UserCheck: 1,000 API requests per month in the free plan. The rule-based engine is not included in the free plan, and you can get up to 1 request per second. - Autheona: 3,000 checks per month, with the rule-based policy engine included. Standard API request rate limitations apply, similar to paid plans. Now, use cases: - WorkOS Radar: Block disposable emails, plus addressing, and Google dot variations. - ZeroBounce, NeverBounce, etc.: Block disposable emails. - UserCheck: Block disposable emails, plus addressing, and Google dot variations; detect public emails; email suggestions; syntax validation; role detection. - Autheona: Everything included in UserCheck, plus business/free/government email identification, deliverability checks, fraud patterns, punycode and mixed-script checks, VPN detection, and bot detection (not necessary if you already use CAPTCHA, Cloudflare, etc.). Final decision from me: - Use WorkOS Radar if you're already in the WorkOS ecosystem. It's harder to integrate with other auth providers. - Use ZeroBounce-like APIs if you need basic disposable email checks. They're not as good if you need a better free tier. - Use UserCheck if you only need email-related validation and want to stay within the free plan. - Use Autheona if you need the most generous free tier available with a custom policy engine. All services take a maximum of a few hours to integrate and test. Both UserCheck and Autheona have a similar approach: integrate once and never touch the code again.
-
Nathan Pierce (@norsegaud) reported@levelsio @Cloudflare Same, switched 5ish months ago and will never go back to namecheap!
-
Bob Tong (@bob80924) reportedhuge warning if you host with DMIT (or any premium VPS rn). attackers are scanning for badly configured SNI proxies to hijack your server and proxy OpenAI / Cloudflare requests for model distillation. it’s a highly organized attack. DMIT is permanently terminating any abused instances to protect their network rep. check your firewall rules before you lose your server.
-
Mesh (@MeshGateway) reportedMeshGateway just crossed 1M requests in less than 30 days, based on @Cloudflare network analytics. Peak day: 183K requests. We built the infrastructure for scale from day one. Now the usage is starting to show it. More agents. More merchants. More machine activity on @RobinhoodCrypto. Mesh is where it starts.
-
RealJBMangum (@RealJBMangum) reportedMost solo builders still treat deploy like a project. Cloudflare Workers + D1 + Pages flips it. Write the code. Push. It runs at the edge. No servers to babysit. I run 11 products this way. keep the stack boring and the ops near zero. What part of your current deploy still feels heavy?
-
Revanth x (@svsairevanth) reported@Cloudflare @CloudflareDev after adding second card it shows this Your account has an outstanding balance. Pay it from Billing before trying again. but no invoice generated. no bill . pls help @Cloudflare team
-
Jeremiah K (@neolaj) reported@dotgil #169 was the promotion to Cloudflare PR (production), so it was awaiting my old school manual review. I'll login and check the changes against the PR log. - Coder agent unit tests and opens the PR to integration branch. - Integration agent does integration testing and merges the PR - Deployment to production is strictly manual and waits for me to review before the deploy.
-
Akash.eth🌊 (@sheikhakash69) reported@0xBlue Cloudflare moving first is a big signal. Domain depth will decide winners.