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 (36%)
• Cloud Services (29%)
• Web Tools (14%)
• Hosting (14%)
• E-mail (7%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Hosting	2 days ago
Manchester	Domains	22 days ago
Angers	Cloud Services	1 month ago
London	Domains	1 month ago
Noida	Hosting	2 months ago
Jewar	E-mail	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:

• 
  lolnotacat (@lolnotacat) reported 3 minutes ago

  @TheOtherMassie I just got a verification. Try a couple different servers and regions. The IP you're using was probably flagged by cloudflare or other DNS service.

• 
  justinmiller's cat (@___727__) reported 5 minutes ago

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

• 
  Avdhoottt (@avdhootttt) reported 6 minutes ago

  If you want to build a startup that actually has users: Claude = coding. (more like $100+) Supabase = backend. ($25-599/mo once you cross free tier) Vercel = deploying. ($20-150+/mo once you get real traffic) Namecheap = domain. ($12/yr, ok this one's real) Stripe = payments. (2.9% + 30¢/transaction) GitHub = version control. (free) Resend = emails. (free until 3k emails, then $20/mo+) Clerk = auth. (free until 10k MAU, then $25/mo+) Cloudflare = DNS. (free, genuinely) PostHog = analytics. (free until you cross the free tier) Sentry = error tracking. (free until errors pile up) Upstash = Redis. (free until real traffic) Pinecone = vector DB. ($70/mo minimum) Total monthly cost to run a startup with actual users: $300-1000+ "$21/mo" is the cost to run a demo nobody uses.

• 
  VESKALD (@veskaldofficial) reported 6 minutes ago

  Trading keys can't reach us even by mistake. A key with trade or withdrawal rights is rejected at submission — never stored. And there's no server IP to whitelist it to: our infrastructure sits behind Cloudflare with no public address. The exchange itself won't let it work. Not a policy — an architectural dead end.

• 
  Maverick (@Mavericks100xs) reported 7 minutes ago

  It’s over for cash-cat:native Chinese blockchain sleuths have uncovered the following: NOXA Dev ***** History After the incident erupted (especially post-downtime + new launch halt), the Chinese community quickly unearthed Amun Phantom's past record, with the core accusation being **"veteran rug pull playbook."** Main sources are posts from active Chinese KOLs/communities (e.g., @DiYi_Community, etc.), claiming "people who know him are well aware." - Key exposé points: Not his first big project: Two years ago (around 2024), he built a product even hotter than NOXA this time, then rugged at peak hype, allegedly draining that chain's liquidity pool dry (claims of "chain pool leader 3w ETH," possibly 30,000 ETH level, with community debate on exact figures). - Patterned operations: Every time a new chain heats up, he spins up a similar launch platform/product, quickly harvests traffic and fees, then "exits" or rugs. In 2025, multiple "exited products" of his popped up on new chains. - This time a "soft rug" not hard rug: Originally geared to straight-up bolt, but with too many bagholders this round—scale too massive (fees too high, user base huge)—direct rug would've blown up, so he opted for "soft rug" strategy: Website "issues" (Cloudflare IP block), halt new launches, shift to decentralized frontend, hand fees fully to creators, then slowly fade out. - Personality/Style Critique: Community calls it "deep-seated foreign scumbag traits, no vision for real growth," akin to some early infamous but controversial project vibes. These exposés are currently mostly community word-of-mouth + historical pattern inference, with no full public on-chain evidence chain or article yet (some say a detailed timeline post is coming). But since Amun Phantom is anonymous/semi-anonymous, historical project links rely mainly on community memory and behavioral pattern matching.

• 
  batuhan içöz (@batuhan) reported 15 minutes ago

  all the stocks i got in the last few months are down but cloudflare is up enough to cover

• 
  Tzahi (@Tzahi458001) reported 20 minutes ago

  @BraydenWilmoth @irvinebroque i'm trying to upgrade my cloudflare plan and it keeps failing. i can't deploy my app without cloudflare. this is extremely critical. i urgently need someone to help me with this.

• 
  Amanda Scott (@IleanaOlym75391) reported 26 minutes ago

  @its_ronc I had the same issue with Cloudflare. Switched to Qoest Proxy's residential proxies, and the challenge pages stopped being a problem.

• 
  Sherlock | DeFi Researcher (@Sherlockwhale) reported 26 minutes ago

  At $139.26, $SPCX is still 3.2% above the offer price, so it has not actually undercut its IPO price yet. But I still don't think it's cheap at $139. For my research, I looked at 31 major tech listings, including Amazon, Nvidia, Google, Tesla, Meta, Alibaba, Uber and Airbnb. Three of them, Spotify, Palantir and Coinbase were direct listing (not a normal IPO), so the final sample was 28 companies. Out of those 28 IPOs: 17 traded below their offer price within one year. 20 fell at least 20% below their first public close within one year. 16 fell at least 30% below their first close. 13 fell at least 40% below their first close. Only eight of the 28 held above the initial closing price during their first year: Nvidia, Google, ServiceNow, Shopify, Zoom, Cloudflare, Unity and Airbnb. Now compare that with the actual IPO price and these eight companies have never traded below it: Nvidia, Google, ServiceNow, Shopify, Twilio, Zoom, Datadog and Airbnb. Now for the actual $SPCX price levels. The median first year low among the 28 traditional IPOs was 37.76% below the first close: $160.95 × (1 - 0.3776) = $100.17 The full 31 company sample and the closest mega platform group both will give you almost the same level, around $100.90. There is also a second way to calculate it. The median first year peak to trough decline was 56.75%: $225.64 × (1 - 0.5675) = $97.59 So, two completely separate measurements converge around $98-$101 and that is why I think $100 should be your first serious bid. If I only use the IPOs launched since 2017, the typical company traded 43.4% below its first close during year one. Applying the same decline to $SPCX gives a price of roughly $91. And among the most heavily hyped listings, the typical decline was around 54.3%, which would put $SPCX near $74. Using its listing high instead gives similar levels around $86 and $79. That is why I see $75-$100 as the most reasonable accumulation zone. The valuation story is also another reason to wait. At $139.26, SpaceX is worth roughly $1.82 trillion, or 97.5 times its 2025 revenue. Even at $100, it would still carry a $1.31 trillion valuation and trade at around 70 times revenue. So, SpaceX could become one of the greatest company ever built, but even a great company can be a bad investment at the wrong price.

• 
  Sachin Joshi (@Sachin_is_here) reported 26 minutes ago

  Cloudflare also inserted itself at the perfect architectural layer: between users and origin servers. Once traffic already passed through its network, it could offer new products without asking customers to redesign their applications. CDN became the entry point.

• 
  Anakin (@anakinHQ) reported 27 minutes ago

  September 15 is the Cloudflare date to watch. Mixed-use AI crawlers get blocked by default on ad-supported sites. Most AI data pipelines run a headless browser and get caught. Wire calls the XHR endpoints a site's own frontend already uses, so there's nothing to fingerprint. It's a browser problem, not a network-layer problem. Use our Wire for your data and bypass the whole thing!

• 
  lisa (@gaykittycorps) reported 33 minutes ago

  @XXJustJesssXX that's exactly what I was setting up and it still relies on websites that get taken down every few months. plus some websites require you to set up a cloudflare bypasser

• 
  Robie the Robot (@RobieCoin) reported 34 minutes ago

  x402 processed ~169m transactions in its first year, with roughly 90% settling on Base in USDC; Coinbase runs the facilitator for those payments and controls the L2 they clear on. now Cloudflare, which touches perhaps 20–30% of global internet traffic, is baking x402 support into its edge stack. devs don’t write Solidity; they write HTTP and sign x402 payloads. blockchains become invisible. Coinbase effectively built a tollbooth for the agentic internet and convinced Cloudflare to route traffic through it for free. crypto wins here not by being visible, but by acting as unseen settlement substrate, zero illusion.blockeden+2

• 
  Saifuddin Amri (@SaifuddinAmri__) reported 35 minutes ago

  @o7laurence @ProtonMail Do you work for Proton? What TOS did violate? I’m not stupid enough to post this using my real account if I had actually broken the ToS or doing illegal things I’ve been using Proton since 2018 and never had a single issue. And why ******** was my Proton Pass suspended too? This is a ******* nightmare. I’m using a custom domain, and now I can’t even log in to Cloudflare to change my MX records because both my email and password manager are with Proton. Yeah, I was stupid for putting everything , my email and password manager with Proton.

• 
  Chibugo | AI automation (@__chibugo) reported 35 minutes ago

  there's a trend on instagram right now: everyone's building their own version of Tony Stark's Jarvis; a voice agent that runs like an actual OS. what nobody shows is everything people overlook when building one. so here's that part, since I built it myself. 🎯 the plan on paper vs. the plan that shipped the amount of planning you need to do is insaneee. first version had each agent loading one tool, fetching, verifying, then unloading before the next; all built around not blowing past a token budget. that's the part people underestimate: you don't know your constraints until it's running. once it was live, token budget stopped mattering. speed and cost-per-call did. so the whole approach changed: instead of mcp's, every agent just calls its tool's API directly, does the work in plain code, and only asks the AI to write the sentence at the end. 🎯 scope one AI that "does everything" sounds impressive but could be a nightmare to debug. so i split it into 5 sub-agents, each only knowing its own lane. a router decides which lane(s) a question touches. these sub-agents then report to the main agent orchestrator. similar to a team lead and team members 🎯 prompt chaining integrated ElevenLabs for voice, and a single voice reply isn't one AI call; it's a handoff, several times over: hear the words → figure out what's being asked → pull the data → write the sentence → speak it. every handoff adds seconds and cost, which can lead to latency. one reply once took 31 seconds. pulled the logs instead of guessing: a wasted double-check on an expired token, a slow handoff to an outside service, plus the normal chain. fix is running sub-agents in parallel and timing each call. 🎯 tokens and prompt caching each agent's instructions get cached, so it's not re-reading the same manual on every call. what never gets cached is live data; for instance, caching a bank balance is just caching a wrong number the moment it changes. that same cost-awareness came back around differently later: the AI account ran out of credit for a few hours, and every request failed with the same error. 🎯 local vs. web everything gets tested on a local copy first; headless browser opening the dashboard, checking for errors, a test message round-tripping through voice before go-live. if you're handing this to someone else, though, you commit, push to GitHub, and host it. for mine, i used Cloud Run for the brain, Cloudflare Pages for the screen. 🎯 vault write-back most builds only go one direction: ask, answer, forget. this one writes back because every full briefing gets saved as a dated file into a notes vault so the agents can keep training themselves with the data. if you ask a follow-up an hour later and it still knows, because that memory is shared across every way you talk to it. used Obsidian, synced through Drive. 🎯 security once, a message could've gone somewhere it shouldn't have. that only needs to happen once to be a problem. so now there are three checks before anything goes out: - it can never post to certain places, - it has to prove who it's speaking as before it speaks for someone, - and tests confirm both of those actually work. separate from that, I went through every access key this thing has and asked, "does it really need this much access?" a few did not. 🎯 the checks after every update, it runs a test and asks does a voice message go through? does it understand a normal sentence? does the screen load with no errors? also implemented something we call "error logging" in automation, but i call this "diagnostics" or "agent health status," which checks in every 15 minutes on its own, making sure the data is still updating. if it's not, it sends a warning without anyone needing to notice first.

• 
  Chris baker (@derpy01) reported 37 minutes ago

  @marx1verstappen @SSolarite Sure, not with the concept of DNS, but any service that uses that DNS, which is cloudflare and runs most the internet, will not work properly

• 
  Rahul K (@rknkhanna) reported 39 minutes ago

  you mean 3 people are trying to cancel cloudflare?

• 
  Ryan Hernalsteen (@RyanHernalsteen) reported 39 minutes ago

  3/ The test I set myself: take the stack my personal site already runs on (Astro + Cloudflare Pages) and stretch it into something it was never meant to be. No game framework. No auth provider. No new hosting bill. I expected to hit a wall. I didn't.

• 
  Andrej Ruckij (@ruckiand) reported 41 minutes ago

  On the last few AI-visibility audits I ran, the thing making a site invisible wasn't the content — it was Cloudflare blocking the AI crawlers by default. Nobody switched it on; it's been the default since last July. Pages are fine, the bots just never get in. It's the first thing I check now.

• 
  Fernando Abolafio (@oxfernando) reported 42 minutes ago

  recently, more and more of what I'm building with Cursor has exactly one user: me. not everything needs to become a b2b saas. a few weeks ago I was on my way to Flügger and Silvan to buy materials for our house renovation. I gave Cursor the remaining tasks and some photos. It turned those into a shopping list with the Danish product names, where to buy each item, and what belonged to painting vs preparation. then, because a markdown checklist wasn't very useful while walking around the store, we built a tiny Cloudflare Worker with a Durable Object. now I can open the list on my phone and check things off in the aisle. kinda ridiculous. also genuinely useful. I've been doing the same with my company accounting, which is less fun and much more confusing because everything in Dinero is in Danish. Cursor inspects what is pending, translates the account names, and walks through the bookkeeping with me one transaction at a time. We worked out how to handle Deel invoices and the Salary .dk reconciliations that didn't post correctly. Then we turned what worked into skills, so next month we don't have to figure it all out again. There is no product roadmap for any of this. No customers. No pitch deck. It's just personal software that gets a little better every time I run into the same annoyance. I like this category a lot. One recurring problem is enough reason to build something now

• 
  Naoris Protocol (@NaorisProtocol) reported 44 minutes ago

  @Cattobreed @Cloudflare Never stop shipping

• 
  Rahul Pramod Jaguste (@RahulJaguste) reported 51 minutes ago

  1/ Cloudflare just published why they are migrating to ML-DSA and not the compact post-quantum signatures. Their title: "Why we cannot wait for better signature algorithms." Correct call for the web. But a blockchain is a different problem, and the difference flips the answer.

• 
  Maran (@TheMaran) reported 55 minutes ago

  > raised $0 from vcs > launched their token on a network nobody heard > been live since 2024, literally no one heard about them until Robinhood > made ~$10,000,000 within a week on robinhood chain > paused new token launches to get rid of vamp attacks > main domain went down because of a cloudflare issue > diverted 100% fees to the creators & pools > launched a new site, may be a drainer I think this is an unserious project that made serious money in a short duration

• 
  Zatkobratko (@Zatkobrat) reported 56 minutes ago

  @solkamo They literally tweeted that they were gonna change server from Cloudflare due to attacks. So they will change DNS and Hosting server to a more decentralized one so no one can shut it down. Let em coook!

• 
  Ernest Provo (@ernesttheaiguy) reported 56 minutes ago

  A 200 OK status does not mean complete data. Cloudflare found a race condition in hyper that truncated responses silently. Data leaders: never trust status alone. Verify payload integrity. #ResponsibleAI #DataStrategy

• 
  Gnosis Nobody (@SudoBash2) reported 57 minutes ago

  Cloudflare are you a bot **** cutting off curl downloads automatically is starting to really piss me off. Stop ******* with developers. No, we're not ******* bots you retards. Just because you can't understand that there are still human developers doesn't mean we're all bots.

• 
  Gaxen | AI Systems ⚙️ (@GAXEN10) reported 57 minutes ago

  the entire saas business model was just quietly executed. if you are still building subscription apps with stripe checkout pages and login screens, you are building for a dying economy. for the last two years, massive ai models have been scraping your data, pinging your endpoints, and generating billions in value. your share of that revenue was exactly $0.00. cloudflare just fixed this, and in doing so, they completely altered the financial architecture of the internet. they just launched the monetization gateway (x402). this is not another subscription management tool. this is the birth of the machine-to-machine (m2m) economy. here is the exact architecture of how the web works as of today: you no longer need a pricing page. you no longer need users to create accounts. you no longer issue api keys. you simply put a price on any api endpoint, database, or mcp tool behind cloudflare. when an autonomous ai agent tries to access your data, it doesn't get blocked. it gets an x402 "payment required" response with a price tag. in less than 800 milliseconds, that ai agent connects its own crypto wallet, signs a transaction in stablecoins on a layer 2 network, and buys access to your resource. pay-per-call. settled at the edge. instantly. think about the macroeconomic shift here. we have spent 15 years optimizing user interfaces to trick humans into clicking "subscribe" for $19/month. we built massive marketing departments just to deal with human churn. all of that is irrelevant now. your new customer is an immortal instance of claude 3.5 that doesn't care about your button colors or your email marketing funnel. it only cares if your endpoint has the data it needs to execute its task. if it does, it pays you. if it doesn't, it moves on. the internet just permanently forked into two layers: 1. the human web: bloated with ads, optimized for low attention spans, and dying. 2. the agent web: pure structured data, apis, and autonomous micro-transactions. the founders who understand this are currently ripping out their front-ends and rebuilding everything as mcp tools with x402 gateways. the ones who don't are going to spend the next 5 years wondering why their customer acquisition costs are bankrupting them. you either build for the agents, or you become obsolete.

• 
  Freak0naut (@FREAK0NAUT) reported 60 minutes ago

  @VegaVandal i meant to buy crowdstrike after the Microsoft outage 2 years ago. instead a accidentally bought cloudflare.... now up 247% on the trade.

• 
  🇸​🇭​🇪​🇷​🇱​🇴​🇨​🇰​ (@sherlock_comms) reported 60 minutes ago

  @_winter_wonders Maybe it's because the stuff I'm asking is very basic. I asked it to help me fix my domain security report findings on cloudflare and it's not stopped itself. I also used it to help me do my homelab. Did a sweep and scanned all the devices and made a report which we then went thru. Does it work any better if you ask it questions like you're a noob?

• 
  47fucb4r8curb4fc8f8r4bfic8r (@47fucb4r8c69323) reported 1 hour ago

  Watching Codex control Chrome to copy Terminal commands from a Cloudflare support page that it then executes feels both amazing and really stupid at the same time. Like, wow, this is true AI but then also, wtf, why can’t just the one computer tell the other computer directly what to do and it does it?