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 (35%)
• Cloud Services (26%)
• Web Tools (17%)
• Hosting (13%)
• E-mail (9%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Cloud Services	12 days ago
New York City	Hosting	15 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:

• 
  DR.PIXEL (@pixelpatchit) reported 1 minute 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

• 
  Ride The Leaders (@ridetheleaders) reported 3 minutes ago

  @RichardMoglen $NET has one of the strongest weekly bases in $IGV Inference has to live near the user and Cloudflare already owns a 300 city network. The weekly backs it up with a six month base, RS line at new highs ahead of price, handle forming 9% off highs. Undercut and reclaimed the 21ema today while $IGV broke. Earnings in 10 days should resolve the base...

• 
  groky (@groktuto) reported 4 minutes ago

  Wtf just happened is @Cloudflare down?

• 
  ok.dot.alt. (@okdotalt) reported 5 minutes ago

  @FuckKoroks Every time i want to download something. Hell, even receipts are ******* blocked. **** cloudflare.

• 
  りっか (@7sistere2) reported 7 minutes ago

  chatgpt 502 Bad Gateway cloudflare

• 
  Informer |-/ (@_Nformer) reported 7 minutes ago

  I love how half the comments are just people who get salty when Cloudflare goes down and the other half are mad about Cloudflare having a monoply.

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

• 
  Santosh Yadav (@SantoshYadavDev) reported 11 minutes ago

  @thdxr I never got comfortable using wrangler, I think I dont like it. otherwise cloudflare has a great DX

• 
  Panat (@ptaranat) reported 15 minutes ago

  @LevJampolsky @Teknium you're better off implementing a simple version of this. give each trust tier its own hermes profile with toolsets stripped in config (platform_toolsets, agent.disabled_toolsets). then you expose only the api_server, and let ur own app authenticate the user and broker ever call. hermes' shared API key reads every session on the instance so it never accepts a session ID from a client. you'll want to map the user to the session in a DB and translate server side. and also put a Cloudflare Tunnel + Access service token in front so the agent host doesn't open any inbound ports. something like this took me one afternoon.

• 
  LaneBrain (@LaneBrain_) reported 16 minutes ago

  ditto (to Vadim's post below) i just had a real-life conversation with an “Ai Entrepreneur & Consultant” who's charging significant money to advise businesses about Ai turns out their knowledge is so deep they've never heard of @Cloudflare before. “what's Cloudflare?” they said... 😳

• 
  Jonas Templestein (@jonas) reported 18 minutes ago

  @thdxr (Not a serious application) Alchemy is v good but unfortunately cloudflare is investing heavily in wrangler for local dev and it sucks not being able to run apps locally So we made a little script that takes env config and secrets in and produces wrangler files and wrangler commands It works quite well for us now - but it does feel like we are building half of IaC because we need to sequence resource creation and tear down and deal with flaky control plane APIs etc

• 
  Zappy (@noelzappy) reported 24 minutes ago

  app-01 and db-01 on a private local network. app-01 is the only host with a public interface, sitting behind Cloudflare. db-01 has no public route at all, it's reachable only over the LAN from app-01.

• 
  Publisher in a Box (@publisherinabox) reported 25 minutes ago

  Click-through on the number one organic result drops about 58% where an AI Overview appears. @ahrefs measured it across 300,000 keywords. That number sits inside a data-heavy breakdown of where AI search stands right now. Five points matter most for operators: 1. Citations alone are not the whole picture. Wil Reynolds tracked a 1,900% month-over-month jump in ChatGPT citations to a single page on his site. Business impact: close to zero. Counting how many times an AI engine mentions you is half a metric. It does not tell you whether you were recommended or just named, whether the description was accurate, or whether it happened on the engine your buyers actually use. 2. Google's own reporting confirms the gap. The new AI performance report in Search Console shows impressions only. No clicks, no queries, no CTR. Marketers asked for attribution data and got a vanity counter. You cannot make a business decision on impressions alone. 3. The click loss is quantified, not anecdotal. The 58% is measured click-through on position one across 300,000 keywords. Publishers who depend entirely on organic search clicks are watching a measurable decline, not an imagined one. 4. Most agentic infrastructure is not being read. Ahrefs studied 137,000 sites and found 97% of llms.txt files never get read by a crawler. Meanwhile Cloudflare reported in June 2026 that bot and agent traffic crossed 50% of all internet traffic for the first time. Technical retrievability is the whole game here. Schema, llms.txt, crawler access. It is the gap that closes fastest and the one almost nobody has verified actually works. 5. GEO demand is climbing from a standing start. "Generative engine optimization" now pulls 7,900 US searches a month, up 997%. The entire AI attribution keyword cluster is up 430% year over year. Operators are searching for this because they feel the traffic shift and want a playbook. Here is the part most people skip. GEO gets you cited inside the AI answer, SEO gets you ranked in a list of links. Four engines answer differently, ChatGPT, Claude, Perplexity and Gemini, and most publishers appear on one and are invisible on the other three. Sentiment counts as much as volume, because being named is not the same as being recommended. We built our GEO scoring before most teams knew the term, and we ran it on our own properties before we ran it for anyone else. The AI referral traffic followed. That is the only reason we are confident enough to publish the methodology. For publishers building a real business, GEO is another revenue line sitting alongside Facebook, the website with Google Discover, and the newsletter. Facebook is the base the rest of it is built on. It pays publishers directly and sends readers to the site, and that is what funds every other channel. A diversified publishing business treats each discovery surface as a channel worth measuring on its own. The operators who figure out AI referral traffic now are claiming ground the rest of the field will have to buy back later. The ground in your niche is still open. How we measure it and how you claim it, in the first reply 👇

• 
  Antraxyz (@antraxone) reported 28 minutes ago

  Stopping the bad guys with Cloudflare: 52,485 malicious requests blocked or challenged in the last month #cloudflare

• 
  현빈 | Hyunbin (@hyunbinseo97) reported 30 minutes ago

  I didn't like Squarespace Domains, but they - support TLD not supported by Cloudflare Registar - the transfer price Namecheap is calling is absurd I guess I will have to stay for these two domains.

• 
  The Godfather (@TheGodfath13541) reported 31 minutes ago

  $DOT just keeps ******* cooking bro. Usage is up + 100% of revenue of revenue going back into the towards $DOT token/buybacks (~11% total supply burned already). Bullish AF + they are targeting a 100B+ TAM (forward-looking), so ARR numbers/users (703 users today) will grow steadily imho. Dot is betting it becomes the Cloudflare/AWS layer for private AI inference.Building the same early rails that scaled other s-tier plays I hold, such as $reppo, $vvv, and $pod. These are the Gold Standard for solid tech product + tying value back into the token. Been in crypto since 2019, anon. Assymetric **** going on here if you ask me. -Godfather

• 
  SaltyAom (@saltyAom) reported 36 minutes ago

  @perpetualtalk Elysia does support Cloudflare Worker but this new version get a better support This runs on Bun 1.3.14 which is not Rust rewrite

• 
  JT (@JT_Safc) reported 40 minutes ago

  @justMERC1 @_Exohh DNS has nothing to do with it. Need to give your PS a dedicated IP address, open up the PS Server ports on that specific IP in your router settings and then also do the DNS but just because the cloudflare DNS’s are more reliable anyway. Then match network settings on PS manual

• 
  Prajwal Tomar (@PrajwalTomar_) reported 42 minutes ago

  Vibe coders are getting sued. People are shipping apps with real users and skipping the boring stuff that kills them. A 20+ year dev shared the pre-launch checklist every AI builder needs. I added what I learned after shipping 60+ apps at the agency. Don't skip this: 1. Protect yourself, not just your app. The moment you collect user data you're in legal territory (GDPR, CCPA). Have a privacy policy. Know where user data lives. 2. Row Level Security. Without RLS, anyone can open DevTools and read your entire database. Supabase → Auth → Policies. Zero policies means your app is naked. 5 min to fix. 3. Test the failure path, not just the happy path. Wrong password 5x. Reset for an email that doesn't exist. Verification link clicked twice. Signup with an existing email. Catches 80% of auth bugs. 4. Security baseline in 2 min. Prompt your AI: "Review my app as a security specialist and make sure I have strong security headers and a solid baseline security posture." 5. OWASP. Prompt: "Review my app against OWASP standards and highlight vulnerabilities." This is where SQL injection, XSS and auth bugs actually get caught. 6. Client-side validation is UX, not security. Attackers disable JS and hit your API directly. Validate again on the server. Every time. 7. AI code leaks data in 3 spots: .env values in the frontend, API responses returning too much, secrets in logs. Prompt: "Check my app for credential or sensitive data leaks in frontend or API routes." 8. API keys in the frontend means game over. If it's in the browser, assume it's already taken. Move it server-side or proxy it. 9. Rate limits before someone burns your API bill. Cap every endpoint hitting a paid API. I've watched a Supabase bill jump from $20 to $200 in a day. 10. CAPTCHA on public forms (Cloudflare Turnstile is free) plus CORS locked to your domain. 10 min, kills bot floods. 11. Error messages that don't leak. "User not found", not "SELECT * FROM users failed". Log full errors server-side, show users generic messages. Build fast. Just don't ship naked. (full breakdown in my article below)

• 
  Matt Schober (@migratewithmatt) reported 43 minutes ago

  Stopping the bad guys with Cloudflare: 2,176 malicious requests blocked or challenged in the last month #cloudflare

• 
  defido 👊⛽️ (@defido) reported 44 minutes ago

  @meaganrgamache Moved to eve and vercel. Got tired of how bad the ai product was. Not sure why cf offers its own inference if it can deliver a stable product there. In terms of deploying something. Cloudflare is uniquely on its own with the way it runs its workers/containers. Using frameworks for agents has been a pain. Eve is supported by vercel in the same way they did Nextjs and they won that vertical. Cf doesn’t do oss well. You guys build and burn oss projects fast. Eve isn’t great the vercel workflows are terribly slow and inefficient. I don’t like the egress costs and vercel is expensive. But they do one thing right. Product works. And if it doesn’t. They fix it.

• 
  Porkbun (@Porkbun) reported 44 minutes ago

  @staabse @baiaphilia Well I'm biased and I'm one of the few folks who built Porkbun but here are my reasons: 1) We let you change your name servers and don't lock you in, at Cloudflare you have to upgrade to an expensive paid plan in order to do so should you ever want / need to. 2) Domain registration is our bread and butter and not a side gig we tacked on later. 3) We're not a multi-billion dollar mega-corp, we truly care about each and every one of our great customers and our company. 4) You can register your domain at Porkbun and still use it at Cloudflare and maintain the freedom to switch DNS providers when needed, eliminating the all eggs in one basket scenario. 5) Great pricing, we sell most domains at our cost (wholesale + ICANN fee + credit card fee), that said we can't afford to eat the credit card fee like Cloudflare can. 6) We actual engage with users on X ;) 7 ) Actual human customer support should you need it. I could keep going but these are pretty good reasons :)

