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.

• Cloud Services (50%)
• Hosting (33%)
• E-mail (8%)
• Domains (8%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	E-mail	4 days ago
Township of Evan	Hosting	5 days ago
Ahmedabad	Cloud Services	10 days ago
Le Puy-en-Velay	Cloud Services	12 days ago
Ann Arbor	Cloud Services	13 days ago
Palermo	Hosting	13 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:

• 
  Krishna Singh (@krishnasinghdev) reported 6 minutes ago

  @tapasadhikary @Namecheap I never liked namecheap / godaddy, don't know why people choose it over simple providers like cloudflare where they charge same amount for 1 or 10 years

• 
  Wes Roth (@WesRoth) reported 9 minutes ago

  Cursor cloud agents can now run on infrastructure you manage, including machine pools that automatically scale with demand. Self-Hosted Machines let agents execute inside your network with access to internal services, source control, custom hardware like GPUs and Macs, and existing build infrastructure, while inference, planning, and the agent loop remain in Cursor’s cloud. Cursor also supports AWS Lambda, Cloudflare, Coder, Daytona, E2B, Modal, Namespace, and Vercel. Cursor says cloud agents now create more than 60% of the pull requests it merges internally.

• 
  bored knees (@boredknees) reported 12 minutes ago

  @punekarnews Fix your cloudflare settings. The site blocks normal users too.

• 
  junebnunny (@junebnunny_) reported 12 minutes ago

  @Gion_the_critic @SportingNest @Cloudflare It's just the type of thing you've just got to come across and you don't really find them that often, because when a campaign is up, it's up for a few hours and then taken down very quickly, because it's quite obviously malware.

• 
  chosem 😖 (@chosem_) reported 15 minutes ago

  @synopsi use cloudflare receive and sending. connect receive to an openrouter API, basically most modern AI will do, even cheaper ones. make it categorize: promotion, support, misc. and then route the support to your actual support platform so you can see it all in one place.

• 
  My1 (@nep.one - Misskey) (@My1xT) reported 15 minutes ago

  @slendidev interesting question would be how fast or slow cloudflare runs on those, as especially on my older laptop it sometimes took a decent while, before needing a click and taking a decent while again, while anubis you dont need to babysit.

• 
  Adam Rackis (@AdamRackis) reported 16 minutes ago

  @kettanaito @flydotio Do your pods auto-sleep when they’re not getting traffic? I think there’s a min setting you have to set to zero to let everything shut down and then just cold start on the next request. Really though surely Cloudflare free tier is simpler?

• 
  Serriff (@serriff) reported 22 minutes ago

  @xbtactics damn i thought we were all buying cloudflare, no?

• 
  MoMoMacro (@MoMoMacro) reported 24 minutes ago

  $NET is in the buy zone. Price: $273.85 Aggressive pullback zone: $274.04 Why we own it: Cloudflare owns the edge that traffic physically transits - a real enforcement point, plus the pay-per-crawl and bot-control layer that decides which AI agents may touch a site at all. Risk: THE MOST EXPENSIVE NAME IN THE ROTATION: 43.3x EV/Sales and ~184x forward earnings on a business with a NEGATIVE GAAP operating margin, ~$109B cap, sitting near its 52-week high. Every take must state the multiple explicitly - the thesis is quality and positioning, never value, and a de-rate does not need bad news to happen. This is the level the work pointed at. Nothing about the thesis changed on the way down.

• 
  volkanolmez (@volkanolmez) reported 26 minutes ago

  @xDestin0 That's almost always a local proxy or antivirus doing SSL inspection — the cert itself is valid (Google Trust Services via Cloudflare). Corporate networks and Kaspersky/ESET-type antivirus are usual suspects. Any chance you're on a work network? 🙏

• 
  Eli Yumn (@EliYumnik) reported 28 minutes ago

  @acolombiadev @Cloudflare GitHub for CI/CD and hosting the damn internet’s repos Supabase Resend Replit Gemini Eleven labs

• 
  Go₿rrr.me (@GoBrrr_me) reported 35 minutes ago

  @janrothen @paoloardoino @The_Pi_Hole And/or set your DNS Servers to: Primary: 1.1.1.2 Secondary: 1.0.0.2 Cloudflare blocks a lot of bad stuff like phishing, scams, and malicious domains right at the network level.

• 
  CerooDan (@danieldmai) reported 35 minutes ago

  Whats going on ? Gmail not working properly rn, websites not loading properly. Don't see errors on cloudflare or AWS.

• 
  PureStory (@PureStoryLabs) reported 37 minutes ago

  @capybaraReborn The best part of the $RDDT debate is where it happened: WSB argued this stock from inside the product. The bull thread that stuck was the S&P 500 add, 2,900 points. The bear thread that stuck was Cloudflare data saying 57% of Reddit's traffic is bots. The stock is down 15% since the July scare over the Google deal, so the crowd living inside the asset still hasn't settled what it's worth.

• 
  Deyder Cintron (@deydercintron) reported 38 minutes ago

  @levelsio @Cloudflare Full API surface that lets you register and manage without handoffs is the real unlock. Anything that forces a browser click or support ticket re-introduces the bottleneck.

• 
  JK (@_junaidkhalid1) reported 40 minutes ago

  @dillon_mulroy @EffectTS_ the cloudflare support point is the one that actually moved me. a lot of these framework bets fall apart the moment you try to deploy somewhere real. effect holding up there changes the calculus.

• 
  Kristian Freeman (@kristianfreeman) reported 41 minutes ago

  Day one support for Cloudflare!

• 
  Patrick Ryall (@PadraigOraghail) reported 43 minutes ago

  The learning is never ending. Mostly it is platforms, in this case using Cloudflare as the auth gate. I had never used cloudflare for more than DNS. Now I have three sites running on it, for free, which is mad. Workers, Zero Trust, DNS, connected to ***. It's all rather slick.

• 
  jc (@jc1337asd) reported 44 minutes ago

  My project on @Cloudflare keeps going down because of free tier limits. I want to upgrade to a paid plan but there seems to be no way to limit spending. A plan that costs from $5 to infinity is not really a good plan :(

• 
  Selenka (@SelenkaOnChain) reported 45 minutes ago

  Netnet Capital team is flexing metrics and talking about successful launch of Subway Runner... Meanwhile, 2 vibecoders literally drained their entire mechanic and became the #1 and #2 top holders. Here is the breakdown directly from one of the guys who farmed them: 🧵👇 "First decent cook of the bull run (if we’re even in one). Spent the last few months trying to get good at on-chain analytics, so hadn't been actively cooking. Two nights ago, I'm watching the feed and notice everyone sending $10 clips to this CA: 0x8154e35166f21305adac82f95b54de8acd44d23a. Instantly smelled pure degen activity. Hit up the group chat, did some digging - turns out it’s a Subway Surfers / Chrome dino style runner game by NetNet. Their shitcoin was sitting at a $90M cap at the time, so I figured if their token is holding that kind of valuation, there’s definitely meat on the bone. Normally, their games are pure casino trash: deposit cash, pray to RNGesus, or get rekt. But why not test it? Played a run manually and noticed that at the end of each game there was a draw. Checked their TG and reverse-engineered the contract - turns out there’s an N% chance to win an NFT from their collection. Their previous official collection had crazy volume and peaked hard, so my degen senses started tingling: this was a hidden gem. Literally 15 minutes later, they pause the game. Perfect timing - gave us room to prep. By that point, I had already captured the WSS traffic and requests. Their game logic was using a basic commit-reveal scheme: courseCommit = keccak256(serverSecret) seed = keccak256(serverSecret ++ playerSalt ++ runId) Meaning: right at game start, the server literally sent us the secret, allowing us to compute the seed and reconstruct the entire track in advance. The game loop: 3 lanes, 30 coins, 3600 ticks to finish (60 seconds). You dodge obstacles while longing/shorting NVDA. 3 hits = you lose the full $10. Complete a flawless run = you collect all coins to refund your stake and it only burns ~$0.20 in fees, giving you an almost free roll at the NFT lottery. In the era of AI and vibecoding, this was child's play. My boy XXX and I started spinning up bots in parallel. Ended up deploying his script since he coded it faster. We simulated runs, got a 100% win rate, set up a websocket listener for when the contract unpauses, and went to bed. Woke up at 6 AM, and literally 30 seconds later the game goes live. We spun up the bots - 5 minutes in, we already bagged our first NFT. Then came the scaling phase. At first, the team didn't give a single **** - no Cloudflare, no rate limiting, not even a basic 429. We ran 10 wallets simultaneously. After a few hours, they finally threw in a primitive 429, and that was it. No bot protection, no captcha, nothing. They didn’t even enforce single-session checks per wallet, so we were running multiple concurrent instances on the exact same address (literally impossible to do manually). The bots printed flawlessly. At one point, our load was crashing live games for actual manual players, forcing the team to repeatedly pause the game to fix lag. Every time they brought it back up, we resumed blasting. Total mint size was 1,060 NFTs. We scooped over 20% of the entire supply. Then came the funny part: the collection had zero secondary volume. Time for a little social engineering. We hopped into their TG playing dumb, gently nudging the admins: 'Hey guys, might want to tweet that the game is live and apply for OpenSea verification!' The final tally: * Total capital spent on fees/burns: ~$1,700 * Total NFTs pulled: ~50–60 pieces (friends got a similar bag) * PnL: Dumped most of the floor tier into bids today at $200–$300 a pop, still holding some. Nothing crazy for a real bull run, but an easy 5-figure profit for a couple of hours of vibecoding."

• 
  Daniel Zahoor (@DanielZahoor) reported 46 minutes ago

  Set your router DNS to 1.1.1.2 and 1.0.0.2 to block malicious sites across your Wi-Fi. These free Cloudflare addresses silently block scams and phishing on every device. You get network-wide protection with zero software to install or manage.

• 
  Ric Orna (@ric_orna) reported 48 minutes ago

  @yongfook Or you gotta be doing something that actually has a moat still. Eg a network of sensors and API. Nobody is gonna vibe code physical stuff. Or something so big and boring a lift that nobody would want to and couldn’t in short order anyway. Vibe code your Cloudflare competitor.

• 
  Eli (イーライさん) (@niceEli1) reported 48 minutes ago

  @tekbog I literally migrated an entire service from one codebase made in C# to Rust with a few seconds of downtime (only was caused by cloudflare tunnels changing the domain from one internal service to another one). It isn’t hard to just make software work without a maintenance period.

• 
  Utsav Patel 🇮🇳 (@mr_utsav_patel) reported 48 minutes ago

  @Cloudflare @CloudflareHelp @Yank if you could help here...

• 
  🔥🏴‍☠️CyberTechWolf🏴‍☠️🔥 (@CyberTechWolff) reported 54 minutes ago

  @ChaoticTKnight I'm gonna laugh if Cloudflare gets DDOSed or some **** because they wanna claim the Internet. Not everyone has to be hijacked by Cloudflare and I hope someone hacks their ******* **** I don't use these words a lot but the Internet might just have robophobia.

• 
  Sahil Mondal (@SahilMondal_) reported 54 minutes ago

  The fastest way to crash PostgreSQL is opening direct connections inside Serverless Lambdas. 1,000 concurrent requests = 1,000 DB connections = OOM crash in 2 seconds. Fix: Put PgBouncer or Cloudflare Hyperdrive in front. Keep 20 persistent connections open and reuse them.

• 
  Nuvorlane (@nuvorlane) reported 54 minutes ago

  Default `/crawl` is `contentUse: "full"`. A site that sets `use=reference` now 400s you at job start. Aug 31, Cloudflare Browser Rendering. The endpoint honors the Content Signals `use` level in robots.txt. Allowed `contentUse` values: `reference` or `full`. `immediate` is not accepted because `/crawl` stores pages. Mismatch = 400 `Crawl disallowed by Content-Signal directive (purpose or use level)`. Site `use=immediate` blocks every crawl. Site `use=reference` blocks the default. This is a second gate beside `crawlPurposes` (`search` / `ai-input` / `ai-train`). Defaults are all three, so `ai-train=no` 400s you too unless you narrow the array. If the job is RAG/index, declare `reference` and drop `ai-train`. Don't debug a 400 as an outage until you've read the site's `Content-Signal`.

• 
  Lex (@TheLexTimes) reported 55 minutes ago

  Hey @Cloudflare I reached out via DM about WARP constantly disconnecting. Is there a direct contact I can talk to? Happy to provide any data to help figure this issue out.

• 
  Goldman Stacks (@GoldmanStacks) reported 57 minutes ago

  @tresokure Your website is down with a DNS resolution error from Cloudflare.

• 
  LUIS- LUIS- (@LUISLUIS532957) reported 1 hour ago

  @itz_pippo still not working, akira is blocked by cloudflare, please include always other hosts, thanks.