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 (54%)
• Hosting (31%)
• 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	2 days ago
Township of Evan	Hosting	2 days ago
Ahmedabad	Cloud Services	8 days ago
Le Puy-en-Velay	Cloud Services	9 days ago
Ann Arbor	Cloud Services	10 days ago
Palermo	Hosting	11 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:

• 
  Ric Orna (@ric_orna) reported 3 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.

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

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

• 
  shownotover (@shownotover) reported 4 minutes ago

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

• 
  Yaz (@yazcaleb) reported 4 minutes ago

  @tin_runje @Cloudflare won't let you down

• 
  Jonathan.G (@Jonathan2134) reported 8 minutes ago

  In reality CloudFlare makes searching the internet worst place because number of websites you can't use despite not VPN.

• 
  lasan (@las_nish) reported 9 minutes ago

  Comparisons of Free Trial Abuse Prevention Services If you're running a SaaS with a free trial or focusing on PLG, authentication and abuse prevention are not the same problem. - WorkOS: If you're already using WorkOS, WorkOS Radar is probably the first thing I'd look at. For a WorkOS stack, WorkOS AuthKit + Radar makes the most sense. You don't need to bolt another authentication system onto your app just to get abuse signals. - Auth0, Supabase Auth, Better Auth: These are primarily identity/authentication platforms. Integrating only these can't prevent free trial abuse. - Custom: Like the previous options, you need a custom way to prevent free trial abuse. Most free trial abuse methods involve disposable emails, Google dot variations, Google/Gmail domain variations, and plus addressing. That's why even when you block bots via Cloudflare Turnstile or CAPTCHA, you can still get these abusers. The industry standards: - Block free trial abuse using lists hosted on GitHub: This is a pain in the ***. If you don't want to pay money, you can use a service that offers a generous free tier. - WorkOS Radar: This is mainly used at the enterprise level. They focus more on WorkOS-related integrations rather than integrations with other providers. - ZeroBounce, NeverBounce, MillionVerifier, DeBounce: These are mainly used to clean/validate emails. There are 100s of alternatives, and most are similar with minor differences. They all have disposable email checking APIs. - UserCheck: This is also an email validation API, but they focus on blocking fake email addresses. It's better than a basic email verification API. - Autheona: This is in the same category as WorkOS Radar and UserCheck, but with more features. It also focuses on fake user detection and is growing with a real user base. Now, pricing: - WorkOS Radar: First 1,000 checks free, then $100 per 50 checks. No application-specific logic changes. Easy to integrate and manage. - ZeroBounce: 100 free validations in the free tier, then pay-as-you-go, starting at 2,000 for $39, and so on. - NeverBounce: No free trial or use case, $8 per 1,000 checks. - UserCheck: 1,000 API requests per month in the free plan. The rule-based engine is not included in the free plan, and you can get up to 1 request per second. - Autheona: 3,000 checks per month, with the rule-based policy engine included. Standard API request rate limitations apply, similar to paid plans. Now, use cases: - WorkOS Radar: Block disposable emails, plus addressing, and Google dot variations. - ZeroBounce, NeverBounce, etc.: Block disposable emails. - UserCheck: Block disposable emails, plus addressing, and Google dot variations; detect public emails; email suggestions; syntax validation; role detection. - Autheona: Everything included in UserCheck, plus business/free/government email identification, deliverability checks, fraud patterns, punycode and mixed-script checks, VPN detection, and bot detection (not necessary if you already use CAPTCHA, Cloudflare, etc.). Final decision from me: - Use WorkOS Radar if you're already in the WorkOS ecosystem. It's harder to integrate with other auth providers. - Use ZeroBounce-like APIs if you need basic disposable email checks. They're not as good if you need a better free tier. - Use UserCheck if you only need email-related validation and want to stay within the free plan. - Use Autheona if you need the most generous free tier available with a custom policy engine. All services take a maximum of a few hours to integrate and test. Both UserCheck and Autheona have a similar approach: integrate once and never touch the code again.

• 
  Gabriel | Algo Trading (@gabrielrockson_) reported 10 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.

