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	11 days ago
Angers	Cloud Services	22 days ago
London	Domains	24 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:

• 
  DO-SAY-GO (@realdosaygo) reported 1 minute ago

  you can't. you'll spend a month chasing down all the things. then get insta banned by CloudFlare or Datadome. I'm deep in this tech and it still took me 300 hours. Even if you're a 10x engineer vs me, you're still droppin 30 hours on this. At 200-500 an hour that's 6-15K. Or you could just pay me the equivalent of 30 minutes, and you can have it right now. Up to you, bad ;)

• 
  Michael Ten 🌨🎶🫐🍀 (@iMichaelTen) reported 4 minutes ago

  @Cloudflare How could a service be built like this with Monero or Bitcoin Cash, those cryptocurrencies? @grok

• 
  Harish Bhatt (@heyharishbhatt) reported 4 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.

• 
  Ashish Rawat (@eashish93) reported 6 minutes ago

  @AniC_dev I like this, I'm building something on cloudflare stack, might wanna use this soon, but things are strictly tied to sandbox + workers etc. If you can natively support cloudflare agents sdk would be helpful.

• 
  tamimbuilds (@tamimbuilds) reported 7 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.

• 
  Nitewalkar (@Nitewalkar) reported 8 minutes ago

  Day 4 of building with Grok Build and using Openclaw to manage what I build. We have made; - Fully Functioning POS App - tailacale - pull from open inv - create new sale - return/refund - Android ready. - Fully Functioning Ops App - work orders - forms - compliance docs - service agreements - calendar - team message board (avail on web) - cloudflare w/ms auth - upload purchases Clawbot Learning - email booking -> work order and draft invoices - email purchase receipt -> update PO, draft purchase/bill - email scan and monitoring - calendar management Websites - hosted docker on backend - rebuilt exclusovely with build - need fine tuning and revision then go live!!!!!!! Next - shared inbox/alias config for custom ms auth logins on one license ms365... ● Saving $700/year in GoDaddy. ● 1.19%/transaction on POS. ● 1-2h/day in admin time saved with OPS ● Clawbot monitors/manages space on always on pc. ● Build script monitors drive and pc it lives on with cron script. Reads logs and fixes issues. SEND MOAR CREDS BROS!!! THIS IS AMAZING!!!!!!! Entrepreneurs ********* @grok @xai @openclaw

• 
  Turnpike (@turnpike402) reported 10 minutes ago

  The announcement from Cloudflare today is a huge step forward for the x402 ecosystem. Part of the problem at this early stage is convincing AI companies that they'll need to pay for what they scrape - CF is a loud voice telling them otherwise.

• 
  ProxyStats (@ProxyStats) reported 11 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.

• 
  hreiðmarr 🇺🇸 (@hreidhmarr) reported 11 minutes ago

  @Cloudflare not a criticism of you at all (congratulations to the team btw), but support for state-regulated surveillance stablecoins was not really the intended objective in using FOSS to build trustless peer-to-peer networks for transactions over the web

• 
  Glitchy Hopkins (@GlitchyHopkins) reported 12 minutes ago

  Fellowship Hall’s vendor data never needed a SaaS detour. I built their intake automation with n8n, NocoDB, Cloudflare Tunnel, Nginx, and PHP on hardware inside the building. Less manual work. More control. Want that? DM me. #n8n #Automation #DataPrivacy

• 
  Oliver (@olvrgln) reported 18 minutes ago

  @auxten @arundsharma We have a similar issue with workers. For now thinking of rewriting some core rust services into ts just for cloudflare. Very curious if you solve this and how

• 
  Exci (@ai_exci) reported 20 minutes ago

  @ZubairIbnZamir @Cloudflare @CloudflareDev Down again today. 7 hours now.

• 
  Rhys (@RhysSullivan) reported 24 minutes ago

  @cschmatzler ah i need to make this flow better, this is for registering your own oauth client but it's showing your mcp connections since the oauth target (cloudflare) is the same, will fix

• 
  PANKRATION (@WEB3Seer) reported 25 minutes ago

  22/ Cloudflare Waitlist launched for Monetization Gateway. New product for charging for resources with settlements in stablecoins via x402 protocol. #Cloudflare 23/ AscendEX Has not posted on X for 9 days. Withdrawals not processed → deposits accepted. Reports of withdrawal issues without response. Delays/non-processing of user withdrawals while continuing to accept deposits. #AscendEX

