Cloudflare status: hosting issues and outage reports
No problems detected
If you are having issues, please submit a report below.
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.
Problems in the last 24 hours
The graph below depicts the number of Cloudflare reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.
At the moment, we haven't detected any problems at Cloudflare. Are you experiencing issues or an outage? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by Cloudflare users through our website.
- Domains (40%)
- Cloud Services (27%)
- Web Tools (13%)
- Hosting (13%)
- E-mail (7%)
Live Outage Map
The most recent Cloudflare outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
|
|
Domains | 16 days ago |
|
|
Cloud Services | 27 days ago |
|
|
Domains | 29 days ago |
|
|
Hosting | 1 month ago |
|
|
1 month ago | |
|
|
Web Tools | 1 month ago |
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:
-
Daniel Hayes Smith (@danielhayesmith) reportedFable5 is shitting the bed for me building on react and Cloudflare. Am I just doing **** wrong with it?!?! Like it is way ******** off
-
Ruchit Dalwadi (@ruchitdalwadi) reported@Cloudflare @OpenAI Search quality is increasingly a data-contract problem. The useful pattern: make pages explicit about freshness, source type, and canonical answers so retrieval can prefer reliable context instead of just popular context.
-
EnesInvestUS (@enes1050392) reported$NET announced a research pilot with OpenAI today. Looks like a routine partnership headline, but there’s a bigger story underneath. The pilot itself is simple. Cloudflare will share network signals like content freshness, traffic quality and actual page changes with OpenAI, who will test whether these signals make ChatGPT’s crawling and indexing better. Here’s why it matters. Cloudflare’s own data shows more than half of AI crawler traffic is wasted re-fetching pages that never changed. Wasted compute for AI companies, wasted bandwidth for site owners. Since over 20% of the web sits behind Cloudflare, it’s the only player that actually sees what changed and what didn’t. Nobody else has that vantage point. The bigger picture: Cloudflare is quietly building the economic layer of the agentic internet. It started with Pay Per Crawl last year, now it’s moving to Pay Per Use, where creators get paid when their content shows up in an AI answer, not when a bot fetches a page. And starting September, training and agent bots get blocked by default on new domains while search stays open. So the setup is clear. AI companies need content, millions of sites want to protect and monetize theirs, and Cloudflare wants to be the tollbooth in between. Today’s OpenAI deal is the strongest validation of that thesis so far, because the biggest player in the industry just sat down at the table. Near-term revenue impact is basically zero, let’s be honest. Valuation isn’t cheap either, the stock trades near its 52-week high and insider selling has been heavy lately. But for the long-term thesis, this is another chapter in Cloudflare’s shift from a CDN and security company into the traffic and royalty infrastructure of the AI era.
-
Digital in Blue (@digital_in_blue) reported@betablacklotus Yep. No issues with doing this in cloudflare. Check it out! My site has no Wordpress and no databases.
-
Evan Oslick (@eoslick) reported@DanielMiessler I still think I wasn’t clear. I have been pushing for 402 being used and this type of strategy for a long time. My issue is with the reach that Cloudflare has there is significant risk in them doing it. I don’t accept “it’s not there now, something is better than nothing” is a merit counter point to handling the risks to those Cloudflare currently serves. Hey, look, we don’t like your content…. We’ll change the income percentage you get.. Hey, yeah, look, you buy this service we’ll decrease our service charge to you… Separations of duties is a recommendation for a reason. Monopolies are prevented (well supposed to be) for a reason.
-
Shreyas Pandey (@Shreyas_Pandeyy) reportedthe cloud wars are getting ridiculous. cloudflare ships something. vercel ships something the next week. cloudflare responds. vercel acquires another company. cloudflare launches another product. somewhere in the middle, aws is still asking you to click through 17 IAM screens. competition has never been this good for developers. every launch from one forces the other to ship faster. containers. auth. edge. ai. compute. if you're building devtools today, your biggest competitor might not be another startup. it's one of these two deciding your category is interesting.
-
Cleper 🌋 (@yaircleper) reportedso @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?
-
T.God (@tgod_ajayi) reportedSpent 2 days convinced my server had issues. It didn't. Nigerian carriers just couldn't route to it. Bad IP announcement from my host at the LACNIC level. Moved DNS to Cloudflare. Fixed in an hour. The bug is never where you think it is.
-
Godwin Iyke (@GodwinCod3s) reportedCloudflare blocks or challenges bad requests from hitting my website. #cloudflare
-
Chinoman10 (@Chinoman10_) reportedWhat a really sad day... Massive fan of BetterAuth, sucks that it's joining Vercel instead of Cloudflare :( At least CF got Astro and Outerbase... but Vercel got ShadCN 😭 I know competition is good, but this is killing me 🙃
-
Benjy Boxer (@boxerbk) reported@eastdakota @dani_avila7 make the agents suffer like the rest of us! 🧠. Good thing if you use Cloudflare, the agents' DDOS attacks for bad ads won't take you down.
-
dan ⚡️ (@mynamebedan) reportedonly cloudflare really could've done this. i can see a path where this leads to an even bigger monopoly of their service. the stripe effect but much larger. i happen to really like this model of paid services on the internet, it's so simple and effective
-
Jaro (@jaro3th) reported@darkmembo @levelsio @Cloudflare Crazy support from cloud flare Ggs mark
-
Mert Metin Tekdemir (@mertmetindev) reported📂 SaaS Stack ┃ ┣ 📂 Frontend ┃ ┣ 📂 React ┃ ┣ 📂 NextJS ┃ ┣ 📂 Vue ┃ ┣ 📂 TailwindCSS ┃ ┗ 📂 Shadcn UI ┃ ┣ 📂 Backend ┃ ┣ 📂 NodeJS ┃ ┣ 📂 Django ┃ ┣ 📂 Laravel ┃ ┣ 📂 FastAPI ┃ ┗ 📂 Express ┃ ┣ 📂 Database ┃ ┣ 📂 PostgreSQL ┃ ┣ 📂 MySQL ┃ ┣ 📂 MongoDB ┃ ┣ 📂 Redis ┃ ┗ 📂 Supabase ┃ ┣ 📂 Auth ┃ ┣ 📂 Clerk ┃ ┣ 📂 Auth0 ┃ ┣ 📂 Firebase Auth ┃ ┣ 📂 Supabase Auth ┃ ┗ 📂 NextAuth ┃ ┣ 📂 Payments ┃ ┣ 📂 Stripe ┃ ┣ 📂 Paddle ┃ ┣ 📂 Dodo Payments ┃ ┣ 📂 Lemon Squeezy ┃ ┗ 📂 Polar ┃ ┣ 📂 Emails ┃ ┣ 📂 Resend ┃ ┣ 📂 SendGrid ┃ ┣ 📂 Mailgun ┃ ┣ 📂 Postmark ┃ ┗ 📂 Amazon SES ┃ ┣ 📂 Storage ┃ ┣ 📂 AWS ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 Google Cloud Storage ┃ ┣ 📂 Supabase Storage ┃ ┗ 📂 Uploadcare ┃ ┣ 📂 Deployment ┃ ┣ 📂 Vercel ┃ ┣ 📂 Netlify ┃ ┣ 📂 Railway ┃ ┣ 📂 Render ┃ ┗ 📂 AWS ┃ ┣ 📂 Domains and DNS ┃ ┣ 📂 Namecheap ┃ ┣ 📂 Hostinger ┃ ┣ 📂 Cloudflare DNS ┃ ┣ 📂 Google Domains ┃ ┗ 📂 SiteGround ┃ ┣ 📂 Analytics ┃ ┣ 📂 Google Analytics ┃ ┣ 📂 Plausible ┃ ┣ 📂 PostHog ┃ ┣ 📂 Mixpanel ┃ ┗ 📂 DataFast ┃ ┣ 📂 Monitoring ┃ ┣ 📂 Sentry ┃ ┣ 📂 LogRocket ┃ ┣ 📂 Datadog ┃ ┣ 📂 NewRelic ┃ ┗ 📂 UptimeRobot ┃ ┣ 📂 DevOps ┃ ┣ 📂 Docker ┃ ┣ 📂 Kubernetes ┃ ┣ 📂 GitHub Actions ┃ ┣ 📂 CI CD ┃ ┗ 📂 Terraform ┃ ┣ 📂 Search ┃ ┣ 📂 Algolia ┃ ┣ 📂 Meilisearch ┃ ┣ 📂 Elasticsearch ┃ ┣ 📂 Typesense ┃ ┗ 📂 OpenSearch ┃ ┣ 📂 AI Integration ┃ ┣ 📂 OpenAI API ┃ ┣ 📂 Anthropic API ┃ ┣ 📂 Replicate ┃ ┣ 📂 HuggingFace ┃ ┗ 📂 Gemini API ┃ ┣ 📂 Integrations ┃ ┣ 📂 Zapier ┃ ┣ 📂 Make ┃ ┣ 📂 n8n ┃ ┣ 📂 Pabbly ┃ ┗ 📂 Webhooks ┃ ┣ 📂 Security ┃ ┣ 📂 SSL ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 WAF ┃ ┣ 📂 Rate Limiting ┃ ┗ 📂 Secrets Management ┃ ┣ 📂 Marketing ┃ ┣ 📂 Search Console ┃ ┣ 📂 Outrank ┃ ┣ 📂 Buffer ┃ ┣ 📂 Analytics ┃ ┗ 📂 Kit ┃ ┗ 📂 Customer Support ┣ 📂 Intercom ┣ 📂 Crisp ┣ 📂 Zendesk ┣ 📂 Tawk ┗ 📂 HelpScout
-
Ewan (@ewan_tindale) reportedThe majority of this was a 1 shot. Fable handled all the "models", animations, zombie sounds, shooting sounds etc by itself (downloaded them from online I guess? I didn't pay much attention) Even for the game design, I just told it to copy the fun parts of COD zombies but for the browser using @threejs then I followed up to fix a few small issues with the menus, multiplayer, box collisions, melee range, added some music tracks. Running on @Cloudflare Workers/Durable Objects
-
Jen (@atryeu1) reported@CriterionDaily @THR Fix or get rid of CloudFlare! Started locking me out with "browser not supported" 9 out of 10 tries to load the site but works fine the 1 try. My browser is up to date & fine. CloudFlare is a broken piece of crap everywhere it's used.
-
Alan Tracey Wootton (@alan_t_wootton) reportedWhat's interesting is that the request to get the Duck goes from your browser, up to cloudflare, then down to my laptop (which is always running), back to cloudflare and then down to your browser.
-
Drewski (@SmellsLikeDrew) reported@Eli5defi @Cloudflare x402 was the missing piece tbh HTTP-native payments mean machines settle per-request with no login walls or card fees choking flow Sentient's autonomous networks are gonna feast on this 🤝
-
Anthony (@anthony_codes) reported@dillon_mulroy @bairdcodes @dok2001 damn. cloudflare ballin on a budget?
-
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.
-
Codemonger (@codemonger00) reportedStartup Founders Pack - Claude = coding. ($20/mo) - Supabase/Convex = backend. (Free) - Vercel = deploying. (Free) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build .
-
Ayush Chugh (@aayushchugh) reportedOkay so my hypothesis was correct and the flyer was the main issue only. Imagine if I am buying 10 tickets together and adding those to my wallet, it would download a flyer from the bucket 10 times and optimise those using sharp individually even though the flyer was same for each ticket. So now, I have implemented a caching mechanism which will cache that flyer. Also, we are now using Cloudflare images for our flyer but passes were implemented with the S3 approach so now we are downloading the smaller flyer using Cloudflare image's transformation functionally. These are the new stats
-
Baby Blue Viper (@babyblueviper1) reported@boydcohen @Cloudflare Real gap, real fix - a spend cap enforced before the payment exists is exactly the missing piece. Worth naming the next layer: your cap answers was this spend ALLOWED. Ours answers was the DECISION to spend actually sound. An agent can stay under budget and still buy garbage.
-
Frisian06 (@Frisian66) reported@axios @Cloudflare @eastdakota AI can't answer my questions, pulls incorrect bullshit from the internet and absolutely sucks at customer service. Somehow AI is going to be better at cutting my hair, making me food, fixing my car and replacing my roof? Nonsense.
-
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
-
Nick Kusters (@NKCSS) reported@levelsio @Cloudflare Is this a free service they provide? Have not looked at it, just moved to SES because it just unblocked the issue and is very cheap, but good
-
burak emre (@bu7emba) reported@_jasonsilberman I had the same issue, created a support ticket and got a reply only (!) a month later. I had to settle my invoice to prevent account suspension but left Cloudflare workers/AI ecosystem and lost my trust. They're just a CDN provider to me know.
-
Santiago Arias (@santiariasgonz) reported@wholemars @levelsio @Cloudflare Twillio sucks
-
CyberForget (@cyberforget) reported@levelsio @Cloudflare I thought you was self hosting your own email service - or have things changed?
-
Alex Y (@AlexYusdut) reportedhosts auto-issue via Let's Encrypt. redirect loops just wait, don't fiddle - Cloudflare proxy (orange cloud) in front of Vercel/Netlify →It silently fails for 2 reasons: - DNS hasn't propagated yet →HTTPS: you don't buy a cert in 2026 —