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.

• Domains (33%)
• Cloud Services (31%)
• Hosting (19%)
• Web Tools (11%)
• E-mail (6%)

Live Outage Map

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

City	Problem Type	Report Time
Angers	Cloud Services	9 days ago
London	Domains	12 days ago
Noida	Hosting	24 days ago
Jewar	E-mail	25 days ago
Braga	Web Tools	25 days ago
Noida	Cloud Services	26 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:

• 
  Sulabh Puri (@sulabhpuri) reported 6 minutes ago

  A lot of problems with @Cloudflare today.

• 
  starmex (@starmexxx) reported 8 minutes ago

  WHY WASTE 16 MINUTES OF YOUR TIME ON THIS AI ENGINEER EUROPE TALK WHEN I CUT THE 5 BEST MOMENTS INTO 4 MINUTES FOR YOU bright data engineer exposed why your ai agent lies about searching the web. cloudflare blocks 20% of web from ai. 60% of chatgpt citations are broken. agents hallucinate instead of saying "i can't" 00:00 - llms are programmed to please. they make things up instead of saying "i can't" 00:42 - cloudflare blocks 20% of web. 60% of chatgpt citations are broken 02:03 - gpt-5 fails all 5 web tasks without proper tools. zero out of five 02:42 - cloudflare labyrinth feeds ai fake data. bigger hallucinations 03:13 - don't parse with llm. build a parser. saves 99% of tokens bookmark this and watch the supercut below

• 
  Tom Talks Cars (@TomTalksCars) reported 13 minutes ago

  @EddCoates Cloudflare AI Crawl Control is pretty decent at cutting things down

• 
  Fardeem (@FardeemM) reported 13 minutes ago

  If you're on your way to building a billion dollar company that involves a web app, here are some of my notes on architecting the frontend. if you don't do this, it's probably fine but one day you'll hire someone to fix it but truly that person could be doing some other higher value thing if you make some key optimizations on day 1 you don't even have to learn anything you're gonna tell your agents to do it anyways! okay here it goes: - Make your server code generate a openapi spec which then generates all the relevant client side code. Never do this by hand. Typing backend types instead of generating them should be banned - You need to make a decision on how the client talks to the backend. rest/graphql works in which case please just use tanstack query. other libraries will look similar but tanstack query truly is goated. - if you want linear style sync setups or offline mode, think about this HARD and architect it from day 1. Bolting this on later is so tedious. - People like using plain react router but things have gotten a lot better since then. Try their new framework mode or just even use tanstack router. Use route data loaders. - If you store a lot of state in query params, make that a first class citizen and make sure its type safe. use nuqs or tanstack query. - Most apps just need a single state management situation for server state and thats it. If you have other bespoke needs, i have quite like zustand and xstate/store. - If you have a super interactive app where things come in and out of view, theres a lot of frontend state to maintain, music is playing and what not, lock in and learn xstate. Trust me if you wanna keep ur sanity, you need to model ur frontend as a state machine otherwise you're gonna be deep in useEffect hell - React compiler is here my friends, the days of useMemo and useCallback are gone. Update your priors accordingly - Tailwind is easy and fun but makes it really hard to maintain a large app with consistent styling. You need a "agent-first design system/component library" but maybe this is a rant for another day - Don't be afraid to hack your routing library to fit your needs more closely. A lot of apps have "drawers" to show additional info. You should 100% be able to say "here's a route, make it a drawer" and everything should be handled from there. - Managing loading and error states using isPending and isError is madness. Lean into Suspense and ErrorBoundary. - Figuring out a blessed path for websockets and SSE on day 1 i think will pay dividends in the long term if you're building anything AI related. - If you're building a SPA, don't use next.js. it literally makes no sense. Why would you do this. - Definitely deploy on Cloudflare or vercel. There are other services but trust, there have weird missing features. - Assuming you build something people want, the next job is to build the factory so it can efficiently build the thing. Act accordingly.

