Cloudflare status: hosting issues and outage reports

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.

Most Reported Problems

The following are the most recent problems reported by Cloudflare users through our website.

• Domains (33%)
• Cloud Services (29%)
• Web Tools (17%)
• Hosting (13%)
• E-mail (8%)

Live Outage Map

The most recent Cloudflare outage reports came from the following cities:

City	Problem Type	Report Time
Paris	Cloud Services	11 days ago
New York City	Hosting	14 days ago
Manchester	Domains	1 month ago
Angers	Cloud Services	2 months ago
London	Domains	2 months ago
Noida	Hosting	2 months ago

Full Outage Map

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:

• 
  Freddyツ (@InvestorFreddy1) reported 4 minutes ago

  In my days of bull-posting $NBIS, I haven't yet made a post about the other great companies that $NBIS is a part of. This is not a holding company. It is a portfolio of bets on infrastructure that the next decade of AI physically cannot run without - and most people covering it have not done the work to understand what is actually inside. ClickHouse is the one that keeps me up at night in the best way. Real-time analytics at a scale that makes most databases look like Excel. Cloudflare runs on it. Spotify runs on it. The entire AI observability space - every company trying to monitor model behavior in production - is converging on columnar databases exactly like this. ClickHouse is not a niche tool anymore. It is quietly becoming the plumbing. Then there is Avride. Autonomous delivery and robotaxi software, spun out of Yandex. They have active pilots with Grubhub and are deploying sidewalk robots in real cities today - not a demo, not a proof of concept, actual commercial operations. The market keeps pricing autonomous as a 2030 story. Avride is operating in 2026. CoreWeave exposure through the stack ties the whole thesis together. When GPU demand spikes, the companies that manage, route, and analyze that compute workload scale with it. NBIS is not one bet on AI. It is six or seven bets on the infrastructure layer sitting just below the headline names everyone already owns. Today's drop is a gift or a warning. I think it is a gift because none of the underlying businesses changed today - only the price did. What I am watching is the ClickHouse commercialization timeline. If they move toward a direct enterprise licensing push or any IPO signal before end of year, the market has not remotely priced that in yet. That re-rating would be violent. I bought at $50 and I have not sold a single share. That should tell you where I stand. What is the one NBIS holding you think is most underappreciated right now? #NBIS #AI

• 
  brendan (@brendonovich) reported 4 minutes ago

  @thdxr i've never used cloudflare until alchemy existed, i'm scared of wrangler configs

• 
  Kamran Khan (@ItsKamranK) reported 6 minutes ago

  @Rian_Visser @Namecheap Rian....worlds best company use Cloudflare for security and speed....if you don't use that's OK....I use Cloudflare CDN for almost every project....I don't have any issue...and why I will pay extra price in renewal charges, if I renew in same flat prices...

• 
  2poyDev (@2poygoy) reported 8 minutes ago

  Noticed money flowing into $JACKET, started digging into the site and twitter. What I found: 1. The token parasites off @jensenhuang (NVIDIA CEO). 2. Their site jacketrobinhood(.)lol redirects to robinnode(.)com running a ClickFix attack: a fake "Cloudflare verification" that tells you to press Win+R and paste text. That's running wallet-draining malware. NEVER do this. Smells like a scam. Don't trade it, don't visit the site, don't connect a wallet. CA in the comments, for onchain verification only. Not a buy.

• 
  Tejas (@stejas809) reported 14 minutes ago

  GitHub — version control (free) Claude — coding ($20/mo) Namecheap — domain ($12/yr) Cloudflare — DNS (free) Vercel — deploy (free) Clerk — auth (free) Supabase — backend + database (free) Upstash — Redis (free) Pinecone — vector DB (free) Resend — emails (free) Stripe — payments (2.9% per transaction) PostHog — analytics (free) Sentry — error tracking (free) Total cost to run a startup: ~$20/month No servers. No DevOps team. No funding required. Just an idea and WiFi. There has never been a cheaper time to build. 🚀 Today is the best time to bet on yourself and build the things ⭐

