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	1 day 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:

• 
  gökhan (@goekhan) reported 3 minutes ago

  fasted the whole day did some core work at home evening coffee gotta ship at least two other products today is "i just can't feel good if i want see that idea in action" for i am already paying for compute, cloudflare, hetzner, and thousand other APIs kinda funny though you can just function, worker and agent the entire internet into apps that talk to each other yet cannot watch a random world cup match from an ondemand commentator like Peter Drury or Alex Jacques and gotta help yourself with your mediocre homeboys you can have arxiv papers have their own podcast via notebookML but cannot push a likeness soccer commentator via kittenTTS or ElevenLabs API legally

• 
  DegenCalls (@Degen_calls_sol) reported 3 minutes ago

  GITHUB REPOS YOU SHOULD KNOW ABOUT Most scrapers break for boring reasons. A button moves, a class name changes, Cloudflare gets in the way, or the crawler dies halfway through a long run. Scrapling turns scraping into a more resilient system. Scrapy-style spiders, concurrent crawlers, pause and resume, anti-bot handling, and adaptive element finding in one framework. The detail most people miss: the adaptive selectors are the real unlock. Instead of hard-coding brittle CSS paths and praying the site never changes, the scraper can relocate elements after redesigns. That matters when you are scraping production targets, not toy pages. This is the shift from scripts to infrastructure. A script extracts data once. A scraping framework keeps extracting when the website changes, slows down, blocks, or moves the target. Most people still build scrapers like one-off hacks. The better setup is a crawler that expects failure and keeps going anyway.

• 
  Stake Exposed ⚖️ (@formatpal) reported 5 minutes ago

  @Stake Code Segregation and Infrastructure Concealment To protect the development team and systematically obfuscate the physical location of the backend infrastructure, a highly secure code-deployment strategy is enforced: Siloed Access (Microservices Dependency): No individual developer in Belgrade has access to the complete monolithic codebase. Tasks are strictly divided: one engineer manages the wallet integration, another maintains a specific game, and a third works on the Risk Engine. Automated CI/CD Pipelines: Code written in Belgrade is committed to enterprise GitHub/GitLab repositories and deployed automatically via secure pipelines (using Docker, Kubernetes, and Terraform). The code is deployed directly to cloud servers hosted by Amazon Web Services (AWS) located in Frankfurt (Germany) and Dublin (Ireland) to minimise latency for European and Middle Eastern players. Cloudflare Enterprise Cloaking: The backend servers are never directly exposed to the public. All incoming traffic is routed through Cloudflare's Enterprise reverse proxy, which masks the real AWS IP addresses. When users attempt to trace the platform's servers, they see IP addresses mapped to the US or Western Europe, completely masking the technical engine room operating from Belgrade.

• 
  Delali (@delali) reported 8 minutes ago

  @DanielSmidstrup Even Vercel, Cloudflare, et al have challenges. For us founders, it never ceases. But I get your point. Let's keep pushing…

• 
  Serenity (@Serenity) reported 8 minutes ago

  @D3vAaron @Cloudflare do your research, many people have had this happen to them due to competition. maybe you've never had a successful business before? stick to making a ****** VPS company

• 
  James Ross (@CherryJimbo) reported 10 minutes ago

  @LoicReco @Cloudflare imo a few things would help a lot: - transparent failover/replication - observability: where's my object, why is it unhealthy - tooling to inspect storage growth - throughput ceilings truly documented, not discovered in **** - fewer footguns (i/o gate deadlocks etc.)

• 
  Clark (@itsclarkholden) reported 10 minutes ago

  PRO TIP: Use cloudflare email routing and sending to make a custom email client for your Saas. No need to pay for support tools like Front.

• 
  Veselin Stoyanov (@st0yanov) reported 10 minutes ago

  💡 Pro tip: Don't send webhooks externally to untrusted parties from your main backend - you'll expose your server IP and get DDoS-ed. A common scenario is having your host hidden behind a reverse proxy like Cloudflare. By sending a webhook, you'll expose your IP address and it's game over. A proper architectural design is to have a separate service on a separate host responsible for delivering your webhooks.

• 
  Sachin Joshi (@Sachin_is_here) reported 10 minutes ago

  The free tier was not only marketing. Every new customer added traffic, attack data and operational experience. That helped Cloudflare improve threat detection, justify more data centres and spread infrastructure costs across a larger network.