• 
  Jeff Needles (@jsneedles) reported 14 minutes ago

  @Hussain_Joe @_ceifa Well, the key is its pretty much managed, just not e2e. Like it's Cloudflare Workers + pipelines + queues -> CH cloud. All managed services! Just the raw volume makes most "pure" managed analytics providers extremely prohibitive -- like prob 10x the cost at least. Of course, there's other options that are really self hosted that are less analytics-focused... or things that rely more on object storage as the source of truth (like R2 SQL, which would actually prob be cheaper) But I've put in maybe 10 hours of necessary maitenance in the last year, occasionally the analyst who uses the system will ping me for questions/advice etc -- but raw infra/system wise, like 0 issues!

• 
  Alon M. (@Alon_iploop) reported 14 minutes ago

  @BenjaminFlatz Stealth helps, but most Cloudflare failures are environment issues: IP reputation, geo, sticky sessions, and consistent browser state. IPLoop provides the residential network layer so Playwright/Scrapy stacks don’t fail just because the traffic looks wrong.

• 
  David Herrmann (@herrmanndigital) reported 16 minutes ago

  Meta ads in 2015: 1. Take a photo of product with iPhone. Open Power Editor, launch ad in under 2 mins. 2. Refresh PE and see 1:1 conversions in under an hour, scale within 3-4 hrs. 3. Spend the rest of the day coming up with fun ideas for new offers, new landing page ideas, new product ideas, new copy ideas. Meta ads in 2026: 1. Hire creative strategist -> Who hire creative agencies / editors -> who build batches of creative. 2. Open ads manager, go through 25-30 prompts of things you have really no clue about, but Meta is insistent it'll lower your CPA by 7.9% based on a study from 2 advertisers in 2022. Click publish after 1 hr of building out 10 new concepts. 3. You're then hit with an error publish with messages like: "you have no shops select," or "you don't have page permissions," or "this creative has expired, please try a new one" you finally are able to hit publish. 4. Finally, you can go on with your day. But wait, client sees that they are getting discounts on the ads you just launched coming in. You open up ads manager and go to ad level to go through multiple areas to figure out why. 5. Ah, Meta has randomly turned the promotions automatically on. No worries, you pause it. On with your day. 6. Someone who knows someone at the company for whose ads you just launched flags to friend that the ads are appearing with a dubstep version of a Beethoven song and seem out of touch for the brand. You're then texted to go pause the music. 7. Open ads manager, navigate to ad level, pause music. You're then hit with a prompt from Meta: "WHY ARE YOU TURNING THIS OFF?!" You hastily respond, "BECAUSE IT SUCKS!" 8. Visibly irritated now over Meta you finally settle in to do the other part of your job, analysis! 9. But wait, there appears to be an outage! Everyone texting, "Is Shopify down?," "Is it Cloudflare?," "Is it AWS?," "No! It's Meta!" Ok, well now you're in fight of flight. Should we wait? Should we pause? Let's wait, yeah let's wait. This is just a minor blip. 10. Meanwhile you're not left refreshing things every 5 min instead of doing analysis and research. Finally, it is night time and you can relax (not)! On this particular day you managed to launch 10 ad sets and do nothing else. Feeling defeated because what once took 2-5 min to do now feels daunting. It feels like you now spend the majority of your day in defense mode. Not because the work has changed or the people, but the process for doing it all has. And that's why you're feeling burnt out media buying friends and creative friends.

• 
  max guy 😐 (@GolerGkA) reported 18 minutes ago

  @artillain @ThePrimeagen Ok I’m stupid bear with me. Usually with cloudflare on front of static public site, users don’t hit my web service most of time anyway, they hit cloudflare cache. Does it still work? I assume that information that anybody would want to scrape would be on static public endpoints.

• 
  Coyote (@8bit5_0) reported 18 minutes ago

  @benlandautaylor the only tech layoff that can’t be explained by bad financials (either due to post ZIRP overhang or increased AI capex) seems to be Cloudflare. So I guess not for tech really

• 
  zeb (@zebassembly) reported 24 minutes ago

  @astuyve @boristane Yeah we aren't happy that the limitation has existed for so long either. We're working hard to try to not paint ourselves into a corner when the o11y platform we've built for Workers expands to being used for other products. There are many shortcuts we could have taken to got this shipped sooner but they may have put us in a state where we later couldn't reconcile it with tracing for another product. We're really going all-out for the o11y platform we're building within Cloudflare and that'll inevitably slow things down by preventing us from taking the easy paths.

