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 (31%)
• Hosting (19%)
• Web Tools (11%)
• E-mail (6%)

Live Outage Map

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

City	Problem Type	Report Time
Angers	Cloud Services	9 days ago
London	Domains	11 days ago
Noida	Hosting	24 days ago
Jewar	E-mail	24 days ago
Braga	Web Tools	24 days ago
Noida	Cloud Services	25 days 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:

• 
  tidux (@skibidiblazor) reported 48 seconds ago

  @prestonjbyrne Not to mention because the major cloud providers have their own international cables between datacenters they'd have to put that DPI filter in front of Cloudflare, Cloudfront, Azure and Google CDNs, YouTube, etc.... it would make the Internet unusably slow.

• 
  Command Code (@CommandCodeAI) reported 1 minute ago

  We're aware of an ongoing incident. Partial outages at Cloudflare and Supabase are causing Command Code CLI to experience intermittent connection issues. We're actively investigating and working on a fix. Thanks for bearing with us.

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 3 minutes ago

  HERMES AGENT JUST TURNED WHATSAPP INTO A REAL AI WORKER But one tiny setup mistake can leave the entire bot completely silent. What Just Dropped: → Official WhatsApp Business Cloud integration → Run Hermes as a private assistant, team bot, or customer support agent → Text one WhatsApp number and get AI replies directly inside the chat Built Like A Proper App: ✓ Secure webhooks and official Meta support ✓ Voice notes, media, read receipts, and typing indicators ✓ Interactive approval buttons when Hermes needs confirmation The Setup: → Run `hermes whatsapp cloud` → Connect your Meta Business account and WhatsApp number → Use Cloudflare Tunnel to expose your local Hermes gateway securely Three Mistakes To Avoid: ✓ Use the 15–17 digit Phone Number ID, not your real phone number ✓ Replace the 24-hour test token with a permanent system-user token ✓ Subscribe to the `messages` webhook field or the bot will never receive anything For a reliable WhatsApp agent, use the official Cloud API path instead of the unofficial personal-account bridge.

• 
  Glitch Truth (@glitchtruth) reported 7 minutes ago

  Day 28 of 30. 30 Days of Practical Tech. A reverse proxy is a server that sits in front of your real server. Cloudflare runs one for free in front of millions of sites. Visitors hit Cloudflare's IP never yours so attackers can't find your machine. Tomorrow Day 29: what a CDN actually is.

• 
  Malte Landwehr (@MalteLandwehr) reported 7 minutes ago

  @EddCoates So many solutions: · Cloudflare/CDN · Caching · Free API without authentication I once worked for a website with 90% bot traffic. This issue is manageable.

• 
  Elyas (@ElyasAlemi) reported 8 minutes ago

  @steipete We hit this in our n8n workflows. PDF intake is slow (Cloudflare queue, async), Supabase lookups are fast. Treating them as different shapes from the start saved a lot of rework. are you running the slow side on a queue or polling?

• 
  Derek Martin 🇨🇦 (@lo_fye) reported 10 minutes ago

  @yashmp2004 Your cache busting and/or expiration is broken. Cloudflare is down. Your hosting’s network connection is shoddy, or oversaturated. A backup or clone process is hammering the disk. There’s a race condition that wasn’t triggered until now. When in doubt, check replication status.

• 
  PunkXBT (@PunkXBT_) reported 10 minutes ago

  @dr00shie that’s not even bad luck at that point, that’s just infra choosing violence specifically on your deploy window lol. cloudflare said “not today” twice in a row. @dr00shie follow back? let’s grow the circle

• 
  Pieces by Julian Undav (@piecebyjulian) reported 10 minutes ago

  I also understand that some of the words on pallets changed. PLEASE NOTE THAT the words were minted onchain, so your words are safe! We shifted the hosting site to Cloudflare after so many api calls (why the site was down for a couple of days) Please bear with us. working hard right now

