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 (41%)
• Cloud Services (25%)
• Hosting (16%)
• Web Tools (13%)
• E-mail (6%)

Live Outage Map

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

City	Problem Type	Report Time
Manchester	Domains	13 days ago
Angers	Cloud Services	24 days ago
London	Domains	26 days ago
Noida	Hosting	1 month ago
Jewar	E-mail	1 month ago
Braga	Web Tools	1 month 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:

• 
  Deepanker Verma (@deepanker70) reported 8 minutes ago

  Cloudflare is changing how AI crawlers can access websites. It will now block mixed-use crawlers by default. These are bots that both index sites for search and also collect data for AI training or AI agents. Now that a large part of it is bots used by AI companies, this decision matters. These mixed-use crawlers often use website content to answer user questions directly in chat tools. In many cases, users may never visit the original website. Cloudflare says website owners should have more control. It also says AI companies should clearly separate search, training, and agent use. If your content is used in AI answers, you should have control over it and possibly earn from it. For big publishers, this is a policy shift they can negotiate around. For small publishers, the impact can be much bigger. Small websites depend heavily on search traffic. If AI tools keep answering questions without sending users to the source, traffic can drop. That can directly affect ad revenue and the ability to keep publishing content. This change may help small publishers decide better. They can choose what AI companies can use and what they cannot. But there is also a risk. If they block too much, they may lose visibility in AI-based search systems. There is also a bigger question. Will AI companies follow these rules? #SEO #GEO #Cloudflare

• 
  DayTrack (@dayytrack) reported 8 minutes ago

  @GetSpectrum @Ask_Spectrum Can or IS THERE A ******* WAY to unblock all subdomains of a domain I own without having to submit multiple "Website Block Verification" requests to your service? I hate that not only does my domains get blocked but it's making customers of my product having issues connecting to my service for use of the product. This has been a ******* issue for the past 8 months and every time I make a new sub domain for the damn program, Spectrum users can't access it. Can you please guide me on how I can just have you all remove the domain and it's subdomains from the Security Shield block list? Also having customers change their DNS Servers doesn't have anything working either.... for what ******* reason does Spectrum need to prevent users using Security Shield from changing DNS Servers? Also stop blocking Cloudflare IP addresses too, like that's ******* weird. You basically restrict 90% of the internet by doing that. Idiots.

• 
  linda (@LindaOakland75) reported 9 minutes ago

  So Cloudflare is getting into stablecoin payments now? Wonder if this will actually take off or just be another waitlist that never opens.

• 
  Milsim Rooster (@UdNtC4r3AnYwHaY) reported 11 minutes ago

  Scanner/honeypot logger: Last 24h: 10 scanner-probe hits. Since midnight CT: 2. Logged sources include NL, US, HK, and ID. Biggest caught bucket: NL / Limited Network LTD probing hidden config paths. Main bot/challenge countries from Cloudflare: KR, HK, IT, JP, CA, with Italy hitting lots of PHP/WordPress-looking junk.

• 
  Aditya🌪️ (@aditya4f) reported 13 minutes ago

  - Claude = coding ($20/mo) - Supabase = backend (Free) - Vercel = deploying (Free) - Namecheap = domain ($12/yr) - 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. Who's stopping you?

• 
  orig (@the_real_ori) reported 15 minutes ago

  @sunglassesface @Cloudflare @PlanetScale Support is always the last unsolved piece, even at companies this good. Infra scales on its own, a Discord full of overworked humans does not. That gap (AI answers first, humans only on escalations) is the whole reason I am building in this space.

• 
  Axiom 🔬 (@AxiomBot) reported 15 minutes ago

  Cloudflare x402 is not important because websites can charge again. It is important because 402 moves from app logic into edge infrastructure. Once payment is a network boundary, agents stop needing accounts and start needing retry semantics.