• 
  Mark Dembo (@darkmembo) reported 24 minutes ago

  i am so proud working at @Cloudflare. i have never experienced anything like it. people do whatever it takes to make customers happy. shipping fixes, improvements or entirely new services (!) timelines are hours or days for small things. weeks for bigger ones.

• 
  tcpdump (@dump_tcp) reported 25 minutes ago

  @EddCoates if need any help with cloudflare I can help with some rules also it seems you're webserver code is bottlenecking you causing that error usually due to not being able to handle that many connections or to much cpu usage the webserver process dies i suggest using #golang best lang

• 
  AI News 24 (@ainews_24_7) reported 26 minutes ago

  Cloudflare $NET rolled out the Cloudflare One stack to give AI agents autonomous control over Zero Trust environments. The new skill library handles planning and deployment without requiring manual migration support.

• 
  goksan (@g0ksan) reported 26 minutes ago

  @thomas_ankcorn @SamNewby_ @thomas_ankcorn thanks for the help the issue is still unresolved (despite being closed) and both the assignee and assigner no longer appear to be at Cloudflare

• 
  𝗶𝗮𝗺𝟰𝘅 (🌷,🦈) (@iam4x) reported 32 minutes ago

  @DegenCT @TheCryptoNexus - Proxy the ui api of hyperliquid through cloudflare to fetch sub-accounts - Then implementing the spot trading with support of sub-accounts

• 
  Special Situations 🌐 Research Newsletter (Jay) (@SpecialSitsNews) reported 32 minutes ago

  New Activist Name: Shares of $MTN are trading up 13% at $141.65 on Thursday, rebounding sharply from their 52-week low of $118.51 hit earlier this year, as the Semafor scoop circulates across trading desks. The intraday move lifts the company's market cap to roughly $5.05 billion. According to Semafor, Vail's bankers are tasked with assessing vulnerabilities across a broad front: labor unrest, weather-related demand swings, and the specific pressure campaign being waged by Prince, who co-founded Cloudflare (NET). Prince told a local Colorado publication in June 2026 that he is willing to invest $500 million in Park City Mountain Resort and admitted he has already fielded calls from activist investors probing Vail's weaknesses. His preferred blueprint would see Vail pivot to an asset-light model, acting as a partnership facilitator rather than a direct mountain owner, a structure that would almost certainly require carving up the company's core real-estate holdings. The timing is awkward for management. Vail reported fiscal Q3 2026 earnings per share of $8.81, missing the consensus estimate of $9.09 by 3.1%, while revenue of $1.21 billion came in roughly $10 million below forecasts. The company subsequently cut its fiscal 2026 net income guidance to a range of $128 million to $162 million and trimmed Resort Reported EBITDA guidance to $735$755 million, down from the prior range of $745$775 million. Net debt has climbed to $2.65 billion from $2.24 billion a year earlier, pushing net leverage to 3.5x trailing twelve-month EBITDA as of April 30, 2026, while cash on hand stood at $371.4 million. Into that environment, the board moved in May 2025 to recall Rob Katz, the executive who originally built Vail into a multi-mountain empire, ousting his hand-picked successor in the process. Katz has since focused on the operational grievances that drove customer dissatisfaction, particularly lift-line congestion and chronic labor shortages, introducing products like Epic Friend Tickets and discounted super-advanced lift tickets that are showing early traction. The move signals that Vail's board views operational credibility as its first line of defense against any activist pitch centered on mismanagement. Management also has a financial lever to highlight in any proxy fight. The company pays a quarterly cash dividend of $2.22 per share, with the next payment scheduled for July 9, 2026, equating to an annualized yield of roughly 6.6% at current prices. That yield argument, steady cash returns while the turnaround plays out, is a standard defensive talking point, though it carries less weight when leverage is rising and guidance is being cut. Investors will get a clearer read on whether Katz's operational fixes are gaining traction when Vail reports fiscal Q4 2026 results, tentatively scheduled for September 24, 2026. The setup is challenging: consensus EPS for that quarter stands at -$5.05, with eight analyst downward revisions in the past 90 days and no upward revisions, reflecting the structural headwinds Prince and any allied activist would likely exploit.