• 
  AM (@finesse24_7) reported 44 minutes ago

  At three months into their operation did I work for cloudflare? At the same time they will say I never worked at Apple Inc. I personally knew Mr. Jobs during his treatment for cancer, and the prior years. This business is committing consumer fraud and government fraud.

• 
  Leo (@0xGKBRK) reported 47 minutes ago

  @FuckKoroks It’s not like Cloudflare puts itself in the middle by hacking the website. The person running the website wants to use Cloudflare. If you’re gonna complain to someone, complain to the website that subjects you to that crap. Or vote with your wallet and go to a normal website.

• 
  Ryan Wycuff (@RyanWycuff) reported 52 minutes ago

  @unusual_whales CloudFlare is cheap as **** and normally riddled with bugs why it goes down and potential takes 1/3r the internet and source repos with it. Dont trust a thing they say.

• 
  Aymane - أيمن (@AymaneOnlineDev) reported 52 minutes ago

  @TeeDevh You might want to check out Cloudflare Email Service. That's what I'm using. The $5/month Workers plan includes 3,000 outbound emails/month, then it's only $0.35 per extra 1,000 emails.

• 
  haden staab (@staabse) reported 53 minutes ago

  @Porkbun @baiaphilia Firstly, I never said there was something wrong with you. You’re more than welcome to give us your pitch. Why should I use Porkbun over Cloudflare?

• 
  Santosh Yadav (@SantoshYadavDev) reported 55 minutes ago

  @apvarun @astrodotbuild @Cloudflare Definitely and I get why pages support is as removed, but I wish the migration experience was seamless too

• 
  DJ Alex Parker (@DjAlexParker) reported 57 minutes ago

  @XBOXSupport Could we get a technical breakdown of the incident? @Cloudflare do it when they have issues and provide lots of detail, would be nice for you to do it too

• 
  Paal (@paalsoberg) reported 60 minutes ago

  kalvo has no user accounts. No email, no password, no database of people. Meals live in SwiftData on the phone, synced via iCloud. The one server is a Cloudflare Worker proxying scans to Claude, so the API key never ships in the app. Less to build, less to breach.