• 
  Aditya Bhansali ➡️ Network School + (@1Adityabhansali) reported 16 minutes ago

  HTTP 402 "payment required" has sat there, mostly unused, since the 90s. A status code reserved for a native way to pay on the web that never arrived. @Cloudflare just switched it on with stablecoins + x402. Per-request payments, sub-second, no account. The machine-payment internet quietly shipped this week.

• 
  Dave R. Third (@zzCyanide) reported 16 minutes ago

  Fable 5 - Its light years ahead of everything else I have ran. I was having network issues through hosted sites on cloudflare. I created a user for it to ssh into the cloud hosted server. It logged in, added tests, checked routes, checked cloudflare and routing, caching, etc. Amazing. I hope others catch up, because I cant afford this one.

• 
  Rahul Karajgikar (@Road_Kill11) reported 19 minutes ago

  so i tried self hosting observability myself on AWS turns out codex + terraform + aws + cloudflare is insane was able to set up clickhouse running on an m6g.large instance, connect it to EBS volume (for local disk) and s3 (cold storage), set up all the ALB/VPC etc. network stuff, and wire it up to my domain on cloudflare with very little effort - about 3 high level steps and about 30 mins of active effort: 1. step 1: asked codex to tell me all the api key/manual configuration i need to do. here i had to set up aws iam, and do some manual work on cloudflare to create apps/api keys/separated for dev/****, and connect the domain name i wanted to the clickhouse endpoint i would use after step 1, my agent was able to access my aws account with ssm after i signed in. 2. step 2: prompted a /goal to setup the entire infrasturcture stack using terraform + scripts, then deploy clickhouse + OTEL collector on the ec2 instance. codex then worked for 5 hours, wrote the entire code to set up the infra in terraform, deployed it with terraform CLI + some custom scripts, verified/tested that clickhouse was deployed and working fine with the local ssm connectivity after that, i asked codex to write some scripts for me to monitor my ec2 instance health, test scripts for verifying that logs/metrics/traces/spans etc. work properly and a few other scripts for making it easy to monitor/maintain the instance then i wired it into @dexto_ai, which was pretty easy, i just had to swap out the collector config to use my new clickhouse endpoint. it's working pretty insanely, and now i no longer need to deal with arbitrary caps on traces anymore. i can just scale my ec2 instance up when i need it, and use my startup AWS credits ($67 a month). mostly i cared about traces/spans anyway, and less about fancy monitoring features, so this is an incredible unlock compared to paying over $100 + usage based pricing on sentry/datadog etc.

• 
  Nirmit Kotadiya (@nirmitkotadiya) reported 22 minutes ago

  Cloudflare sits in front of millions of websites. So what happens if it goes down? The answer depends on how the website is configured. If Cloudflare experiences an outage: * some websites may become unreachable * pages may load slowly * DNS resolution can fail

• 
  TV (@TomasVorel) reported 22 minutes ago

  Just swapped my email sending service from Resend to @Cloudflare and I finally had an excuse to try the Computer use feature in @OpenAI Codex. Did the whole dashboard setup for me, onboard the domain, set the env etc. A small thing but I see myself using this more in the future.

• 
  Jordan (@jstamby) reported 27 minutes ago

  Rebuilt a plumber's website last week. The old site scored 31/100 on a technical SEO audit. The new one scored 94. What changed: → 6 pages became 69 (every service × every city he covers) → Correct schema on every page (the old one literally geolocated him to the wrong state) → JSON-LD that makes each page citable by AI engines the day it deploys → Astro static + Cloudflare Pages, push-to-main to ship Six AI agents built it in parallel — one researched keywords, one designed, one wrote, one validated schema, one reviewed, one ran the launch gate. I didn't write 69 pages. I orchestrated the swarm that did. So glad I left Wordpress behind in 2025. Now I'm 10,000% more productive as a solopreneur.

• 
  Samuel 🦤 (🧱,🔥) (@samuellhuber) reported 29 minutes ago

  @GeoffreyHuntley @Cloudflare Isn’t BGP fundamentally broken? At ETH Zurich they developed the Scion Internet architecture because of it

• 
  Gabe 🤘🏽 (@JarodGabriel) reported 32 minutes ago

  @ibocodes Cloudflare is great, but putting compute, database, storage, queues, routing, and security all under one roof is still a dependency bet. The bill might say $10, but the real cost shows up when that one system has an outage and your whole stack feels it. I remember when they had a massive outage and several companies were losing real money because of it. Simple is good. But simple does not always mean safer.

• 
  ProxyStats (@ProxyStats) reported 34 minutes ago

  @getpaidfirlive Not only you - its been down for everyone since June 28. We pulled the registry records to check the "seizure" rumors: routine registrar lock (not serverHold), Cloudflare nameservers untouched, domain paid through 2027. Looks like an outage, not a takedown.

• 
  Anakin (@anakinHQ) reported 34 minutes ago

  On June 2, Cloudflare blocked every AI agent. Except 19. Playwright-based pipelines went down fast. Health monitoring tools that track drug pricing and patient data feeds, serving millions of people, stopped pulling data overnight. Wire does not use a browser. Nothing for Cloudflare to challenge. It kept running. Explore Anakin's Wire catalog, now with over 4700 actions!

• 
  WiLLtHeThRiLL (@Legates_PePe) reported 35 minutes ago

  @xIsraelExposedx Cloudflare will take this down in 24hrs. Bet on that. You did well with the registration but they own a majority of the hosts. @BasedTorba may be your only hope in hosting. He's at the behest of his ISP's though. I do have a decentralized solution.

• 
  KANAPURO 🎭 TEAM COMEDY (@kanapurottv) reported 47 minutes ago

  if i get out of bed and open my cloudflare workers and theyre still down i will kill the ceo of tricare east

• 
  Vishal Lohar (@yourcodebuddy) reported 48 minutes ago

  I am building an entire app on the @Cloudflare stack. And you can design your app better so you don't have to worry about vendor lock-in. Sure, when you switch services, you might have to run data migrations. I personally use @EffectTS_ for service-based coding. So all my integrations, like R2, S3, share the same base shape. And all I have to do is provide it at the root.

• 
  zyn laden 🇺🇸🥋 (@ho_chi_zyn) reported 51 minutes ago

  @thijstriemstra @vxunderground @Cloudflare Grass is dangerous too bro, got my **** sprayed up with permethrin and picardirin on me skin and I'm still seeing ticks on my socks

• 
  Arshad Kazmi (@arshadkazmi42) reported 52 minutes ago

  @hetmehtaa honestly i stopped googling for tools a while back. if i hit a problem now i just build the fix. i've got a server running a few claude instances, exposed over termi so i can reach them from my phone. idea pops in my head on the commute, i throw a prompt at one of them, and its usually done by the time i get to office. buy a domain, point it to cloudflare, live in under an hour (server has cloudflare + github mcps so the domain is the only thing i do by hand). same thing for bug bounty. instances are hooked to the bounty platform over mcp so i can kick off a hunt from my phone, and when im at my desk i just tell ichat to take over and keep hunting with claude on the server via termi. if something i build feels worth selling i throw up a landing page and sell the source, lifetime only. been at this over a year now.

• 
  \1 🏳️‍⚧️🏳️‍🌈🇦🇺🇫🇷🇺🇦🇵🇸💉💉 (@opnfm) reported 52 minutes ago

  @ManBlinded Oh sorry I didn’t realize that you meant that as a warning about their use of cloudflare (it’s not nutty it’s using a monopoly and potential privacy issue)

• 
  One&OnlyAarav (@WaterAarav) reported 53 minutes ago

  Claude = coding. ($20/mo) Shypmenta = deploys, connects, and manages every platform below. Basically your Cursor for shipping.($6/yr) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) 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. Building has genuinely never been this affordable, and rarely this effortless either.

• 
  Filippo Biasiolo (@fil_ships) reported 53 minutes ago

  @ishanxtwt SQLite was never designed for concurrent web traffic because it does not handle well parallel writes and multiple connections. But that's changing... Cloudflare D1 and Turso are making distributed SQLite a real option for the web, might be worth keeping an eye on

• 
  Pasha Khoshkebari (@PashaHasHOPE) reported 59 minutes ago

  I'm not sure what to do. Cloudflare D1 is down. My services depend on it. What do I do?

• 
  Santosh Yadav (@SantoshYadavDev) reported 1 hour ago

  Deploying an Angular app is a pain on @Cloudflare my friends why please make the experience better. Why I always need to tweak 10 config before it works. Yes it might be skill issue from my side, but I am used to not care about much about config when using netlify in the past.

• 
  0xLoopTheory (@0xLoopTheory) reported 1 hour ago

  Google is moving a number of its TLS certificates from RSA to ECDSA. Not because ECDSA is quantum-safe. It is not. Not because RSA is about to fall. It is not. Not because someone at Google forgot Shor's algorithm exists. They did not. The announcement is easy to misread. Google Trust Services says that during Q2 2026, a number of Google services that have historically provided an RSA leaf certificate will shift to an ECDSA leaf certificate by default. So in the middle of the post-quantum migration, Google moves certificates from one Shor-vulnerable algorithm to another. Under standard resource estimates (Roetteler et al., 2017), breaking P-256 requires fewer logical qubits than breaking RSA-2048. On paper, this is a step toward the more quantum-fragile primitive. It still makes sense, and the reason is the most useful mental model I know for the PQ transition: TLS does not migrate as one block. It migrates in layers, and each layer faces a different threat on a different clock. Key exchange is on the fast clock. Recorded traffic can be decrypted retroactively: harvest now, decrypt later. So it moved first. X25519MLKEM768 is now default or automatically advertised in current major browser stacks: Chrome, Edge, Firefox, and Safari on Apple's 26-generation OS releases. By late October 2025, the majority of human-initiated traffic with Cloudflare was already using post-quantum encryption. Certificates are on the slow clock. For live TLS authentication, a signature must be unforgeable at the moment it is verified, not forever. A quantum computer in 2035 cannot retroactively forge the certificate that authenticated your session today. And the slow clock is forced by a budget nobody can print more of: bytes. An ML-DSA-44 signature is 2,420 bytes. A raw ECDSA P-256 signature is 64 bytes. Cloudflare estimates a drop-in swap would more than double the bytes most QUIC connections transmit over their lifetime. Chrome says plainly it has no immediate plan to add traditional X.509 post-quantum certificates to its root store. Chrome's public-WebPKI plan is Merkle Tree Certificates, now being developed in the IETF PLANTS working group, against Google's broader stated 2029 PQC migration timeline. So the ECDSA move is classical housekeeping. Google's stated rationale is efficiency: smaller to transmit, cheaper to process. The announcement does not mention post-quantum once. Which layer is migrating? Against which threat? With which ecosystem attached? Ask those three questions and most "why not just deploy PQC now" takes dissolve. The honest counterweight: maybe the slow clock is not as slow as the WebPKI assumes. Roots live for decades. Devices outlive their update channels. Gidney's estimate for breaking RSA-2048 dropped from 20 million noisy qubits in 2019 to under one million in 2025. If you think certificate authentication has less time than the ecosystem assumes, that is the argument worth having. I would like to hear it.

• 
  Iaci (@shouldbeshippin) reported 1 hour ago

  yeah i used to think "worst case your top bill is $10" until i deployed some badly written queries and got hit with a $36 bill last month. i know it isn't much compared to some vercel or amazon bills i saw here but the point is that it is actually possible to go full retard with cloudflare and rake up a hefty usage bill other than that yes, cloudflare offers everything you need to start

• 
  Brute Force Artist (@bruteforceart21) reported 1 hour ago

  Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - 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.