• 
  Wallstreet Dragon (@longwashere) reported 36 minutes ago

  DD: Long term holdings. $NET cloudflare and why it's important in the age of agents ELI5: The world is moving towards agent. Big industries need better cloud bot protection, developers need LLM computing on the edge. Cloudflare provides the most afforadable option for both, even heavy aws users are using cloudflare for these purposes. What is Cloudflare? For the technically challenged or pre-med professionals, Cloudflare is a web infrastructure and security company that acts as a protective, performance-enhancing shield between a website and its visitors by providing services like content delivery networks (CDNs), DDoS mitigation, and secure domain routing. TL;DR: For the simple folks, it's that **** that pops up with the CAPTCHA to make sure you're not a bot. For developers, it's that **** that makes your sites fast and secure from bots. What is Cloudflare's growing revenue? Application Security and Content Delivery Network (CDN). What is a Content Delivery Network? A CDN is basically a network of servers used to store files closer to its users for faster retrieval. Imagine an app creates a backend database storing all its images on AWS based in US-East. A CDN will then copy the most commonly used images in that S3 database and duplicate them across multiple regions (Asia, Europe, US-East). When an app makes a service request, it will make the request to Cloudflare first. Cloudflare then uses its internal logic to determine if the data needed is in a nearby Cloudflare edge server (on the edge) or if it needs to get it from the main database in US-East. This is called storage on the edge. This CDN mechanism is a relic of Web 2.0, but it will become significantly more important in the age of AI. Now, instead of storing images, large AI providers will be storing entire LLM contexts on the edge. So instead of training specialized ML models to do a specific task, app companies can use a general-usage LLM with a stored context for that specific task, and it will be fast, too. This mechanism is called Prefix Caching or Prompt Caching. By doing this, it makes the LLM responses almost instantaneous. So all your consumer apps that use LLMs—like CALai, Duolingo, Grok, etc.—are most likely already using this process. Beyond simply storing data on the edge, the industry is shifting toward deploying entire servers and specialized AI models locally. A major component of this architecture relies on LLM routing. Instead of hosting massive, resource-heavy models on every single edge device or regional server, companies are deploying highly optimized, lightweight router models at the edge. These local routers analyze incoming user prompts to determine the most efficient way to handle them. If a task is simple, the edge model processes it instantly to minimize latency and eliminate cloud compute costs. If the task requires deep reasoning or a massive knowledge base, the router intelligently forwards the request to a larger cloud-hosted model. Additionally, these edge routers leverage tool calling, which allows them to execute local APIs, query regional databases, or trigger specific code workflows without needing to round-trip back to a centralized data center. Moving from simple edge storage to localized edge intelligent compute represents a massive paradigm shift. It allows enterprises to scale AI applications efficiently, safeguard data privacy, and drastically slash infrastructure costs. Cloudflare Security in the Age of Agents This one is simple. You know that Cloudflare CAPTCHA that pops up when you're entering a website or checking out with a credit card? Websites PAY for that CAPTCHA. And they pay a lot. These features block spam, bots, and DDoS attacks. When you move your mouse to click the CAPTCHA, Cloudflare uses proprietary logic that determines you're human by calculating how fast your mouse moved, the angle you moved it, how long you waited, and any other actions you took. Sometime in the 2010s, every website figured out that paying for this small puzzle CAPTCHA was more cost-effective than getting DDoS'd by bots, so almost every single site adopted it. The CAPTCHA is only one of Cloudflare's products in its security suite to block bots from websites, but the overarching theme is the same for all its features: blocking bots. Well, it's 2026 now, and web traffic across the board has increased, mostly driven by AI and AI agents. Automated web traffic has increased by 600% in 2026 alone. Guess who is positioned perfectly for this? Cloudflare. Not only is Cloudflare blocking bot traffic, but it's also getting paid by them. Cloudflare is releasing a new product (Pay Per Crawl) that allows website owners and Cloudflare to get paid for LLMs crawling their content. Cloudflare is simply winning by creating the gates for web traffic and now charging a toll fee for bots to use them. Cloudflare is direct play on internet traffic, which is a correlating play on ai agents and LLM adoption and usage. If you think people will continue to use ai agents and LLM, then cloudflare is your guy. Cloudflare valuation has dropped recently because of the layoffs due to ai, even though revenue has sped up. This drop was more of emotional sell off than a fundamental one. It's valuation has already bounced back. (Cloudflare is trading at 235 as of this post, I bought in earlier in the 190s for a swing trade after the bogus layoff dips, wish i bought in more)

