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.

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

Live Outage Map

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

CityProblem TypeReport Time
New York City E-mail 4 days ago
Township of Evan Hosting 4 days ago
Ahmedabad Cloud Services 9 days ago
Le Puy-en-Velay Cloud Services 11 days ago
Ann Arbor Cloud Services 12 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:

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

  • eelko1976
    ッ ᴇᴇʟᴋᴏ ᴀʟᴇxᴀɴᴅᴇʀꜱ (@eelko1976) reported

    ethereum:native under the 2400$ solana:So11111111111111111111111111111111111111112 just under the $100 mark. Aay. @BloFin_Official Why do I get a temporarily ban from @Cloudflare for too many requests wtf?! Have to use a VPN now (which I wasn't before) otherwise I cannot access MY account.

  • QreatureQriator
    Harlen Bayha 🇺🇸 (@QreatureQriator) reported

    @mrfundman @Cloudflare Did it work with Outlook emails? My bots struggle with Outlook's interface so bad.

  • LUISLUIS532957
    LUIS- LUIS- (@LUISLUIS532957) reported

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

  • 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

  • PadraigOraghail
    Patrick Ryall (@PadraigOraghail) reported

    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.

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

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

  • jeff_weinstein
    Jeff Weinstein (@jeff_weinstein) reported

    Cloudflare, known for internet-scale internet infrastructure, is now building internet-scale billing infrastructure, in partnership with @stripe. (Detailed data about usage and cost is now a fundamental element of any service.)

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

  • nuvorlane
    Nuvorlane (@nuvorlane) reported

    Cloudflare AI Gateway monthly usage invoices no longer break out input and output tokens. Previously you got two lines, e.g. 40k input at $0.000001 ($0.04) and 24k output at $0.000005 ($0.12). Now one line: anthropic/claude-haiku-4.5 — $0.16. Model names on invoices and logs also normalize to provider/model, so dated suffixes disappear from the identifier. Credit-purchase invoices are unchanged. If a FinOps parser keys on token line items or version suffixes, fix it before the next month-start invoice lands.

  • serriff
    Serriff (@serriff) reported

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

  • realjamesmtz
    James Martinez (@realjamesmtz) reported

    @mrfundman @Cloudflare Damn too rich for me.

  • AnimeNovakai
    Anime Novakai | Anime News, Updates & Leaks (@AnimeNovakai) reported

    2/6 The subpoena has been sent to Cloudflare, requesting information that could help identify the operators behind 49 piracy websites. Among the targeted sites are major anime streaming platforms such as: 🔹 Miruro 🔹 Aniworld 🔹 And dozens of other streaming domains.

  • sprki999
    ticktechh (@sprki999) reported

    @OmegaNekoSimp Thats the only human check that doesnt trigger me. What the actual **** does the challenge of clicking a box from cloudflare do? How isnt that challenge useless?

  • Dr_Internets
    Dr. Internets (@Dr_Internets) reported

    @spacebruce @alynokioku Hello, I am Albanian cloudflare. Due to poor technology, I need you to paste this totally real command into your admin command prompt. Very real, trust.

  • 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

  • liltechnomancer
    🍄 DO NOT FOLLOW TIMO 😈 (@liltechnomancer) reported

    @thdxr Because you have process issues. If you didn't extensions would work on cloudflare.

  • Cassiel1137
    Cassiel (@Cassiel1137) reported

    @SportingNest @Cloudflare Quite spectacularly a scam. Luckily anyone who might fall for it (cough... everyone has their off days fella... cough) wouldn't have the first clue how to do any of that ****.

  • 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

  • tangvu_dev
    Tang Vu (@tangvu_dev) reported

    I compared Cloudflare Workers and Vercel Edge Functions, two production platforms built on V8 isolates, using a latency-sensitive crypto analytics service. The workload fetched prices and computed OHLC + VWAP over 24 kline periods.

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

  • yash_d_desai
    Yash Desai (@yash_d_desai) reported

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

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

    @Cloudflare Fix human verification

  • CarloDotGG
    Carlo GG (@CarloDotGG) reported

    @SimonHoiberg Easy fix Step 1: Use Cloudflare AI Gateway to build your own custom Openrouter for your business, then select whichever provider you'd like, or even attach custom providers like BaseTen, FAL .... Step 2: set billing limits per user if needed.

  • noelcetaSEO
    Noel Ceta (@noelcetaSEO) reported

    8/ Layer 5: CDN implementation (distribute content): CDN = Content Delivery Network How it works: - Content stored on multiple servers worldwide - User gets content from nearest server - Fast delivery regardless of geography Setup: - Cloudflare (easiest, free tier available) - Akamai (enterprise) - CloudFront (AWS) Impact: 20-40% speed improvement for global sites.

  • alexanderbetok
    Alex Betok | PolyViper (@alexanderbetok) reported

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

  • TheBaconFather
    Drew Lemacks (@TheBaconFather) reported

    @PancakesRevenge No, I use cloudflare to tunnel. I don't have any open ports on my network.

  • pcppup
    Megumi, Internet Angel 🏳️‍⚧️ (@pcppup) reported

    @NightlyArii i think you are not catching my sarcasm :) i do not know how much you know about cybersec, but a static page would require Cloudflare, Github, or my Computer to get hacked, which is just crazy. You're just criticizing AI because you can. It's good for some things, bad at others.

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