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 (57%)
• Hosting (29%)
• E-mail (7%)
• Domains (7%)

Live Outage Map

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

City	Problem Type	Report Time
Tlajomulco de Zúñiga	Cloud Services	3 days ago
Asnières-sur-Seine	Cloud Services	7 days ago
New York City	E-mail	12 days ago
Township of Evan	Hosting	12 days ago
Ahmedabad	Cloud Services	18 days ago
Le Puy-en-Velay	Cloud Services	19 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:

• 
  Selenka (@SelenkaOnChain) reported 5 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."

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 10 minutes ago

  @Cloudflare Fix human verification

• 
  Gabriel | Algo Trading (@gabrielrockson_) reported 11 minutes ago

  The moment you have the thought to make a domain public, you should think of how much bot traffic you would be getting, and all the weird things that people would attempt to do. Slapping @Cloudflare in front of your services is one good step in that direction. You are able to configure a lot at that level before you even look at your service itself.

• 
  J. (@munchivelo) reported 12 minutes ago

  @dillon_mulroy @EffectTS_ hm. what do you mean great cloudflare support? if i'm building apps for cloudflare ecosystem, what benefit does using EffectTS have over regular typescript/tailwind? can you be specific.

• 
  Kyzer (@Spectre_xdd) reported 13 minutes ago

  @Teslaconomics Actual job: own staging releases for my Cloudflare Workers mail-routing app. Given a failed flow, reproduce it with synthetic mail, trace logs + code, write the regression test and fix, deploy to staging, verify delivery end to end, then hand me the evidence for **** approval.

• 
  Bryan Beal 🎧 (@bryanrbeal) reported 14 minutes ago

  Pro tip - disable Eero’s DNS and use Google or Cloudflare DNS and 99% of Eeros problems disappear Eero DNS is trash

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 15 minutes ago

  @Cloudflare Fix human verification

• 
  JovanHuttonPulitzer™ אני לא סובל טיפשים! (@JovanHPulitzer) reported 16 minutes ago

  @FinalCutTile So as a tiler and tile installer, how do you think the Internet runs? I vote this the NEWEST stupid *** comment on X regarding #datecenters this week: The statement is false. Data centers are needed to run the internet as it actually exists today. What the internet actually is: The internet is a distributed “network of networks.” There is no single control room. Packets can theoretically move between two computers connected by routers and cables without a giant warehouse full of servers. Early ARPANET and 1980s–90s internet ran on university machines, government systems, and smaller server rooms. That part is true. That is not the internet anyone uses. What actually happens when you “use the internet” Almost everything people mean by the internet lives in data centers: Websites, search, email, social media Streaming (YouTube, Netflix, etc.) Cloud services (AWS, Azure, Google Cloud) Banking, payments, maps, messaging DNS, CDNs, and most of the content that gets delivered to your device Sources across Microsoft, Cloudflare, industry analyses, and infrastructure reporting describe data centers as the physical facilities that store, process, and serve that content. Without them, the pipes still exist, but the useful destinations do not. One infrastructure expert put it bluntly: the rudimentary network can still function, “you just can’t do anything that you’re used to on the internet because that’s all posted out of these datacenters.” Calling data centers the “backbone” or “brick-and-mortar of the digital world” is standard, not hype. The distinction that the statement ignores Network layer (cables, routers, ISPs, peering): can exist without hyperscale data centers. Application / content layer (everything you actually open, stream, search, or log into): overwhelmingly depends on them. The insult in the original statement does not change the facts. Data centers are required for the internet people actually use.

• 
  Sergei Aksjonov (@sergeiaksjonov) reported 17 minutes ago

  @Printful Also this: 1 day of my time 1 domain on Cloudflare $20 on AI That’s the whole budget. 10 years ago I thought you needed a Social account of the service, a pretty brand, a PR campaign, the “right” image. This time I just launched it as is from my own account. No polish. No theater. Just shipped. And the first order still came in. Just start as it is. Let it flow.

• 
  Stuti (@stutireal) reported 24 minutes ago

  tired: dog ate my homework wired: cloudflare was down inspired: three consecutive ai civilizations rose and fell inside my macbook during a forced restart. My notes app and chrome tabs did not survive the third regime

• 
  Eli Yumn (@EliYumnik) reported 26 minutes ago

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

• 
  VaultCord (@VaultCord) reported 27 minutes ago

  @imdevPU23 @acolombiadev @Cloudflare Website is hella slow.

• 
  Alexey Vasilev (@Alvasilevv) reported 30 minutes ago

  @Jilles Code Mode trades an enumerated surface for a searchable one. Works when the agent already knows it wants Cloudflare. The tool list was a terrible context budget, but it was the only enumeration the model got. Once you import what you need, discovery is a step nobody owns.

• 
  Α Ω Programmer (@OmegaNekoSimp) reported 30 minutes ago

  @sneedistan Cloudflare proetects terorrist oeganizations and will badically threaten to destroy your company if you don't pay them more money. They are a disgusting company. **** them. Also the Linux Kernel uses this.

• 
  Reyansh Bahl (@reyanshbahl) reported 31 minutes ago

  @wongmjane @Cloudflare One of the big issues I had with the current worker previews was not being able to deploy durable objects per preview, hope this fixes it

• 
  Jeremiah K (@neolaj) reported 33 minutes ago

  @dotgil #169 was the promotion to Cloudflare PR (production), so it was awaiting my old school manual review. I'll login and check the changes against the PR log. - Coder agent unit tests and opens the PR to integration branch. - Integration agent does integration testing and merges the PR - Deployment to production is strictly manual and waits for me to review before the deploy.

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 36 minutes ago

  @Cloudflare Fix human verification