• 
  JD'oh (@JDoh2983) reported 11 minutes ago

  Why Crest Fundgrove and this setup are fake Classic 'fake' pattern: "AI trading bot" with impossible claims (e.g., 85%+ accuracy, easy passive profits, minimal effort). Real markets don't work this way consistently. Minimum deposit around $250 (common in these scams). They often show fake profits in your "account" to encourage more deposits, then make withdrawals difficult or impossible (claiming fees, taxes, or needing more money to "unlock"). No real regulation: Reviews couldn't verify proper licensing with Canadian regulators (IIROC/CSA). Legitimate platforms targeting Canadians are transparent about this. Fake testimonials and reviews: Their own site has glowing "verified" reviews with inconsistent numbers. YouTube "reviews" are mostly affiliate promo videos (they earn commissions on deposits/signups). Related 'fake' service reports: Similar names (e.g., Crest Maverick Broker) have Reddit complaints about fake profits followed by withdrawal blocks or demands for more money. The weird domain + tracking params: Legitimate financial companies do not use domains like "hetouchesitdies dot com" or heavy affiliate cloaking like this. This is infrastructure for running mass scam ads. The Cloudflare content you may have seen on the page is likely because these 'fake' operations often use Cloudflare for hosting/CDN/protection (or content cloaking). It doesn't make it legitimate.

• 
  Pablodecortes (@pablodecortes) reported 12 minutes ago

  @cramforce Does it support Cloudflare Workers or only Vercel?

• 
  𝗶𝗮𝗺𝟰𝘅 (🌷,🦈) (@iam4x) reported 13 minutes ago

  @DegenCT @TheCryptoNexus - Proxy the ui api of hyperliquid through cloudflare to fetch sub-accounts - Then implementing the spot trading with support of sub-accounts

• 
  DownWithBigBrother (@DWBB1984) reported 15 minutes ago

  @ultrasxiv Fair on bandwidth being a real cost, but the 2GB figure is a long way out. Cheapest DO droplet includes 500GB+ outbound, Hetzner 20TB+. At 600-700GB household use you’re a pound or two over on DO, zero on Hetzner. Stays around the base £4-5 for most, not £300. And “un-bannable” was the precise word, not hyperbole. A commercial VPN is bannable because it’s a named brand with known IPs, a company that can be pressured or blocked. That’s the weakness. Self-hosting removes the target entirely. There’s no technical category called “a VPS used as a VPN.” It’s a rented server running standard encryption (WireGuard, IPsec), the same protocols carrying every bank settlement, ATM link and corporate tunnel on earth. To ban it you’d have to block those protocols (killing Visa, every corporate VPN, all remote work) or blacklist the datacentre IP ranges (AWS, Hetzner, OVH) that host the actual internet: payment gateways, banking backends, Stripe, Cloudflare, gov services. You can’t separate “server someone might tunnel through” from “server running the shop you’re buying from.” The second and third-order effects would cripple e-commerce, open banking and logistics, all riding the same cloud backbone. That’s the sovereignty point. You can ban a brand. You can’t ban the capability of renting a server and encrypting your own traffic, not without taking modern commerce down with it.

• 
  Japan Anime News (JAN) (@JapanAnimeNews_) reported 24 minutes ago

  A change to our Cloudflare settings appears to have caused access issues for some users. We apologize for the inconvenience this may be causing. Please bear with us for a few days while we work to resolve the issue. 🙏

• 
  Chirag (@chirag) reported 28 minutes ago

  There's a case to run a meta network on Cloudflare rails. These childish things by the regime can be bypassed at scale.

• 
  Calvin (@Calvin24seven) reported 28 minutes ago

  @EddCoates Honeypots, cloudflare, fingerprinting, not giving so much value away for free would help. Site is great btw

• 
  Lachlan (@lynx769) reported 36 minutes ago

  @EddCoates Are you using Cloudflare in front of it? It should help.

• 
  Alon M. (@Alon_iploop) reported 42 minutes ago

  @BenjaminFlatz Stealth helps, but most Cloudflare failures are environment issues: IP reputation, geo, sticky sessions, and consistent browser state. IPLoop provides the residential network layer so Playwright/Scrapy stacks don’t fail just because the traffic looks wrong.

• 
  Adnan (@atresnjo1) reported 44 minutes ago

  if @Cloudflare services had a strict spending limit i'd use them for everything tbh, just too afraid to vibecode some side **** and wake up to a $5k bill

• 
  Aidan Quinn (@BwcDeals) reported 46 minutes ago

  @EcomCJ Man email me. This damn site dms I almost never get! I’m sorry. I’m close to passing Akamai. I can do it now with proxies but it’s expensive and I know I can do it without them. I’m doing it with Cloudflare and PerimeterX already.