• 
  Flavio Amiel (@fba) reported 14 minutes ago

  Yet some very pro SEOs here say llms don’t matter. It does matter specially for SaaS in the building space. The strategy is: LLMs recommend you because is free to enter and easy of plug. You might or not upgrade at some point. I’m sticking with resend and cloudflare because if this. And I know the moment I need to upgrade I won’t even flinch. SaaS of the world: fix and keep your .md’s and llms.txt updated.

• 
  Matt (@meszmatew) reported 15 minutes ago

  Is anyone else having issues with cloudflare billing?

• 
  Ayush Chugh (@aayushchugh) reported 16 minutes ago

  A few days ago, our login API experienced a DDoS attack. This triggered a high volume of SMS notifications, resulting in unexpected operational costs. Although we had IP-based rate limiting in place, the attack was highly coordinated, utilizing rotating IP addresses and phone numbers to bypass our initial defenses. To mitigate the immediate financial impact, we temporarily disabled our notification micro-service. We have since implemented a frontend CAPTCHA to verify requests before they reach the server. Additionally, we are configuring advanced Cloudflare rules to better protect our infrastructure against future incidents.

• 
  Konstantinos (@kostasbotonakis) reported 17 minutes ago

  Cloudflare support: Health checks, checking a static page on Cloudflare Pages show plenty of outages. It’s been now 2 weeks

• 
  Lain on the Blockchain (@CryptoCyberia) reported 18 minutes ago

  @Valen_T_N So many major internet outages the last 2 years, more than the previous 28 years I have had on Earth. Amazon store went down for hours a couple months ago, and they held an emergency meeting where they reportedly told devs to stop using LLMs to code because it's sloppa. Cloudflare went down, killing most of the internet. Windows 11 updates have broken devices a half dozen different updates now. Nvidia had to unrelease a driver package, the first time doing so in decades. There are many more examples too of LLMs causing the final product to be significantly worse. The real spooky part is that when you try to name software that was newly made, had features added, or was upgraded in user experience in any way because of the magical power of LLM coding, you literally cannot think of even one (1) example.

• 
  Abdul Rauf (@armujahid) reported 19 minutes ago

  @karachism @argamingpk1 Will check. My setup is -> pihole (custom block list, dns cache) -> dnscrypt -> cloudflare zero dns. But yeah, noticed random issues on vanilla network without any custom setup.

• 
  Sudotech Limited (@SudotechLimited) reported 21 minutes ago

  X thought we were using a VPN. Here's what happened. MTN Nigeria uses a proxy. If you're on MTN, your traffic is automatically proxied. How we know: Logging into our Cloudflare account on Airtel always fails. On MTN, we can access Cloudflare and a few soft-banned service in Nigeria.

• 
  Josh (@joshmanders) reported 21 minutes ago

  @leodev So if I am understanding this correctly, using Cloudflare email is $21.45 for 50k emails? Honestly that's acceptable to me. Especially if they have good inbox placement and reliability. AWS is saturated with spammers and ****. I'll pay a premium to guarantee my stuff hits inboxes.

• 
  Erik ≋ 🇺🇸 Fight for Digital Rights 🇺🇸 (@ErikInCt_) reported 23 minutes ago

  @PorkPoncho PlayStation can't control when AWS ***** up. Come on bro, you're smarter than this. There's no switch that says, "Bypass AWS if AWS has issues." My site goes down if Cloudflare has issues, somethings you can't control.

• 
  syxncwtww (@syxncwtw) reported 27 minutes ago

  Does anyone know if cloudflare is down ??

• 
  Duane C (@DuaneC6) reported 28 minutes ago

  @CryptoCyberia The internet was never a system of tubes, it has always been 500 micro-services pointed at each other like loaded firearms. People on remote, nearly-uncontacted islands know when Cloudflare goes down, and now it goes down all the ******* TIME.

• 
  Schwerelos.io (@schwerelosio) reported 30 minutes ago

  +37% following every tracked call on $ARM since March, 4 scored calls, 50% hit rate. The catalyst is concrete: Arm's AGI CPU, a data center chip built for agentic AI workloads, with Meta as lead co-development partner and OpenAI, Cloudflare, SAP, and SK Telecom already committed. Semiconductors don't usually have this kind of customer list locked in before the chip ships.

