1. Home
  2. ❯
  3. Companies
  4. ❯
  5. 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.

  • 57% Cloud Services (57%)
  • 29% Hosting (29%)
  • 7% E-mail (7%)
  • 7% Domains (7%)

Live Outage Map

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

CityProblem TypeReport Time
Tlajomulco de ZΓΊΓ±iga Cloud Services 24 hours ago
Asnières-sur-Seine Cloud Services 5 days ago
New York City E-mail 10 days ago
Township of Evan Hosting 10 days ago
Ahmedabad Cloud Services 16 days ago
Le Puy-en-Velay Cloud Services 17 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:

  • rea1ReinaCruz
    Reina Cruz πŸ₯ΌπŸ§€πŸ‡¨πŸ‡Ί (@rea1ReinaCruz) reported

    @Cloudflare Fix human verification

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

  • HanifCarroll
    Hanif Carroll (@HanifCarroll) reported

    At a previous job, I was lucky to work with a staff-level front-end engineer who was very good at what he did and thorough like no one else I had worked with. I didn’t always appreciate that thoroughness. At first, I found it maddening. Meetings with product and design would drag on because he always had an enormous list of questions about whatever feature we were discussing. I was usually eager to finish the meeting and start coding. It took me a while to understand that he wasn’t making the process longer. He was asking the questions we would otherwise have to answer halfway through development, when an unanswered question could block the feature or send it in the wrong direction. Every unanswered question holds an assumption, and that assumption might not match what product or design had in mind. I thought about him recently while reviewing the search process for Casamo, a product I’m building to help people compare furnished stays. Before changing the code, I started asking questions: Why were we processing listings already known to be over the user’s budget? Why were hotel-like properties entering the process when the user had asked for an entire place? Why did we stop after finding six suitable stays if ten were available? How old could a review be before it stopped being useful evidence? Those questions exposed decisions that had been made when Casamo ran on a low-powered VPS and needed to do as little work as possible. They didn’t all make sense now that the product runs on Cloudflare. We changed the search process to reject known mismatches earlier, treat six results as the minimum rather than the target, continue until it finds ten suitable stays, and only use reviews from the previous year as evidence. If I had started coding immediately, I probably would have made the existing process faster without questioning whether it was still the right process. I don’t know if I’ll ever have as many questions as he did, but now I understand what he was protecting us from.

  • BK_McCallum
    McCallum (@BK_McCallum) reported

    @imjeremytho @georgeregnery @stelzner_n1150 I 100% agree that the claim maker bears the burden. And I 100% stand by what I said: Your own laziness is the reason you're in this predicament. "Netcraft’s monthly survey shows the web adding roughly 550k–640k net new sites per day. Total hostnames sit around 1.43–1.47 billion. Verisign’s latest Domain Name Industry Brief puts registered domains at 401.6 million, up 8.1% year-over-year. Cloudflare Radar recorded 19% global traffic growth in 2025. Telegeography and ITU numbers show international bandwidth and fixed-network traffic still compounding in the low-to-mid 20s percent range even before you count extra AI crawlers. IDC DataSphere (via Statista) has annual data created at 181 ZB in 2025 and 221 ZB projected for 2026. Consumer cloud storage is a $15B market growing ~17% CAGR; photos alone are 1.72 trillion a year and most of them go to the cloud."

  • Gzmzyn22
    Mildred Bell (@Gzmzyn22) reported

    $CRWV: Q2 Earnings Revenue: 2.6B or 10.4B ARR EOY 2026 ARR Target: 18B-19B Backlog: 104.2B at end of Q2 (129.2B Aug 11) Adjusted EBITDA Margin: 59% Operating Margin: 5% Adjusted Net Loss: -22% Full AI Platform Contrary to misinformation on X, Coreweave serves Managed Inference, Development Tools, Orchestration and Observability and are a full AI Platform. EBITDA Margins Their EBITDA margins with software come out to 59%. $IREN's H1-4 EBITDA margins are 85% but after depreciating DC build cost for an apple-to-apple's comparison, $IREN's H1-4 EBITDA margin minus DC depreciation come out to 55%. $IREN is able to keep up on EBITDA margins without software because IREN is vertically integrated on the power and datacenter front. Coreweave's software make up for it's colocation costs to achieve 59% EBITDA margins. For comparison $NBIS has ~40% EBITDA margins. Once $IREN integrates Mirantis and DSX OS, it has a great chance of leading on EBITDA margins among the 3 Neoclouds. Backlog Coreweave hit a 129.2B backlog on earnings day Aug 11 which is a huge 25B increase from 104.2B at end of Q2. This is great news for $CRWV, $NBIS, $IREN as it shows the unprecedented demand in this sector. Financing Coreweave will likely benefit from Nvidia's 500B financing pool along with $NBIS and $IREN. However, it's high interest cost make it's Net Loss Margin -22% on what otherwise is a great inflection point of 5% operating income. In other words, Coreweave is a profitable business operations wise besides its high interest payments. This bodes well for Neocloud sector profitability as a whole. Enterprise Customers Coreweave has the widest diversification of customers among Neoclouds with: Primary Cloud: Bentley, Caterpillar, Grammarly, Isomorphic Labs, Sunday Robotics. Expanded Partnership with: Cognition, Databricks, HRT, Periodic Labs, Rescale, Runway ML. Primary cloud is important because although Coreweave and NBIS both serve Cloudflare, they are not the primary cloud for cloudflare. Likewise Shopfiy's primary cloud is GCP not NBIS. Being a primary cloud for a customer is more indicative of usage beyond of orchestrated GPUs or bare metal+k8s. Contracted Power 3.7GW by end of Q2 and 4.2GW by Aug 11. This is a majority colocation however, colocation is working for Coreweave as they still achieve 59% EBITDA margin. This sometimes results in delay but their main problem is interest expense, not colocation. $CRWV is a 55B company with 35B debt for a total of 90B EV. If $IREN can buildout 5GW and integrate in Mirantis to catch Coreweave, it has large upside as $CRWV itself still has significant upside from it's 90B EV.

  • HauberDevs
    Hauber πŸ‡΅πŸ‡Έ (@HauberDevs) reported

    @AlexaIs60635 @James_inthe_box absolutely ******* terrible take. Cloudflare literally powers 10% of the internet. Plus alot of services use AWS, if you block that you would essentially be locking yourself out of a good portion of the internet

  • WCTranslations
    Witch Cult Translations (@WCTranslations) reported

    We're aware our site is experiencing increased load times again. This is due to increased traffic following the episode and issues with our Cloudflare integration. Unfortunately, we can't do much right now to improve load times, so please be patient and try not to spam refresh.

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

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

  • shownotover
    shownotover (@shownotover) reported

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

  • krishnasinghdev
    Krishna Singh (@krishnasinghdev) reported

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

  • rea1ReinaCruz
    Reina Cruz πŸ₯ΌπŸ§€πŸ‡¨πŸ‡Ί (@rea1ReinaCruz) reported

    @Cloudflare Fix human verification

  • Spectre_xdd
    Kyzer (@Spectre_xdd) reported

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

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

  • LearnWithBrij
    Brij Pandey (@LearnWithBrij) reported

    πŸ“‚ SaaS Stack ┃ ┣ πŸ“‚ Frontend ┃ ┣ πŸ“‚ React ┃ ┣ πŸ“‚ NextJS ┃ ┣ πŸ“‚ Vue ┃ ┣ πŸ“‚ TailwindCSS ┃ β”— πŸ“‚ Shadcn UI ┃ ┣ πŸ“‚ Backend ┃ ┣ πŸ“‚ NodeJS ┃ ┣ πŸ“‚ Django ┃ ┣ πŸ“‚ Laravel ┃ ┣ πŸ“‚ FastAPI ┃ β”— πŸ“‚ Express ┃ ┣ πŸ“‚ Database ┃ ┣ πŸ“‚ PostgreSQL ┃ ┣ πŸ“‚ MySQL ┃ ┣ πŸ“‚ MongoDB ┃ ┣ πŸ“‚ Redis ┃ β”— πŸ“‚ Supabase ┃ ┣ πŸ“‚ Auth ┃ ┣ πŸ“‚ Clerk ┃ ┣ πŸ“‚ Auth0 ┃ ┣ πŸ“‚ Firebase Auth ┃ ┣ πŸ“‚ Supabase Auth ┃ β”— πŸ“‚ NextAuth ┃ ┣ πŸ“‚ Payments ┃ ┣ πŸ“‚ Stripe ┃ ┣ πŸ“‚ Paddle ┃ ┣ πŸ“‚ Dodo Payments ┃ ┣ πŸ“‚ Lemon Squeezy ┃ β”— πŸ“‚ Polar ┃ ┣ πŸ“‚ Emails ┃ ┣ πŸ“‚ Resend ┃ ┣ πŸ“‚ SendGrid ┃ ┣ πŸ“‚ Mailgun ┃ ┣ πŸ“‚ Postmark ┃ β”— πŸ“‚ Amazon SES ┃ ┣ πŸ“‚ Storage ┃ ┣ πŸ“‚ AWS ┃ ┣ πŸ“‚ Cloudflare ┃ ┣ πŸ“‚ Google Cloud Storage ┃ ┣ πŸ“‚ Supabase Storage ┃ β”— πŸ“‚ Uploadcare ┃ ┣ πŸ“‚ Deployment ┃ ┣ πŸ“‚ Vercel ┃ ┣ πŸ“‚ Netlify ┃ ┣ πŸ“‚ Railway ┃ ┣ πŸ“‚ Render ┃ β”— πŸ“‚ AWS ┃ ┣ πŸ“‚ Domains and DNS ┃ ┣ πŸ“‚ Namecheap ┃ ┣ πŸ“‚ Hostinger ┃ ┣ πŸ“‚ Cloudflare DNS ┃ ┣ πŸ“‚ Google Domains ┃ β”— πŸ“‚ SiteGround ┃ ┣ πŸ“‚ Analytics ┃ ┣ πŸ“‚ Google Analytics ┃ ┣ πŸ“‚ Plausible ┃ ┣ πŸ“‚ PostHog ┃ ┣ πŸ“‚ Mixpanel ┃ β”— πŸ“‚ DataFast ┃ ┣ πŸ“‚ Monitoring ┃ ┣ πŸ“‚ Sentry ┃ ┣ πŸ“‚ LogRocket ┃ ┣ πŸ“‚ Datadog ┃ ┣ πŸ“‚ NewRelic ┃ β”— πŸ“‚ UptimeRobot ┃ ┣ πŸ“‚ DevOps ┃ ┣ πŸ“‚ Docker ┃ ┣ πŸ“‚ Kubernetes ┃ ┣ πŸ“‚ GitHub Actions ┃ ┣ πŸ“‚ CI CD ┃ β”— πŸ“‚ Terraform ┃ ┣ πŸ“‚ Search ┃ ┣ πŸ“‚ Algolia ┃ ┣ πŸ“‚ Meilisearch ┃ ┣ πŸ“‚ Elasticsearch ┃ ┣ πŸ“‚ Typesense ┃ β”— πŸ“‚ OpenSearch ┃ ┣ πŸ“‚ AI Integration ┃ ┣ πŸ“‚ OpenAI API ┃ ┣ πŸ“‚ Anthropic API ┃ ┣ πŸ“‚ Replicate ┃ ┣ πŸ“‚ HuggingFace ┃ β”— πŸ“‚ Gemini API ┃ ┣ πŸ“‚ Integrations ┃ ┣ πŸ“‚ Zapier ┃ ┣ πŸ“‚ Make ┃ ┣ πŸ“‚ n8n ┃ ┣ πŸ“‚ Pabbly ┃ β”— πŸ“‚ Webhooks ┃ ┣ πŸ“‚ Security ┃ ┣ πŸ“‚ SSL ┃ ┣ πŸ“‚ Cloudflare ┃ ┣ πŸ“‚ WAF ┃ ┣ πŸ“‚ Rate Limiting ┃ β”— πŸ“‚ Secrets Management ┃ ┣ πŸ“‚ Marketing ┃ ┣ πŸ“‚ Search Console ┃ ┣ πŸ“‚ Outrank ┃ ┣ πŸ“‚ Buffer ┃ ┣ πŸ“‚ Analytics ┃ β”— πŸ“‚ Kit ┃ β”— πŸ“‚ Customer Support ┣ πŸ“‚ Intercom ┣ πŸ“‚ Crisp ┣ πŸ“‚ Zendesk ┣ πŸ“‚ Tawk β”— πŸ“‚ HelpScout

  • SoccerGuyUS
    SoccerGuy (@SoccerGuyUS) reported

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

  • RealBucketShop
    BucketShop (@RealBucketShop) reported

    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.

  • _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.

  • belljobs94
    William Bello (@belljobs94) reported

    THE GOAT on their free service !! @Cloudflare hands down

  • Trendy_Tim
    Tim (@Trendy_Tim) reported

    @The_Baron_X150 @SportingNest @Cloudflare That was crowdstrike, cloudflare take down half the internet with some dodgy js or dns config.

  • SecWeekly
    Security Weekly Podcast Network (@SecWeekly) reported

    That CAPTCHA may not be protecting you. A click-fix attack can use a fake Cloudflare CAPTCHA to convince users to open PowerShell or Terminal and paste a command themselves. Once the command runsβ€”especially with administrator privilegesβ€”the attack chain can begin. What should organizations block before social engineering gets a user to execute the attack for them? #Cybersecurity #PowerShell #SocialEngineering

  • AdamRackis
    Adam Rackis (@AdamRackis) reported

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

  • mpawlo
    Mikael Pawlo (@mpawlo) reported

    @stutireal cloudflare is never down - I would blame the dog

  • _theCyberDoctor
    Henry C | DevSecOps (@_theCyberDoctor) reported

    4/ The part I'm proudest of isn't the happy path. It's what happens when the web fights back. CrunchBase threw a Cloudflare captcha β†’ agent refused to bypass it, wrote down why, moved on. LinkedIn threw a sign-in popup β†’ agent closed it and read what was visible. Chrome crashed β†’ agent reloaded.

  • ElijahTrillionz
    Elijah Trillionz (@ElijahTrillionz) reported

    There is currently no cards or payment methods that is working for Cloudflare. @Cloudflare @CloudflareDev @CloudflareHelp And no way of getting help. This is bad

  • ric_orna
    Ric Orna (@ric_orna) reported

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

  • Ciunkos
    PrzemysΕ‚aw Zalewski (@Ciunkos) reported

    @efalcao @proofpoint @Cloudflare Most likely by the fact Cloudflare is kinda bad at handling abuse reports - try filling their form and see for yourself. Any service that could be used for spam delivery, will eventually be used for that. And Cloudflare now tastes what other providers experience day to day.

  • BrendanRyanM
    Brendan Ryan (@BrendanRyanM) reported

    @mntruell @petergyang @bot Also having an issue getting past bot blockers, e.g. cloudflare prompts to press a button and prove you’re human. Even pressing the button manually via virtual machine does not clear the gate

  • gabrielrockson_
    Gabriel | Algo Trading (@gabrielrockson_) reported

    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.

  • kristianfreeman
    Kristian Freeman (@kristianfreeman) reported

    Day one support for Cloudflare!

  • argamingpk1
    AR GamingPK1 πŸ‡΅πŸ‡° (@argamingpk1) reported

    @DanielZahoor But Cloudflare DNS routing is so bad.