• 
  Francisco T. Barbosa (@Cisco_research) reported 47 minutes ago

  @YashasGunderia I believe this is more a Cloudflare thing. Lots of issues with log in/log out

• 
  Matt Carey (@mattzcarey) reported 49 minutes ago

  Day 0 support for MCP servers on Cloudflare, with Workers OAuth Provider. Thanks to our customers for working with us to ship this for the wider ecosystem :) Sounds small but this is massive for MCP auth in large companies.

• 
  zeb (@zebassembly) reported 51 minutes ago

  @astuyve @boristane Not to get too into the weeds but the concern is where the trace context gets inherited and where we check the users tracing configuration. Before a request ever goes to the Workers runtime there's our FL2 (essentially the Cloudflare webserver) that actually accepts the http connection for various reasons we want that part that isn't entirely related to Workers to be aware of tracing so we can do cool things in the future. This entails creating a way for FL2 to fetch the user's tracing config (sampling, if they want to enable propogation, etc), passing that context through FL2, passing it to the Workers runtime, and then when the Worker does a fetch we need to pass it back through to FL2 so we can potentially attach the context header. None of this is strictly about just parsing that trace context header, more about threading configuration and ceoss-service communication.

• 
  Nikhil Agarwal (@nikhildp) reported 53 minutes ago

  @dinasaur_404 @Cloudflare Yes looking for billing cap. How do you test dynamic workers as well as dynamic workflows in local dev? We had a disastrous outcome of losing $800 because the deployed code ran into infinite loop using dynamic workflow. Support team was not at all helpful.

• 
  max guy 😐 (@GolerGkA) reported 54 minutes ago

  @artillain @ThePrimeagen Ok I’m stupid bear with me. Usually with cloudflare on front of static public site, users don’t hit my web service most of time anyway, they hit cloudflare cache. Does it still work? I assume that information that anybody would want to scrape would be on static public endpoints.

• 
  Nikhil Agarwal (@nikhildp) reported 55 minutes ago

  Everyone please don't fall for false advertising of @Cloudflare @CloudflareDev. They have several billing issues that you can find easily on reddit and their customer support is bad. I moved from GCP to Cloudflare and that was a terrible mistake. Got to move back now!

• 
  starmex (@starmexxx) reported 55 minutes ago

  WHY WASTE 16 MINUTES OF YOUR TIME ON THIS AI ENGINEER EUROPE TALK WHEN I CUT THE 5 BEST MOMENTS INTO 4 MINUTES FOR YOU bright data engineer exposed why your ai agent lies about searching the web. cloudflare blocks 20% of web from ai. 60% of chatgpt citations are broken. agents hallucinate instead of saying "i can't" 00:00 - llms are programmed to please. they make things up instead of saying "i can't" 00:42 - cloudflare blocks 20% of web. 60% of chatgpt citations are broken 02:03 - gpt-5 fails all 5 web tasks without proper tools. zero out of five 02:42 - cloudflare labyrinth feeds ai fake data. bigger hallucinations 03:13 - don't parse with llm. build a parser. saves 99% of tokens bookmark this and watch the supercut below

• 
  Kamil Fabian (@KamilFabian) reported 55 minutes ago

  @EddCoates cloudflare free tier. Solved my 1mil req per minute problem. Just make sure to set up properly.

• 
  CAPED CRUSADER🦇 (@stilleclectic) reported 58 minutes ago

  @matthansbello Sigh, everything was originally done on namecheap but I’ve now just moved the dns to cloudflare. Waiting to see if that fixes the issue

• 
  ƒrαeყ (@fraey0) reported 1 hour ago

  it costs about $21/month to run what could become a multi-million dollar startup • human brain = reasoning (free) • claude = coding ($20/mo) • supabase = backend (free) • vercel = deployment (free) • namecheap = domain ($12/yr) • stripe = payments (2.9%/trx) • github = versioning (free) • resend = email (free) • clerk = auth (free) • cloudflare = DNS (free) • posthog = analytics (free) • sentry = error tracking (free) • upstash = redis (free) • pinecone = vector DB (free) everything sums up to roughly $20 to $25 per month so, the tools are not the barrier anymore. most ideas don’t fail because they’re expensive to build. they fail because they never get built at all. what’s stopping you?