• 
  Anakin (@anakinHQ) reported 13 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!

• 
  Sorower H. (@sorower01) reported 14 minutes ago

  @Cloudflare dashboard down?

• 
  Andrii (@Andrii38324276) reported 14 minutes ago

  @eastdakota @Cloudflare Great PR move to look breezy about it publicly, but genuinely curious: does Cloudflare actually see a measurable customer bump every time a competitor loses an engineer to a rival, or is this more vibes than data at this point?

• 
  Crypto Jargon (@Crypto_Jargon) reported 17 minutes ago

  💥BREAKING: Every major card network just signed onto a payment protocol built for software to pay software, no human involved. The Linux Foundation confirmed the x402 Foundation is now formally governed by 40 members, and Coinbase's original contribution of the protocol is complete. The list of backers is the real headline: Visa, Mastercard, Amex, Stripe, Ripple, Google, Amazon Web Services, Cloudflare, Circle, and both the Solana and Stellar foundations, among others. Here's the part almost nobody knows. HTTP, the protocol every website runs on, has had a status code sitting unused for thirty years. Code 402, labeled "Payment Required." The web's original architects expected someone would eventually build payments directly into it. Nobody did, because card fees made charging fractions of a cent pointless, so the internet monetized through ads and subscriptions instead. x402 finally uses that code. A server asks for payment, a client sends a stablecoin transfer, usually USDC, and gets the data back in seconds. No account, no card, no prior relationship needed. That's exactly why AI companies care. An autonomous agent can't open a bank account or pass a credit check, but it can sign a transaction. Google already built x402 into its own agent payment system. Cloudflare ships it by default in its agent toolkit. The actual usage is still small, about $24 million moved last month across 75 million payments, averaging 32 cents each. That's nothing next to what Visa or Mastercard move in a single day. But the average payment size is the tell. No card network on earth can process a 32 cent charge profitably. This protocol was built for a kind of commerce that doesn't fit inside the rails these same companies already own, which is exactly why they just joined it instead of competing with it.

• 
  ℭ𝔬𝔳𝔢 (@ekojoecovenant) reported 23 minutes ago

  Spent the day migrating my PR review agent off waitUntil() and onto Cloudflare Queues. Turns out waitUntil() has a silent 30-second ceiling. Learned that the hard way when longer PR reviews just... stopped mid-analysis. Queues fix it properly instead of me hacking around a timeout.

• 
  Mick.net - Maker: Document.Bot 🤖 BestTime.app 🎉 (@mick__net) reported 29 minutes ago

  @sumukx I like 5.6 but same here in terms of OCD chasing targets. I asked to use a cloudflare tunnel. After 1h still OCD retrying i asked why it took so long and what it is blocking it. Then it replied i need you to run ‘cloudflare login’ in the terminal for auth. I think 5.5 would have asked directly instead of trying really hard with 100’s of unsuccessful work arounds.

• 
  Avdhoottt (@avdhootttt) reported 32 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.

• 
  Piyush (@PyDataWizard) reported 33 minutes ago

  Total monthly cost to run a startup: ~$20 - Claude ($20/mo) = coding - AWS Free Tier = hosting & DB - Vercel = frontend (free) - Stripe = payments (2.9%/txn) - GitHub, Clerk, Cloudflare, Sentry = all free Never been a better time to ship. What’s stopping you? 🚀

• 
  Maverick (@Mavericks100xs) reported 36 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.

• 
  Sachin Joshi (@Sachin_is_here) reported 39 minutes ago

  Cloudflare Workers was an especially important shift. Cloudflare stopped being only a service placed in front of applications. Developers could now run application logic directly across its edge network. The CDN became a computing platform.

• 
  Anti Lying (@aimtomisb3hav3) reported 40 minutes ago

  @Support X just put me through a Cloudflare anti-bot verification. I'm a verified account. I PAY YOU monthly. Please stop being lousy.

• 
  Sherif Peterson (@sherifpeterson) reported 41 minutes ago

  Bots just passed humans on the web. Cloudflare puts it at 57.5% of all traffic, a year before they expected it. Run that forward 5 years: browsing mostly disappears. Sites will turn into machine-readable endpoints with a thin human front. Agents do the visiting. Everything gets abundant except attention. Scarcity moves to the human side. Verified-human platforms. Content with a person visibly behind it. Same thing that happened to handmade goods after factories the cheap version wins volume, the human version wins price. At that point a company's personality isn't branding. It's the moat. Creating has never been this cheap. Getting noticed has never been this expensive. Most people will scroll past this stat. That's kind of the point

