1. Home
  2. Companies
  3. Cloudflare
Cloudflare

Cloudflare status: hosting issues and outage reports

No problems detected

If you are having issues, please submit a report below.

Full Outage Map

Cloudflare is a company that provides DDoS mitigation, content delivery network (CDN) services, security and distributed DNS services. Cloudflare's services sit between the visitor and the Cloudflare user's hosting provider, acting as a reverse proxy for websites.

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.

At the moment, we haven't detected any problems at Cloudflare. Are you experiencing issues or an outage? Leave a message in the comments section!

Most Reported Problems

The following are the most recent problems reported by Cloudflare users through our website.

  • 55% Cloud Services (55%)
  • 27% Hosting (27%)
  • 18% Domains (18%)

Live Outage Map

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

CityProblem TypeReport Time
Le Puy-en-Velay Cloud Services 9 hours ago
Ann Arbor Cloud Services 2 days ago
Palermo Hosting 2 days ago
New York City Hosting 11 days ago
New York City Cloud Services 1 month ago
Los Angeles Cloud Services 1 month 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:

  • serriff
    Serriff (@serriff) reported

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

  • SahilMondal_
    Sahil Mondal (@SahilMondal_) reported

    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.

  • chrisjlocke
    Chris Locke (@chrisjlocke) reported

    @SportingNest @DaveLukewski @Cloudflare No it didn't. Just posting engagement bait crap.

  • junebnunny_
    junebnunny (@junebnunny_) reported

    @Gion_the_critic @SportingNest @Cloudflare It's a click fix attack

  • realjamesmtz
    James Martinez (@realjamesmtz) reported

    @mrfundman @Cloudflare Damn too rich for me.

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

    @Cloudflare Fix human verification

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

    @Cloudflare Fix human verification

  • tangvu_dev
    Tang Vu (@tangvu_dev) reported

    In the Vietnam 100-VU burst, Cloudflare averaged 191.77 ms vs Vercel’s 430.95 ms. P95 was 337.11 vs 879.96 ms, with 0% errors on both. But cross-region burst tests reversed the winner in the same regions as the warm tests.

  • arrzzt
    Arijit (@arrzzt) reported

    @Cloudflare @eastdakota I cancelled Workers Paid today, just a day after the new billing cycle started. I haven’t really used anything from this month’s paid limits, but I’ve already got a $5.90 invoice. Any chance you can cancel this renewal and void the invoice? 🥹🙏🏻

  • KamilFabian
    Kamil Fabian (@KamilFabian) reported

    @RueNahcMohr @lmilsfsd @Cloudflare just cler the cache. Problem is at your "receiver" ;)

  • aldozampatti
    Aldo (@aldozampatti) reported

    @jmsuth @ChadMoran @monarch_money BTW, If you aren't using Cloudflare for your MCPs, LMK and I can help. Not sure what's the reason behind but I'm just extending a hand :)

  • daveying99
    David Haddad (@daveying99) reported

    @levelsio @Cloudflare Easy decision. Only thing I would like more is domain favoriting (considering buying) and more tld support (namecheap has more and godaddy much more)

  • AntarYaami
    KS (@AntarYaami) reported

    Why doesn't @Cloudflare support .so domains yet?

  • ImGlorping
    Imglorping Medias (@ImGlorping) reported

    @mintyyyyy7 Digital artists can easily adapt their skills to traditional if there’s a power outage and they feel like drawing. If cloudflare suffers an outage the average ai artist can’t do anything

  • SoccerGuyUS
    SoccerGuy (@SoccerGuyUS) reported

    @levelsio @Cloudflare Namecheap is awful. Anyone looking for a better Google Domains (since they rug pulled) alternative: Porkbun.

  • gm_mertd
    Mert Deveci (@gm_mertd) reported

    STOP INSTALLING 55 SKILLS TO USE A SINGLE API. @firecrawl @Cloudflare If it is more than 3 skills agent needs to f... use you, your platform is already too complex and the agent won't be able to use it. Simply put it into the CLI where it can output instructions on doing --help or --best-practices Can't believe the amount of dark patterns emerging here. @vercel is guilty of the same thing

  • MomenBuilds
    Momen Adel (@MomenBuilds) reported

    i was literally and always pro vercel and was inspired by them and specifically @rauchg but after this tbh im gonna migrate offer to cloudflare or even host locally after this ****

  • SelenkaOnChain
    Selenka (@SelenkaOnChain) reported

    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."

  • cali_baba_
    Calibaba (@cali_baba_) reported

    Vibe coding escaped the IDE 😭 Cloudflare has thousands of non-engineers building internal apps with AI agents. Meta is turning prompts into playable social experiences. The next billion “developers” may never call themselves developers.

  • designertom
    Tommy Geoco 🇺🇸 (@designertom) reported

    context: grok bot runs in the cloud out of the box, which is great, but the whole point of registering a computer is letting agents run things on YOUR machine. i have a mac mini as the home base for my whole OpenClaw (and others) agent stack: my Obsidian knowledge vault, my capture scripts, QMD and sub-surface UIs for slices of workflows connected to crons, all of it lives there. grok's agents are supposed to reach into that box and run stuff. the bug: from the iOS app, every one of those commands dies with "couldn't bind the command for review." i checked the mini's side and grok's own exec daemon was connected the whole time but the command never even left the app. same commands run fine from desktop. so it's the mobile approval surface that's broken, not the computer link. and there's no allowlist or auto-approve at all. every command needs a review card that mobile can't show. which means all agent → your-own-computer automation is dead from my phone ended up standing up my own authed relay on the mini + a cloudflare tunnel just to route around the approval layer. it works, but come on. what i want: 1. per-computer command allowlist so trusted scripts skip review 2. fix the review card on mobile 3. when it fails, give the agent a real error instead of a silent retry loop

  • SyntaxError2505
    SyntaxError » CEO of "CEO of..."-names (@SyntaxError2505) reported

    @NewAgeRetroNerd It never failed on me Cloudflare should have a look

  • jamescoder12
    James (@jamescoder12) reported

    The uncomfortable truth. Your ISP has no incentive to optimize your router settings. They have every incentive to leave them on factory default and every incentive to upsell you when the defaults cause problems. When your Wi-Fi is slow, you call and complain. They test Speed 1 the connection to your modem. It's fine. So they tell you "everything looks good on our end" which is technically true. Then they offer you a faster plan. You pay $30/month more. Speed 1 goes up. Speed 2 the Wi-Fi to your devices doesn't change. Because the bottleneck was never the pipe coming into your home. It was the 6 feet between your router and your laptop. When your firmware is 4 years out of date, they don't push an update. When your channel is congested, they don't suggest switching. When your DNS is slow, they don't mention Cloudflare. When your channel width is halved, they don't widen it. When your security is on WPA2 with the factory admin password, they don't flag the risk. Every free fix that would make your Wi-Fi faster is a fix that prevents them from upselling you a more expensive plan. Every month you rent their router is $14 in revenue for a $60 device they deployed years ago. The rental has no end date. The equipment depreciates. The revenue doesn't. He called his ISP 4 times. They suggested upgrading twice. He upgraded twice. He paid $360 extra over a year for a faster plan that didn't make his Wi-Fi faster because the problem was never the plan. It was 9 settings his ISP could have fixed in a 5-minute phone call. They chose to sell him a faster highway instead of widening the off-ramp. "Your ISP isn't slow. Your settings are. And the company delivering your internet profits every month you don't know the difference." 9 settings. 15 minutes. $528/year back. Faster internet on a cheaper plan. The router was never broken. The defaults were designed by a company that makes money when you think it is.

  • nilan_sathz
    Sathz_நிலன் (@nilan_sathz) reported

    Stopping the bad guys with Cloudflare: 212 malicious requests blocked or challenged in the last month #cloudflare

  • fedemas
    Federico (@fedemas) reported

    @frederickjames @Superwall @RevenueCat Never used Cloudflare honestly. Started on Supabase, now I'm on Convex. Curious tho, what's your use case? You call Cloudflare straight from Swift or you still have a backend?

  • nuvorlane
    Nuvorlane (@nuvorlane) reported

    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`.

  • boredknees
    bored knees (@boredknees) reported

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

  • zoecyber001
    Zoë (@zoecyber001) reported

    RAPID FIRE CYBER NEWS - WEEKEND EDITION The weekend wasn't quiet. 1. Manchester Airports Group is facing an alleged data theft. Extortion group FulcrumSec claims it stole around 86 GB of data containing customer, booking and travel information. 2. Berlin's government is refusing to pay ransomware attackers who claim to have stolen 5.79 TB of data from its network. The city confirmed the extortion attempt but says it won't pay. 3. Several Chrome and Edge extensions were caught delivering malware that can steal crypto-related information, browser history and sensitive data. Some were also used to inject fake ClickFix prompts. 4. Infostealer malware is now stealing active Claude sessions. Anthropic warned that attackers can potentially take over Claude accounts using stolen session information without simply needing the user's password. 5. Microsoft uncovered TerminalFix, a new ClickFix campaign using fake Cloudflare CAPTCHA pages to trick people into running malicious commands that install a reverse-tunnel backdoor. Cybersecurity keeps finding new ways to abuse things we already trust.

  • jessethanley
    ˗ˏˋ Jesse Hanley ˎˊ˗ (@jessethanley) reported

    It is interesting to me that I have some DNS/network requirements and I can't use Cloudflare for what I want to do.

  • jamescoder12
    James (@jamescoder12) reported

    The full impact. What he changed and what happened: 1. Moved router from cabinet to open shelf: 74 Mbps → 155 Mbps 2. Changed Wi-Fi channel to least congested: 155 Mbps → 290 Mbps 3. Widened channel width to 80 MHz: 290 Mbps → 380 Mbps 4. Switched DNS to Cloudflare (1.1.1.1): browsing latency dropped noticeably on every device 5. Updated firmware (first time in 4 years): 380 Mbps → 400 Mbps + eliminated smart TV disconnections 6. Changed admin password + upgraded to WPA3: closed the 2 biggest security holes in the network 7. Separated 2.4 GHz and 5 GHz bands: eliminated TV buffering caused by band steering 8. Enabled QoS (work laptop prioritized): zero Zoom call drops during peak household usage 9. Bought own router, returned ISP rental: $168/year saved + full control over all settings Starting speed: 74 Mbps (on a 500 Mbps plan getting 15% of what he paid for) Ending speed: 440 Mbps (getting 88% of what he paid for) Then the real move: he downgraded from the 500 Mbps plan back to 200 Mbps because 200 Mbps with optimized settings delivered faster Wi-Fi to his devices than 500 Mbps with factory defaults. Monthly savings from the plan downgrade: $30 Monthly savings from returning the rental: $14 Total annual savings: $528 with faster, more stable, more secure internet Total time to make all 9 changes: 15 minutes of settings + one trip to Best Buy + one phone call to return the rental.

  • _junaidkhalid1
    JK (@_junaidkhalid1) reported

    @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.