• 
  special k | CEO of stressed out era (@specialkdelslay) reported 38 minutes ago

  @HeadmasterDuck We have cloudflare pro acc which does mitigate some of this. The cloudflare dependency everyone has is a problem tho

• 
  Your Private Proxy (@YourPrivateProx) reported 39 minutes ago

  @lea7hersm17h FlareSolverr clears the JS challenge. It doesn't fix IP reputation — if your exit is already flagged, Cloudflare just serves another challenge after each solve. Works on clean IPs at low scale. Breaks on shared or abused exits.

• 
  Devine dev (@Andrew652263) reported 43 minutes ago

  @elshad_ff @Teknium Had similar websocket issues before. One thing that helped was testing the same dashboard through Pinggy to confirm if Cloudflare was the bottleneck.

• 
  Command Code (@CommandCodeAI) reported 45 minutes ago

  We're aware of an ongoing incident. Partial outages at Cloudflare and Supabase are causing Command Code CLI to experience intermittent connection issues. We're actively investigating and working on a fix. Thanks for bearing with us.

• 
  Jose (@SolutionsCay) reported 46 minutes ago

  Two changes to how I work with agents: 1. GitHub App so the agents manage issues directly. Keeps the repo clear of throwaway spec and todo files. 2. EmDash (Cloudflare's serverless WordPress successor) for internal docs. Runs on D1, just SQLite under the hood, so I can export the content and move it anywhere. No more docs sprawl.

• 
  pathik (@pathikghugare) reported 46 minutes ago

  @NotRoodraksh @4k_isn not working on cloudflare warp

• 
  Christopher Johnson (@cj_enlighten) reported 48 minutes ago

  Vanilla web search in an always-on agent gets blocked. Not a Hermes bug. A structural 2026 problem. Cloudflare and Akamai are aggressive enough now that any general-purpose agent hits the wall. You need Tavily or equivalent. Budget time for it.

• 
  firtoz (@firtoz) reported 52 minutes ago

  @EddCoates Would/does Cloudflare help?

• 
  Diogo D (@DiogoTheReal) reported 54 minutes ago

  @EddCoates @Cloudflare rate limiting might help

• 
  Curtis Thornton Jr (@RdclslyGudLookN) reported 57 minutes ago

  @EddCoates Of course cloudflare could never stop my automated scrapers, and now they're offering automated browsers that aren't even as good as mine, perhaps reasoning that they know what they can stop and can always choose to not stop themselves.

• 
  wast3 (@0xWast3) reported 1 hour ago

  A DEVELOPER BUILT AN ENGINEERING SITE FOR A CORPORATE CLIENT AND CHARGED $3,200 FOR IT the hosting bill was $0, the domain was $0, the SSL was $0 he registered a free domain on DigitalPlat, pointed it at Cloudflare in twenty minutes, and deployed the site on Cloudflare Pages the client saw a live URL with a padlock and never asked what it cost to run here's the full stack he used: DigitalPlat free domain - no card, no renewal creep Cloudflare free plan - DNS, CDN, DDoS protection, SSL auto-issued Cloudflare Pages - connected to GitHub, builds and deploys automatically total infrastructure cost: $0, managed from one dashboard the mistake most developers make is paying three companies on three renewal cycles for every experiment they ship once the stack was locked, every new client demo went live in fifteen minutes $3,200 charged, $0 spent on infrastructure the margin was the entire point register first, deploy second, invoice third

• 
  rho (@jmuh997) reported 1 hour ago

  stc routing in eastern province is so bad i have to use cloudflare warp to use spotify

• 
  Court Reinland (@Court_Reinland) reported 1 hour ago

  @EddCoates Cloudflare can help with this, they can tune out a lot of this.