• 
  MechaboyDos☄️🐙🌿👁🐾🎼🍵💭 (@MechaboyDos) reported 28 minutes ago

  @hytebrand Site has to be bugged or something, or just overloaded on traffic... Either I get Cloudflare errors, or I can pre-order but it says sold out when I try to add to cart, or I get a success messaged that I added to cart but then my cart stays empty. Please fix this.

• 
  Danielle Morrill (@DanielleMorrill) reported 32 minutes ago

  wtf happened at Cloudflare? shipped like a ******* monster for the last 6 months, dominating my feed with new stuff daily. Now my feed is full of departures?

• 
  Kun Chen (@kunchenguid) reported 33 minutes ago

  i hope 2026 is the last year where we still have to manually click through any website to set things up in the last month, google cloud and app app review are the two repeated offenders that still need manual click-throughs - bad by contrast, github, cloudflare, hetner etc are pretty much entirely configurable by agents - good (why not computer use / browser automation? because i don't want to expose secrets in plain text and let the agent type them via keystrokes and capture them into screenshots)

• 
  Boring Engineer (@boringeng) reported 37 minutes ago

  Last night I did something I haven’t done in years: I opened my raw server logs. Not analytics. Not a dashboard. The actual access logs on the box. I was curious about one thing — with everyone saying “people don’t google anymore, they ask ChatGPT” — is any of that actually visible on my site? What I found kind of shook me. GPTBot — OpenAI’s crawler — hit my documentation 400+ times in the last 30 days. Not my homepage. My docs. The quickstart, the API reference, the self-hosting guide. It’s reading the exact pages a developer would read before adopting a tool. PerplexityBot crawls me almost every night around 2am. Quietly building its index of what my product is and does. And then the one that actually got me: a user-agent called ChatGPT-User. It’s not a scheduled crawler. It fires when a real human, mid-conversation, asks ChatGPT something that requires fetching a live page. It hit my pricing page 9 times yesterday. Nine times yesterday, a real person was asking an AI about my product. I will never know who they were, what they asked, or what the AI told them. Here’s the part that bothers me most: NONE of this appears in analytics. Not in GA4, not in Plausible, not anywhere. These bots don’t execute JavaScript, so tracking scripts never fire. As far as every analytics tool I pay for is concerned, this traffic does not exist. The only place it’s recorded is a log file nobody opens. So I kept digging, and it got worse: — Some of my “GPTBot” hits came from IPs that aren’t OpenAI’s. Random scrapers wearing GPTBot’s name as a disguise. I would never have known. — AI crawlers were hitting doc URLs I moved a year ago. 404s. Which means when an AI tries to learn what my product does, some of what it finds is a dead page. That’s not a broken link anymore — that’s a wrong answer being served to my next customer. — And apparently Cloudflare now blocks some AI crawlers by default on new sites. Meaning there are founders out there right now whose docs are invisible to ChatGPT, who opted into that without knowing, and whose analytics will never tell them. Step back and the picture is strange: an entire layer of the funnel — machines reading your site, deciding whether you get recommended, sometimes fetching pages because a human is asking about you at that exact moment — and it is completely invisible to every tool we use. We measure humans obsessively. We measure the thing that increasingly sends the humans not at all. Search had 20 years of tooling built around it. Search Console, rank trackers, an entire industry. This new layer has… grep. I’m not sure what the answer is yet. Maybe it’s a weekend script. Maybe it’s something bigger. But before I build anything, I want to know if this is just me: Have you ever looked at what AI bots do on your site? Do you know if you’re being crawled, cited, blocked? If this is a problem you have — or one you didn’t know you had until this post — reply or DM me. Genuinely trying to figure out what’s worth building here.

• 
  One&OnlyAarav (@WaterAarav) reported 38 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.

• 
  auxten (@auxten) reported 38 minutes ago

  @olvrgln @arundsharma Cloudflare Workers is the next problem we're going to try and solve.

• 
  Arshad Kazmi (@arshadkazmi42) reported 41 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.

• 
  Brute Force Artist (@bruteforceart21) reported 41 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.

• 
  Kun Chen (@kunchenguid) reported 44 minutes ago

  i hope 2026 is the last year where we still have to manually click through any website to set things up in the last month, google cloud and app app review are the two repeated offenders that still need my manual click-throughs - bad by contrast, github, cloudflare, hetner etc are pretty much entirely configurable by agents - good (why not computer use / browser automation? because i don't want to expose secrets in plain text and let the agent type them via keystrokes and capture them into screenshots)

• 
  plebo6 (@plebo86) reported 50 minutes ago

  Per AI: An online cookieless future ahead where internet companies can no longer depend on third-party cookies to follow you across multiple websites for advertising and profiling. Instead, the emphasis shifts toward privacy, user consent, and data that people knowingly share. Even though Google’s plans for Chrome have evolved over time, the industry has largely been moving toward privacy-first approaches because of browser restrictions, regulations, and changing consumer expectations. Here’s what that means in practice: For everyday internet users More privacy: Companies have a harder time tracking your browsing across unrelated websites. Less “creepy” advertising: You may no longer see an ad for a product immediately after viewing it on another site. More consent choices: Websites increasingly ask what types of tracking you’re willing to allow. Slightly less personalized ads: Advertising is more likely to be based on the page you’re viewing or information you’ve voluntarily provided, rather than your browsing history across the web. For businesses Companies are adapting by relying more on: First-party data (information customers provide directly, such as account registrations, purchases, or newsletter signups). Contextual advertising, which places ads based on the content of the webpage rather than the person’s browsing history. Privacy-enhancing technologies, such as aggregated measurement and secure data collaboration, to understand campaign performance without exposing individual identities. Industries likely to benefit Several sectors stand to gain as organizations invest in privacy-first technologies: Cybersecurity and privacy software Identity and authentication services Consent management platforms Cloud data infrastructure Customer relationship management (CRM) software AI-driven marketing analytics Examples of well-known public companies involved in these areas include: Salesforce Adobe Cloudflare Microsoft Oracle Investment implications If privacy-first trends continue over the next several years, companies that help businesses: manage customer data, obtain and document consent, analyze marketing without invasive tracking, and secure digital identities could continue to see growing demand. At the same time, advertising businesses that relied heavily on third-party tracking have had to redesign their technology and measurement approaches. Looking ahead The “cookieless future” is not simply about eliminating cookies. Instead, it’s a shift toward an internet where: users have more control over their data, companies rely more on direct customer relationships, advertising becomes more privacy-conscious, and artificial intelligence plays a larger role in understanding trends from aggregated rather than individually tracked data.

• 
  Fahad Hussain (@FahadHussa3165) reported 50 minutes ago

  Claude = coding. ($20/mo) GitHub = version control. (Free) Supabase = backend. (Free) Clerk = auth. (Free) Resend = emails. (Free) Vercel = deploying. (Free) Cloudflare = DNS. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Stripe = payments. (2.9%/transaction) Namecheap = domain. ($12/yr) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build

• 
  world (@world_xyz) reported 52 minutes ago

  cloudflare issue is resolved @worldnetwork no more crying in the casino i will accept your surrender in world war 3

• 
  Yash D (@AI_by_yash) reported 53 minutes ago

  Claude/codex = coding. ($20/mo) GitHub = version control. (Free) Supabase = backend. (Free) Clerk = auth. (Free) Resend = emails. (Free) Vercel = deploying. (Free) Cloudflare = DNS. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Stripe = payments. (2.9%/transaction) Namecheap = domain. ($12/yr) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build

• 
  a^M33 (@Dialupinternt) reported 58 minutes ago

  Ummmm I'm getting CloudFlare DNS issues on EBGames in Canada. Anyone else?

• 
  Tanmai Gopal (@tanmaigo) reported 58 minutes ago

  Met someone at the AI Engg conf today from a FAANG who said that when they tried examining Claude Tag it was a total non starter. This is how you think about adding say a cloudflare integration to a Claude Tag type agent that uses specific credentials per agent. - Users: we want to use Claude tag to get data from CF for quick debugging for some of our tenants. - CF admin: ok, here’s an API token with some privileges for you - users: can you give it to our Anthropic admin - Anth admin: have you decided what slack channel they’ll be in? - CF admin: WTF do you mean slack channel? Who cares. - Users: it’s ok, we’re on this slack. Claude Tag is scoped per channel. - Anth admin: ok. these are the all the slack users in the channel. Is this token fine? - CF admin: ******** would I know….These people look like they’re from customer support. I don’t think they can query the CF data? - Anth admin: yeah maybe we need another slack channel. Slack admin, can you help out? - Slack admin: ok here’s a new slack channel - Anth admin: woot all done - Users: ********. All our context and trouble shooting starts with a customer service escalation. That’s why we even wanted this. Sigh.

• 
  0xLoopTheory (@0xLoopTheory) reported 60 minutes 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.