• 
  Jake Gevorgian (@JakeGevorgian) reported 37 minutes ago

  @_slowstacking @FinancialPhys It's not like I'm not putting money in web. I spend $30k worth of time as I'm also tek savvy and do these seo stuff myself. What I've missed big time was cloudflare integration and schema. But even with that, I see companies who pop up on google first pages that I've never heard of in woodworking communities I am in... Btw, I don't think "competitor" is a valid term in this day and age for craftsmen in wood. It's not like we're selling car parts or plumbing supplies imported from China. :) this is what I'm stressing about---Google should focus on local American creators for people who look for local makers.

• 
  Art Chicken 🐓 (@ArtChicken4) reported 37 minutes ago

  From Jovan Hutton Pulitzer's Telegram- - For tech nerds understanding the PCAP fraud: The mechanism works, and every input is public. Rosters of US election officials are published (state SoS directories, EAC, NASS, commercial lists). Take each office's email domain → MX lookup → resolve the mail host to an IP → geolocate it. You now hold a table of "jurisdiction → IP → city/lat/lng" covering every election jurisdiction in the country, built entirely from DNS, without ever sending a packet to an election office. That table would look authoritative and survive spot-checking — the IPs are real, the org names are real, the geography is real. It would also be probatively empty, because an MX record identifies who handles that office's email. It says nothing about vote systems. The signature of an MX-derived list would be hundreds of jurisdictions collapsing onto a handful of shared mail-provider IPs — Microsoft 365 (*.mail.protection.outlook.com), Google Workspace, Barracuda, Proofpoint — because that's who most county governments use. What your file actually shows I tested it. The target roster is a complete enumeration of election jurisdictions, and the counts are exact: State Rows Actual jurisdiction count Massachusetts 351 351 municipalities Connecticut 169 169 towns Texas 254 254 counties Georgia 159 159 counties Virginia 133 95 counties + 38 independent cities Kentucky 120 120 counties North Carolina 100 100 counties Iowa 99 99 counties One row per jurisdiction, zero duplicates in any state. Real network traffic doesn't distribute itself one-event-per-administrative-unit. This is a roster walk. But the IPs are coarser than your MX hypothesis. Eleven states collapse to a single IP for every jurisdiction: 490 Maine town clerks        -> 13.32.25.126     (AWS CloudFront edge) 351 Massachusetts clerks     -> 45.60.195.2      (Imperva/Incapsula WAF) 246 Vermont town clerks      -> 45.60.45.214     (Imperva/Incapsula WAF) 237 New Hampshire clerks     -> 199.192.7.129 169 Connecticut town clerks  -> 199.107.32.42 160 Texas election admins    -> 98.129.145.194   (Rackspace) Plus 104.17.x / 104.18.x (Cloudflare) across 189 more rows. Those aren't mail servers — they're CDN and WAF edge addresses, the public front door of a state's website. A CloudFront edge IP is shared by thousands of unrelated customers; it isn't "Maine's election system," and you can't route vote data to it, because it terminates HTTPS for public web content and nothing else. So the lookup behind this file was one resolution per state's public web presence, cloned across every jurisdiction in that state. An MX-per-office build would have been more sophisticated than what was actually done here. And 253 rows have TargetIP = literally * — a failed lookup, no address at all. Those rows still carry 70,448 flipped votes. Votes attributed to an intrusion against an IP that does not exist. Bottom line Your instinct is right about the class of technique: a public roster plus DNS resolution manufactures a nationally-complete, real-looking IP table with no access to anything. That's the general answer to "could this manufacture data" — yes, trivially, and it's undetectable if you only check whether the IPs are real. The detection method is the reverse question: not "is this IP real?" but "what does this IP actually serve?" Real intrusion data resolves to the specific host attacked. Manufactured data resolves to whatever the jurisdiction's public name happens to point at — a CDN, a WAF, a mail gateway, a hosting provider. That's what's here: 490 distinct Maine towns, all pointing at one Amazon CDN address.