• 
  Alex Betok | PolyViper (@alexanderbetok) reported 10 minutes ago

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

• 
  JK (@_junaidkhalid1) reported 12 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.

• 
  2$p00ky (@dos2p00ky) reported 13 minutes ago

  No ******* way that’s really you messaging in that chat…but then I accidentally clicked the button, the chatbot responded, I sent an emoji; then you sent a name and email template & then suddenly OF was also trying to track along with ur site through cloudflare 💀 What a ******* webhook to stay connected to every chat someone has open from ur webpage authenticated by the network cert…holy **** 🥵 for that setup

• 
  Chris Locke (@chrisjlocke) reported 13 minutes ago

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

• 
  Kyle Avery (@kyleavery) reported 20 minutes ago

  @wongmjane @Cloudflare finally, i won’t need 3 workers for each service 🙏

• 
  Declan | Rust Developer (@buildWithDeclan) reported 20 minutes ago

  @acolombiadev @Cloudflare Thats why i am loyal to them. They provided services when i was poor. All my platforms are in cloudflare

• 
  Eli Yumn (@EliYumnik) reported 27 minutes ago

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

• 
  Krishna Singh (@krishnasinghdev) reported 29 minutes ago

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

• 
  Mildred Bell (@Gzmzyn22) reported 32 minutes ago

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

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

• 
  Α Ω Programmer (@OmegaNekoSimp) reported 37 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.

• 
  bored knees (@boredknees) reported 39 minutes ago

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

• 
  Gaylord (@laolu_afolabi) reported 40 minutes ago

  @lanreadelowo From Claude: """ Technically, yes — it's buildable, and "platform-agnostic" is realistic because most providers and gateways (OpenRouter, LiteLLM, Portkey, etc.) have already converged on an OpenAI-compatible schema, so a routing layer that swaps providers behind one endpoint isn't a huge engineering lift. But there are a few things in the premise worth stress-testing before you build. **The "discount arbitrage" framing is a bit shakier than it sounds.** Most of these gateways aren't reselling models at a discount — they're reselling at close to list price plus a fee. While OpenRouter states it doesn't mark up inference pricing, its credit purchase fee effectively acts as a surcharge on all usage. LiteLLM's pitch is the opposite direction — zero markup by self-hosting, with OpenRouter's ~5% fee costing meaningfully more at scale. So the "discounts" you'd be arbitraging are less "provider A is cheaper than provider B for the same model" and more: rate-limited free tiers, short-lived promos, or BYOK arrangements — OpenRouter's BYOK is free up to a monthly allowance before a 5% fee kicks in. Those are real, but they're capacity-constrained and often disappear once volume shows up — hard to build a durable business on chasing them. **The bigger product risk: tokens/models aren't fungible.** Swapping Gemini for Claude for GPT under one endpoint isn't like arbitraging cloud spot instances — different tokenizers (so "$/token" isn't apples-to-apples), different tool-calling formats, different output style and capability. If your router silently reroutes a customer's traffic to whatever's cheapest this hour, you can quietly degrade the app built on top of it. That's the actual hard problem, not the proxying. **What's actually working in production right now is narrower than blind price-routing:** AT&T processes tens of billions of tokens a day using cache-aware routers that send simpler tasks to cheaper models, cutting costs up to 56% with only ~2% quality degradation, and this "model cascade" pattern — cheap/fast models handle the default case, only escalating to a frontier model when a confidence check fails — is used by both AT&T's LiteLLM-based router and Databricks' Smart Router. That's routing by task-fit with cost as a constraint, not routing purely by whoever's running a promo this week. **Competitive landscape is already crowded**: OpenRouter, LiteLLM, Portkey, Requesty, Helicone, Not Diamond, Martian, TrueFoundry, Cloudflare AI Gateway, Ofox all do some flavor of unified-endpoint routing today, several with automatic fallback/cost-based rules already built in. Pure discount-hunting is a thin moat — anyone can scrape pricing pages, and providers may treat aggressive arbitrage-only usage as a ToS problem. Where I'd actually look for a wedge if I were you: quality-aware routing with an audit trail (so teams can trust that "cheaper" didn't mean "worse" for their specific task), rather than price-only arbitrage. """