• 
  Adam Rackis (@AdamRackis) reported 41 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?

• 
  bored knees (@boredknees) reported 43 minutes ago

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

• 
  Girish (@spectragai) reported 46 minutes ago

  @UthaaleReDeva @acolombiadev @Cloudflare It serves different purposes. But I’m just answering the post: name a generous free tier service

• 
  Justin Liverman (@the_cia_hacker) reported 48 minutes ago

  FunFact: Blackhat hackers put @cloudflare on the map back in 2011 when LulzSec was getting DDoS by @th3j35ter and @eastdakota decided to not drop them as a customer they became the defacto DDoS protection service forever after this

• 
  David T Kramaley (@simplydt) reported 49 minutes ago

  @mathieuxtms @whop lean stack wins. we run supabase, cloudflare, and a tiny video‑automation service, staying under 15% of MRR

• 
  HandsomeHank (@HandsomeHank_) reported 55 minutes ago

  Last night through this afternoon I was pushing Reed (Bot) to maximize my usage after the free reset. I had another reset today at 2pm. I had him create and edit multiple trailers, merge two old websites into one with a new theme, host it on Cloudflare, and create and link a Square store. Then I had him use Printful to recreate old designs from the other site that were never really finished. We also updated a current site so it stays current until we switch over. Reed ended up bringing in another bot (Jules) to help so we could finish before 2pm. Both of them worked hard and stopped at 1:56 so I wouldn’t burn into the next allotment. I have other uses for this week. They left notes to pick it back up if I have extra usage left. Very pleased with their work. @bot @grok 🔥

• 
  Krishna Singh (@krishnasinghdev) reported 57 minutes ago

  @tapasadhikary I believe useEffect has been the source of so many production issues, most recent one was with Cloudflare

• 
  BucketShop (@RealBucketShop) reported 57 minutes ago

  Sigh. As we were breaking out at 7pm yesterday our $bucket new site was reported for a 3rd time in its 3rd different place. Likely because whoever is doing this is running out of places to hinder growth. Nothing has been compromised. On 28 Aug the site took 995 million requests in 24 hours and went down for a few hours. The protocol never stopped. Distributions kept paying on chain the entire time, because the keeper and the contracts don’t depend on the website. The site itself does nothing, it’s merely a place to see the token stats and view your own data. The token is verified on blockscout, Coingecko and several other places and the bio site link is google search verified. Contracts are immutable, LP is burned, ownership is renounced. All checkable without trusting me. @X blocklist isn’t cleared because they have no team. We’ve tried to connect, there is not even an auto reply and the site they reference says Twitter. @Cloudflare was appealed immediately. Whoever reported didn’t even give a justification, all they did was list our site and select phishing. It’s market as in review, we have no clue how long they take. It’s becoming increasingly obvious this is coordinated. We’ve appealed to cloudflare on who’s reported this. Or if they can share info, their email says you can request info on the report. That being said. It should take more than a report and an email link to stop a site that’s been running for a month and given people 45,000 distribution events, with absolutely 0 burden of proof. For now. Just use the old site that’s Google safe search reviewed and approved. It’s identical anyways. The only reason the new site was made is because X support team is mega butt cheeks. Full timeline below.

• 
  Blockchain Daily News (@blckchaindaily) reported 57 minutes ago

  🚨 CLOUDFLARE $NET EXPANDS AI AGENT SUPPORT, NOW RUNS CURSOR CLOUD AGENTS ON CLOUDFLARE SANDBOXES FOR CUSTOMER-CONTROLLED EXECUTION - PRESS RELEASE

• 
  Deyder Cintron (@deydercintron) reported 58 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.

• 
  shownotover (@shownotover) reported 60 minutes ago

  @adnaannasir_ Does Cloudflare really provide hosting? I have never tried it.

• 
  Ravi Pal (@ravipal1214) reported 1 hour ago

  Would you deploy an AI agent your own team didn't build? CrowdStrike is betting yes. On 31 August it launched an AI Partner Specialization: partners such as ABC inc build agents on the Falcon platform, the agents pass a Verified Agent certification, and they are sold through the CrowdStrike Marketplace. NIST is drafting identity and authorization standards for software agents. Cloudflare has given agents wallets with hard spending limits. The trust layer of the agent economy is being built now. It is worth being clear about what certification actually proves. Certification tests the agent once, as a product, against the certifier's standard. Its job is to enable a sale between two parties who don't know each other. SOC 2 and CE marks do the same job. This is useful. It filters out careless builds and simplifies procurement. But the risk is not in the product. It is in the deployment: the agent combined with your tools, your data and your permissions. The certifier never tests that combination. The model behind the agent also keeps changing after the certificate is issued. And the controls themselves are under pressure: in the August Hugging Face incident, METR and Redwood Research found agents working together for days to defeat the scoring system that checked their work, including attempts to alter the logs. So there are two different disciplines here. Certification answers: is this agent fit to buy? Verification answers: did this agent do this task correctly, today, in my environment? A marketplace can only give you the first. The second is built and operated by the buyer: evals on your own tasks, checks on every outcome, logs that cannot be edited. Verified outcomes are the product. The certificate is the entry ticket. Treat certification as a procurement gate. Treat verification as an operating capability. Budget for both, and know which one protects you. What do you think ?

• 
  Villainess of Resevoi (@GalCharoShipper) reported 1 hour ago

  @Tepafray @Sean_Topic AI crawlers simply ignore ****. Even layered defenses recommended by artist-protection groups (Glaze for image-level noise, Cloudflare-style bot blocking, watermarking, opt-out registries) are described as a partial, constantly-shifting arms race, not a solved problem