• 
  KnowTechGlobal (@KnowTechGlobal) reported 40 minutes ago

  That difference changes architecture. If your app depends on slow upstreams, the platform that charges less for waiting can look cheaper even when the code is identical. The winner is not "Cloudflare" or "AWS" in the abstract. It is the workload shape.

• 
  Polymarket Alpha (@Polymarketalpha) reported 41 minutes ago

  🚨 JUST IN: Bots now generate more web traffic than humans. According to Cloudflare, bots accounted for 57.5% of global web page requests in June 2026, while human traffic fell to 42.5%. This marks a historic turning point for the internet. AI crawlers, automated systems and intelligent agents are no longer a minor part of the web—they are becoming its dominant users. Cloudflare’s CEO had previously predicted that bot traffic would not surpass human traffic until 2027. Instead, the milestone arrived a year early. The internet is rapidly shifting from a network built primarily for humans to one increasingly accessed, indexed and operated by machines. Technological progress—or the beginning of a less human internet?

• 
  adas🧦🌹 (@adastroworld) reported 44 minutes ago

  @thsottiaux just does a cloudflare auth "human check" loop when trying to sign in from the browser lol

• 
  ₳ndreas (@mrgrauel) reported 44 minutes ago

  @tibor_tee @cursor_ai T-E51116 Same issue with Quad9, Cloudflare, Google as DNS.

• 
  Danilo Falcão (@danilofalcao) reported 45 minutes ago

  Cloudflare reports that nearly 70% of BGP paths have their ORIGIN attribute rewritten by transit providers for traffic advantage, not correctness. It argues that ORIGIN should be deprecated in route selection. Network operators should examine the evidence and policy impact.

• 
  Aiden (@WallisDev) reported 45 minutes ago

  @thdxr mostly terraform and a custom deploy pipeline that just pushes code directly to the workers. Config changes land through terraform updates It sucks. this stuff and: * No workload identity federation * Their permissions story is simple - too simple hold Cloudflare back for me

• 
  DR.PIXEL (@pixelpatchit) reported 54 minutes ago

  Swapdesk Alpha: DNS Expansion and Reliability Improvements As Swapdesk Alpha continues to mature, we plan to expand beyond our current Cloudflare and Google DNS support by adding additional DNS provider options. These providers have given us a strong foundation during the alpha phase, allowing us to focus on building and testing core functionality while maintaining reliable connectivity. During the THORChain swap process, users may occasionally experience intermittent connection issues while the application is retrieving required swap information, such as the deposit address needed to complete a transaction. These issues are not consistent and do not occur during every swap, but when they happen, they can create confusion because they occur during an important step in the transaction flow. It is important to clarify that an error message during this stage does not automatically mean a transaction has failed or that funds are at risk. In many cases, the issue is related to communication between the application and supporting services, which may include DNS resolution, API availability, network routing, or other connectivity factors. To improve reliability, future versions of Swapdesk Alpha will introduce broader DNS support, improved fallback handling, and additional resilience measures. The goal is to provide users with a smoother experience, reduce unnecessary interruptions, and ensure that Swapdesk remains dependable as adoption grows. We appreciate the feedback from early users helping identify areas where reliability and user experience can continue to improve.

• 
  Lucas Rodriguez (@LucasSaasbr) reported 56 minutes ago

  Cloudflare blocks or challenges bad requests from hitting my website. #cloudflare

• 
  Sample (@sample) reported 57 minutes ago

  Cloudflare suffers a parity issue where platform features/runtime configs are Wrangler-only; omitted from native API/Terraform providers. So one can't choose purely declarative IaC or pure Wrangler; they're forced a hybrid & IaC tools have to shell out to Wrangler CLI subroutines

• 
  Dr. Gonzo (@N3DrGonzo) reported 58 minutes ago

  @AnisDrawn PSN goes down more often than CloudFlare. And CloudFlare has an outage QUOTA. But yes, please tell me how an all digital ecosystem for a console is a good thing.

• 
  David Frosdick (@DavidFrosdick) reported 58 minutes ago

  Cloudflare Email then sends the customer a link to a watch page. They can react, or reply, and that comes back into D1 against the original order. Whole loop, no third-party service in the middle.