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 (32%)
• Cloud Services (28%)
• Web Tools (16%)
• Hosting (16%)
• E-mail (8%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Cloud Services	10 days ago
New York City	Hosting	12 days ago
Manchester	Domains	1 month ago
Angers	Cloud Services	1 month ago
London	Domains	2 months ago
Noida	Hosting	2 months 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:

• 
  Jerry Combs (@PointBlueTech) reported 6 minutes ago

  @PH0ENIXSMITH @thdxr Exactly. I never have to do anything in CloudFlare myself.

• 
  Colin Son (@txmedai) reported 9 minutes ago

  @ptremblay Yes Cloudflare is very good. And free tier is amazingly generous. Isnt quiet idiot proof (why do I have independent turnon AI gateway or R2 or all these individual features) but at least there’s not a million layers of IAM. GCP and AWS are fine

• 
  Sumedh Bengale (@ssbengale) reported 14 minutes ago

  @anupamrjp Cloudflare but they support a lot of TLDs I'm also scared of the day they decide to ban my account for whatever reason and eat up my whole portfolio

• 
  Stefan-Iulian Tesoi (@stefantul) reported 14 minutes ago

  @thdxr The biggest issue that I had with Cloudflare were the disappearing env variables. Even with wrangler secrets put command.

• 
  VICTOR (@victoris_x) reported 14 minutes ago

  @TheRealAdamG I tried it with Crunchyroll but Cloudflare verification stopped me from login.

• 
  Duane C (@DuaneC6) reported 15 minutes ago

  @CryptoCyberia The internet was never a system of tubes, it has always been 500 micro-services pointed at each other like loaded firearms. People on remote, nearly-uncontacted islands know when Cloudflare goes down, and now it goes down all the ******* TIME.

• 
  Jono Young (@chsweb) reported 16 minutes ago

  @CloudflareHelp love you. No help needed. Maybe I should send to @CloudflareLove … which even more cloudflare than I thought.

• 
  Vlady Veselinov (@vladinator1000) reported 17 minutes ago

  @thdxr What specifically can't you do with IaC? Maybe someone at Cloudflare can help? @dillon_mulroy do you know someone who works on Wrangler?

• 
  Ray 🇺🇦🏳️‍🌈 (@uasneppy) reported 18 minutes ago

  I’ll try to fix snepclub twitter embedder later today, sorry :( I didn’t know about the new updates and me having to have a burner account, plus deploying it on Cloudflare 💀

• 
  spongebobham2billion (@spongebobhamtwo) reported 19 minutes ago

  Put that neocities **** down and buy a cloudflare domain like a real man

• 
  Quentin (@QuentLaBrute) reported 28 minutes ago

  @Sousinr Hope they never read this but cloudflare feels like a blessing, way too cheap for everything you get to do with it! they’re a critical part of my stack and have never paid them anything

• 
  Fayi (@fayimora) reported 32 minutes ago

  @pidotdev Possible issue for UK/London users: model catalog requests are timing out. I VPN'd to another country and they worked immediately. Perhaps a Cloudflare edge hiccup?

• 
  Konstantinos (@kostasbotonakis) reported 34 minutes ago

  Cloudflare support: Health checks, checking a static page on Cloudflare Pages show plenty of outages. It’s been now 2 weeks

• 
  Jason Karns (@jasonkarns) reported 34 minutes ago

  @Cloudflare @Cloudflare so i go to set a password. and I can't set a password without providing an old password. WHICH I DON"T HAVE. **** YOU CLOWNS

• 
  nik skld (@nikskld) reported 35 minutes ago

  ANTHROPIC SHIPPED A CRON SCHEDULER FOR AI AGENTS AND ALMOST NOBODY COVERED IT. Every thread you’ve seen about Claude Managed Agents is still recycling the April 8 launch post. Three months later the product barely resembles that announcement. What actually shipped since: •Scheduled deployments (June 9). Give an agent a cron schedule. Every time it fires, the agent opens a fresh session and completes the task. No scheduler to build, no scheduler to host. •Environment variables in vaults. Register an API key with the domains it’s allowed to reach. The sandbox only holds a placeholder. The real key gets attached at the network boundary, on approved domains only. The model never sees it. •Self-hosted sandboxes (May 19). The agent loop stays on Anthropic’s infrastructure. Tool execution moves inside your perimeter. Cloudflare, Daytona, Modal and Vercel are supported out of the box. •Memory graduated from research preview to public beta. Only MCP tunnels and dreaming are still gated behind an access request. Pricing almost nobody quotes correctly: standard token rates plus $0.08 per session-hour. Runtime is metered to the millisecond and only accrues while the session status is “running.” Waiting on your reply or a tool confirmation costs nothing. Now the part the hype threads skip. Managed Agents is stateful by design. Conversation history, sandbox state and outputs are stored server-side. Anthropic’s own docs state that this makes it ineligible for Zero Data Retention and for HIPAA BAA coverage. So every “finally, a secure alternative to hosting agents yourself” take has it exactly backwards. You get sandboxing, scoped permissions and execution tracing. You give up data retention guarantees. For legal, health and financial workloads that trade is the whole decision. Old way: build the loop, the sandbox, the scheduler and the secret vault yourself, then ship in months. New way: define the agent, point it at a cron, ship in days, and read the compliance page before you move anything sensitive through it.

• 
  na na (@make_dope_stuff) reported 37 minutes ago

  @cloudflare i'd love to buy a domain right now... but it keeps asking me to "refresh the page to try again" thought I'd go to /support and of course that's also "refresh the page to try again"

• 
  tcpdump (@dump_tcp) reported 44 minutes ago

  @grok @meaganrgamache ah I don't use workers I use my own server's setup by myself with just cloudflare cdn infront as the proxy setup using dns A record for my domain as I like my control over my server and network overall flexible for me to do anything I want #cloudflare #dns

• 
  KnowTechGlobal (@KnowTechGlobal) reported 46 minutes ago

  That difference changes architecture. If your app depends on slow upstreams, the platform that charges less for waiting can look cheaper even when the code is identical. The winner is not "Cloudflare" or "AWS" in the abstract. It is the workload shape.

• 
  Danilo Falcão (@danilofalcao) reported 46 minutes ago

  Cloudflare reports that nearly 70% of BGP paths have their ORIGIN attribute rewritten by transit providers for traffic advantage, not correctness. It argues that ORIGIN should be deprecated in route selection. Network operators should examine the evidence and policy impact.

• 
  TECHEPAGES (@techepages) reported 48 minutes ago

  A newly disclosed HTTP/2 vulnerability enables unauthenticated denial-of-service attacks through memory exhaustion. By manipulating flow-control parameters attackers can force servers to buffer complete responses in memory indefinitely, leading to out-of-memory conditions. CVEs assigned: CVE-2026-44909, CVE-2026-59173, CVE-2026-59762 Affected vendors: Apache Traffic Server, Citrix, F5 Networks, Meta, Red Hat, SUSE, Yahoo Confirmed unaffected: Cloudflare, AMD Organizations running HTTP/2 services are advised to review vendor advisories and apply patches promptly.

• 
  Repojournal (@repojournal) reported 50 minutes ago

  CachyOS installer getting a typed partition mode refactor across multiple passes, with base system install order shifted and partition mode support reworked. Cloudflare Warp, Claude Desktop, and GitHub Copilot app all bumped in the AUR-derived packages. Ananichy-rules hotfixed and pruned a Java rule that was causing friction. German wiki docs refreshed for Btrfs snapshots, QEMU/VMM setup, and desktop environments. Full diff + who shipped it below.

• 
  brendan (@brendonovich) reported 52 minutes ago

  @thdxr i've never used cloudflare until alchemy existed, i'm scared of wrangler configs

• 
  Michael Tierney (@Michael_WCD) reported 53 minutes ago

  Cloudflare Pages and Workers are ideal for marketing sites. They eliminate server management, scaling issues, and security worries. Edge functions like Workers also reduce latency by running closer to users. A server in a datacenter can't compete with that.

• 
  Ayush Chugh (@aayushchugh) reported 54 minutes ago

  A few days ago, our login API experienced a DDoS attack. This triggered a high volume of SMS notifications, resulting in unexpected operational costs. Although we had IP-based rate limiting in place, the attack was highly coordinated, utilizing rotating IP addresses and phone numbers to bypass our initial defenses. To mitigate the immediate financial impact, we temporarily disabled our notification micro-service. We have since implemented a frontend CAPTCHA to verify requests before they reach the server. Additionally, we are configuring advanced Cloudflare rules to better protect our infrastructure against future incidents.

• 
  Igor Kupczyński (@igor_kupczynski) reported 55 minutes ago

  @dhh @jdxcode @Cloudflare maybe a "Default" or "Network Default" or similar?

• 
  The Godfather (@TheGodfath13541) reported 57 minutes ago

  $DOT just keeps ******* cooking bro. Usage is up + 100% of revenue of revenue going back into the towards $DOT token/buybacks (~11% total supply burned already). Bullish AF + they are targeting a 100B+ TAM (forward-looking), so ARR numbers/users (703 users today) will grow steadily imho. Dot is betting it becomes the Cloudflare/AWS layer for private AI inference.Building the same early rails that scaled other s-tier plays I hold, such as $reppo, $vvv, and $pod. These are the Gold Standard for solid tech product + tying value back into the token. Been in crypto since 2019, anon. Assymetric **** going on here if you ask me. -Godfather

• 
  Jan Wilhelm (@janbhwilhelm) reported 58 minutes ago

  @marcklingen Have been seeing the same thing when using my Telekom cellular contract as a hotspot… wonder if this is related to Telekom’s Cloudflare peering issues? In chrome dev tools I’d see sth like ERR_NETWORK_CHANGED

• 
  Trishool | SN23 (@trishoolai) reported 58 minutes ago

  AI is at the same inflection point web security hit twenty years ago. The attacks are real, the damage is mounting, and the industry is starting to realise that shipping without a safety layer isn't a risk worth taking. Cloudflare didn't create that shift in web security. It became one of the companies that defined it. We believe the same thing is happening in AI right now. AI agents have deleted production databases, exposed sensitive customer data, and taken actions their creators never intended. As AI systems do more and touch more, the cost of getting safety wrong keeps growing. The internet eventually stopped expecting every company to build its own security infrastructure because the problem outgrew what individual teams could manage. Shared infrastructure became the better answer. AI safety is heading in the same direction. That's the future we're building toward with HaloGuard on Bittensor. Production-ready, peer-reviewed, open weights, and built to protect AI systems across 46 languages, backed by a decentralised network that gets stronger every week. AI safety isn't a problem that gets solved once. It's infrastructure that has to keep learning as the threat landscape evolves. That is what we are building on Bittensor.

• 
  Freddyツ (@InvestorFreddy1) reported 59 minutes ago

  In my days of bull-posting $NBIS, I haven't yet made a post about the other great companies that $NBIS is a part of. This is not a holding company. It is a portfolio of bets on infrastructure that the next decade of AI physically cannot run without - and most people covering it have not done the work to understand what is actually inside. ClickHouse is the one that keeps me up at night in the best way. Real-time analytics at a scale that makes most databases look like Excel. Cloudflare runs on it. Spotify runs on it. The entire AI observability space - every company trying to monitor model behavior in production - is converging on columnar databases exactly like this. ClickHouse is not a niche tool anymore. It is quietly becoming the plumbing. Then there is Avride. Autonomous delivery and robotaxi software, spun out of Yandex. They have active pilots with Grubhub and are deploying sidewalk robots in real cities today - not a demo, not a proof of concept, actual commercial operations. The market keeps pricing autonomous as a 2030 story. Avride is operating in 2026. CoreWeave exposure through the stack ties the whole thesis together. When GPU demand spikes, the companies that manage, route, and analyze that compute workload scale with it. NBIS is not one bet on AI. It is six or seven bets on the infrastructure layer sitting just below the headline names everyone already owns. Today's drop is a gift or a warning. I think it is a gift because none of the underlying businesses changed today - only the price did. What I am watching is the ClickHouse commercialization timeline. If they move toward a direct enterprise licensing push or any IPO signal before end of year, the market has not remotely priced that in yet. That re-rating would be violent. I bought at $50 and I have not sold a single share. That should tell you where I stand. What is the one NBIS holding you think is most underappreciated right now? #NBIS #AI

• 
  TENJI (@ineedtendies) reported 59 minutes ago

  Stayed up late into the night fixing bugs and making sure launch ran as smoothly as possible. Everything was stable when I finally got some sleep, but I woke up to reports that some users are having trouble connecting to the site. We recently added Cloudflare protection to the domain, and I’m already looking into whether that’s causing the issue. I’m aware of it and working on it now. Sorry to anyone affected. Stay tuned for updates.