• 
  Domi (@domirosari0) reported 43 minutes ago

  @eastdakota @Cloudflare Just hire me Problem solved 🥸

• 
  Karan (@kwakhare5) reported 44 minutes ago

  rate limits on LLM APIs are brutal spent the last hour mapping groq 429 errors in a cloudflare worker just to return a pretty json toast instead of crashing the content scriptsmall details but necessary fr

• 
  sunil pai (@threepointone) reported 45 minutes ago

  lol I hear people on bsky are trying to cancel cloudflare for sponsoring localfirstconf?

• 
  kyle (@whatdafuqkyle) reported 46 minutes ago

  🚨BREAKING: @x I can sniff a @Cloudflare bed **** from a mile away. platform is currently dumping on iOS.

• 
  Sophia dev 🤓 (@Sophia_Crypto) reported 48 minutes ago

  @Lovable We have a bug. We use Cloudflare turnstile for our app sign in but on your windows desktop app it won’t pass / validate despite all your URLs whitelisted in cloudflare.

• 
  Cyber_Racheal (@CyberRacheal) reported 49 minutes ago

  This is infact entirely true. A Department of Justice court filing confirmed that employees from the Department of Government Efficiency (DOGE) moved a massive dataset to an unauthorized location. Under the direction of agency tech leadership, a live copy of the Numerical Identification System (NUMIDENT) database was uploaded to a custom cloud server. This database contains the sensitive personal information, birth details, and Social Security numbers of more than 300 million Americans. The agency’s internal security teams explicitly flagged the action as "high-risk" with a potential for "catastrophic impact". The situation grew worse when officials admitted that data was improperly shared through an unapproved, third-party server network hosted by Cloudflare. A federal whistleblower, agency Chief Data Officer Charles Borges, revealed that the data transfer bypasses independent security monitoring and auditing protocols. Government lawyers acknowledged that the Social Security Administration cannot fully account for the data. They currently lack the access needed to verify who viewed the files, what exact information was shared, or if the records still exist on the outside server.

• 
  W. Rix Victory II (@Wrix2) reported 52 minutes ago

  @nikitabier My visibility is near zero and I joined around 16 years ago. Spent 6+ months with cloudflare screwing me up horribly. Stripe rejected my CashApp, but it handshakes with it elsewhere. On top of recovering from being run over by a truck, these issues have been very painful.

• 
  Chubby♨️ (@kimmonismus) reported 55 minutes ago

  Every Sunday we publish an exclusive interview in the Superintelligence newsletter. The last few: - Ahmed Awadallah, Partner Research Manager at Microsoft Research AI Frontiers, on small on-device agents that go toe to toe with the giants. - Phil Gurbacki, VP of Product for Weights & Biases at CoreWeave, on a research agent that reads your experiments and launches the next training run itself. Akshay Kothari, Co-Founder and COO of Notion, on a million custom agents. - Coming up: Cloudflare, Google Cloud, and several more I can't announce yet. - The part I still find hard to believe is that I get to sit down with the people actually building this. Every week, someone new. Subscribe for free down below:

• 
  Matt Gibbs (@ematt) reported 58 minutes ago

  Meta gets to scrape our work for free to train its AI. We get the compute bill, engineering cleanup and downtime. Its crawler knocked one of my sites offline in the process. In a 45-minute window, meta-externalagent made ~1,210 requests. 849, roughly 70%, ended as 499s: the crawler opened them, then abandoned them. The burst hit hundreds of long-tail dynamic URLs. At the same time, usage jumped to ~2 CPU cores, memory climbed from under 1 GB to 5.4 GB, V8 exhausted its heap, and four Cloudflare health checks failed. This wasn’t a giant volumetric DDoS, and Cloudflare didn’t fail. Another app on the same server handled 126,000+ edge requests during the same window. The problem was concurrency. Abandoned requests left expensive Redis, Supabase and React rendering work running at the origin. A CDN can cache completed responses. It cannot cancel application work already underway. Our origin should have had stronger backpressure and disconnect cancellation. That’s being fixed. But a weakness in our stack doesn’t make Meta’s crawler behaviour reasonable. Meta gets the AI training material for free. Publishers absorb the compute costs, engineering time and downtime. How is that remotely fair?