• 
  William Bello (@belljobs94) reported 40 minutes ago

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

• 
  Stuti (@stutireal) reported 44 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

• 
  COLLINSEO (@alexcollinseo) reported 50 minutes ago

  Breaking news! Your site might start blocking AIs from September 15th.. And if you block them, you won't show up in AI answers. The good thing? It takes a sec to unblock! This setting is inside Cloudflare. You might not even know your website uses Cloudflare because it works in the background as a CDN, helping your website load faster. If you check your website using the tools I mention, you can find out whether Cloudflare is being used on your site. Cloudflare seems to have taken this step because of how AI companies are crawling websites, and honestly, I don't completely disagree with the reason behind it. But having AI crawlers automatically blocked from September 15 could be a problem if you want your business to appear in AI answers. The setting is inside Security Settings. Look for the AI crawler control and make sure it is set to allow rather than block. This is especially important if AI visibility is part of your strategy. With one of my clients, we went from zero to around 500 visitors from AI traffic in two months. And what I did was exactly what I explained in the video. If your AI crawlers are blocked, you're potentially closing the door on that traffic before it even has a chance to reach you. #SEO #DigitalMarketing 👇🏼 Comment VIDEO for the FULL VIDEO BREAKDOWN

• 
  Ben Hocking (@bmwhocking) reported 50 minutes ago

  @rustie5555 There are a lot of round robin API calls for content. Works fine if you are close to their US data-centre. Sucks for us. They are using Cloudflare, I don’t believe they are processing at Cloudflare’s edge, just caching content. They need better & faster timeline building.

• 
  Daniel Zahoor (@DanielZahoor) reported 55 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.

• 
  Atif (@ioAtif) reported 56 minutes ago

  @acolombiadev @Cloudflare @coderhq Although it's not a service but a whole platform

• 
  Noel Ceta (@noelcetaSEO) reported 58 minutes ago

  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.

• 
  manny shaw (@MannyShaw) reported 60 minutes ago

  @0xAdesola 1.1.1.1 does not block malware or phishing. For that, use 1.1.1.2. DNS generally cannot unblock geographically restricted streaming services. That normally requires an authorised VPN or Smart DNS service. It cannot increase your broadband speed. It may make the beginning of website loading slightly quicker if your ISP’s DNS is slow. AdGuard DNS blocks many domain-based advertisements, but not every advertisement. It usually cannot reliably block YouTube, Instagram or advertisements served from the same domain as the content. Parental DNS is useful but not foolproof. VPNs, encrypted DNS, mobile data and some apps can bypass router-level filtering. How to change DNS on your router While connected to your home Wi-Fi, open a browser. Enter one of these common router addresses: 192.168.1.1 192.168.0.1 192.168.29.1 192.168.100.1 The correct address is often printed underneath the router as Router IP, Gateway or Web GUI. Sign in using the router’s administrator username and password. This is not necessarily your Wi-Fi password. Check the router label or your ISP’s documentation. Before changing anything, take a photograph or screenshot of the existing settings. Look for a menu called: Internet or WAN Network DHCP Server LAN Settings DNS Settings Disable Automatic DNS, Obtain DNS automatically, or DNS from ISP. Enter your chosen pair. For general family protection, I suggest: Primary DNS: 1.1.1.3 Secondary DNS: 1.0.0.3 For advertisement blocking instead: Primary DNS: 94.140.14.14 Secondary DNS: 94.140.15.15 Do not mix servers from different providers; otherwise filtering may become inconsistent. Tap Save/Apply and restart the router. Disconnect and reconnect your devices to Wi-Fi, or restart them. Cloudflare confirms that router-level configuration normally applies the DNS setting across connected devices.

• 
  That Brazilian Omo Eko (@sholawa) reported 1 hour ago

  Cloudflare has my airtel IP restricted lol.... Slow internet caused it; I must have hit the rate limit that day...

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

  @Cloudflare Fix human verification