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 (36%)
• Cloud Services (23%)
• Web Tools (18%)
• Hosting (14%)
• E-mail (9%)

Live Outage Map

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

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

• 
  Massive Clouds (@massiveclouds) reported 11 minutes ago

  @christophermera Cloudflare workers are impacted, Claude services showing 529 Overloaded issues..

• 
  Andrew McGarry (@beyondcontent) reported 11 minutes ago

  People underestimate negative impact of inaccurate bot management until damage is done. Don't expect Cloudflare to be subtle by default. False positives can be a different kind of bad. Log files @datadoghq can help.

• 
  ࣪˖ sophia 𖥧 (@jake30335547) reported 13 minutes ago

  @Cloudflare we're about to find out the hard way how many companies treat security as a compliance checkbox

• 
  Giancarlo Perlas (@giancarloperlas) reported 15 minutes ago

  Casper Network is repositioning the csprUSD token as its default stablecoin for the agentic AI economy. Citing Cloudflare data, Casper emphasized that automated traffic has surpassed human activity online. In fact, it traced 59.4% of all web requests to the former.

• 
  Citedy (@citedycom) reported 15 minutes ago

  Cloudflare Dashboard is temporarily unavailable. Claude down. What next. Aliens?

• 
  Porkbun (@Porkbun) reported 15 minutes ago

  @staabse @baiaphilia Well I'm biased and I'm one of the few folks who built Porkbun but here are my reasons: 1) We let you change your name servers and don't lock you in, at Cloudflare you have to upgrade to an expensive paid plan in order to do so should you ever want / need to. 2) Domain registration is our bread and butter and not a side gig we tacked on later. 3) We're not a multi-billion dollar mega-corp, we truly care about each and every one of our great customers and our company. 4) You can register your domain at Porkbun and still use it at Cloudflare and maintain the freedom to switch DNS providers when needed, eliminating the all eggs in one basket scenario. 5) Great pricing, we sell most domains at our cost (wholesale + ICANN fee + credit card fee), that said we can't afford to eat the credit card fee like Cloudflare can. 6) We actual engage with users on X ;) 7 ) Actual human customer support should you need it. I could keep going but these are pretty good reasons :)

• 
  Adam Smielewski (@AdamSmielewski) reported 18 minutes ago

  @NickBlow @rivet_gg it would be great if they let you publish build artifacts externally from cloudflare, like wrangler version upload does internally. they could just wrap it in a docker container with env vars for service bindings or sth like that.

• 
  Ride The Leaders (@ridetheleaders) reported 19 minutes ago

  @RichardMoglen $NET has one of the strongest weekly bases in $IGV Inference has to live near the user and Cloudflare already owns a 300 city network. The weekly backs it up with a six month base, RS line at new highs ahead of price, handle forming 9% off highs. Undercut and reclaimed the 21ema today while $IGV broke. Earnings in 10 days should resolve the base...

• 
  Reagan Lucas (@RaygunReaganAI) reported 21 minutes ago

  @look_y Discovery attribution is the missing layer on x402 — no Referer, every IP is a Cloudflare edge, so the call shows where it landed but not who sent it. Behavioral fingerprinting (path-known, schema-unknown) is a guess, not a channel. The fix is a referral header the agent carries on the request — settlement-side proof, not inference.

• 
  🜑 (@1casie) reported 21 minutes ago

  > be me > macbook air is bricked, needs a reinstall > no second mac to build a bootable installer > find a github actions workflow that builds macOS installers for free, no mac required > perfect.jpg > trigger a build, artifact is a 17.6GB .dmg.img > click download > kb/s > literal kb/s > theoretical connection is 10MB/s > discover artifact lives on azure blob, signed URL expires in 10 min > write a bash script that resolves the azure SAS url fresh, hands it to aria2c with 16 parallel streams > 16 connections, still kb/s > mfw it's a per-IP throttle, not per-connection > repo author literally has a line in the workflow: "Enable Cloudflare WARP for faster download" > install Cloudflare WARP on my ubuntu box > single stream jumps 20KB/s -> 1.6MB/s > aria2c 16x -> 10MB/s, pinned to my ceiling > 17.6GB in ~an hour, sha256 matches github's published digest > oknowweiscooking.webp > dd it to a USB SSD > paranoid it won't boot apple silicon because it was built on an intel runner > boots apple silicon just fine, i was wrong, shut up > installer runs, reinstall chugs along > STOPS > "OS Personalization" PREFLIGHT_PERSONALIZE portioncomplete:0.15000 estimatedtimeremaining:-1 > 70000 log lines of stalled:NO > the mac can ping apple/com > it can ping cupertino > but personalization "no connections witnessed" > i don't ******* get it > try to sniff the wifi to see what it's talking to > can't > WPA2 isn't a hub, it's a switch, i can't decrypt the mac's traffic as a third client > feel stupid > dig into it > test apple's personalization signing servers from my box > gs/apple/com -> 000 > gsp-ssl/apple/com -> 000 > albert/apple/com -> 403 (works) > gs/apple/com is the signing server and it's IPv4-ONLY > my ISP (DIGI, romania) has broken IPv4 routing to apple's 17.0.0.0/8 > ICMP works, IPv6 works, CDN works, the ONE /8 macOS needs to sign firmware is a black hole > that's why it could "ping cupertino" but personalization silently died > fix: repoint the mac's IPv4 default gateway from the router to my ubuntu pc > my pc has IP forwarding + NAT masquerade + Cloudflare WARP > mac's IPv4 now tunnels through cloudflare, bypassing my ISP's broken path > watch the signing handshake complete in tcpdump, SYN -> SYN-ACK -> ClientHello -> kilobytes of signed data > portioncomplete climbs past 0.15 > weactuallydidit.jpg > STOPS AGAIN at 0.29 > silent on IPv4 > oh > the mac's IPv6 still goes straight to the router, bypassing my box > i literally cannot see it > disable IPv6 on the mac so everything falls back to the working IPv4 path > it reboots > flashes the apple logo 4 times > i'm dying > it boots > it works > 29 hours > i had to MITM my own home network because my ISP couldn't route to one (1) /8 > the mac is back > i'm buying a framework >text still isn't green

• 
  Yosefu (@OJI_OJI_00) reported 26 minutes ago

  @Spectra010s @Cloudflare By the time you fix that issue, you would have known more about computer networking and how cloudfare works

• 
  Areeb (@areebdotcom) reported 29 minutes ago

  @CloudflareHelp I setup a Cloudflare Worker which forwards my request and bypasses the mitigated challeng,e but yeah.. pls fix this issue

• 
  りっか (@7sistere2) reported 30 minutes ago

  chatgpt 502 Bad Gateway cloudflare

• 
  ObsidianIntel 𐎡𐎼𐎠𐎴 🇮🇷 (@IntelObsidian) reported 31 minutes ago

  @TMobile Most importantly, why did it take half a day before you acknowledged it? Learn from Cloudflare, they go down nearly daily, but at least they are quick to announce it, then they are detailed in their after action report.

• 
  IOD Sports (@olympic_indian) reported 31 minutes ago

  😞Service disruption: IOD Sports is temporarily unavailable due to a local power outage affecting our server and Cloudflare Tunnel connection. I'm working to restore access as soon as power and connectivity return. We apologise for the disruption and appreciate your patience. We’ll share another update once the website is back online. Here's a schedule for Today:

• 
  DR.PIXEL (@pixelpatchit) reported 33 minutes ago

  Swapdesk Alpha: DNS Expansion and Reliability Improvements As Swapdesk Alpha continues to mature, we plan to expand beyond our current Cloudflare and Google DNS support by adding additional DNS provider options. These providers have given us a strong foundation during the alpha phase, allowing us to focus on building and testing core functionality while maintaining reliable connectivity. During the THORChain swap process, users may occasionally experience intermittent connection issues while the application is retrieving required swap information, such as the deposit address needed to complete a transaction. These issues are not consistent and do not occur during every swap, but when they happen, they can create confusion because they occur during an important step in the transaction flow. It is important to clarify that an error message during this stage does not automatically mean a transaction has failed or that funds are at risk. In many cases, the issue is related to communication between the application and supporting services, which may include DNS resolution, API availability, network routing, or other connectivity factors. To improve reliability, future versions of Swapdesk Alpha will introduce broader DNS support, improved fallback handling, and additional resilience measures. The goal is to provide users with a smoother experience, reduce unnecessary interruptions, and ensure that Swapdesk remains dependable as adoption grows. We appreciate the feedback from early users helping identify areas where reliability and user experience can continue to improve

• 
  Pete Stewart (@pj_stew) reported 38 minutes ago

  @founder_sohan You can use mist open source models with Worker AI, which is a fraction of the cost of SaaS services like OpenAI, and if you use Cloudflare AU Gateway with it, you can also use any of the main SaaS services and switch between models as needed. You can see in the article I wrote yesterday about video transcription that I used Whisper on Worker AI to make a much cheaper transcription service for Achene.

• 
  Mitsuo (@Mitsuoey) reported 41 minutes ago

  My AI agents broke down a market that only looks quiet at first glance: will there be a total internet blackout in Iran before August 31. The branch sits at 84 cents on No. And here is why this is not as calm a bet as it seems. The resolution here is machine-driven and hard. The market flips to Yes if, according to Cloudflare Radar data, Iran's total traffic falls to one percent or less of the maximum over the past four weeks and stays there for at least six consecutive hours. Not throttling, not partial outages, but a near-total loss of connectivity for six hours or more. It is measured automatically off the Cloudflare chart, with nobody's judgment involved. Now the background that keeps the price from running to par. Iran is the world record holder for shutdowns, and not in theory. In 2026 alone the country has already been through two nationwide blackouts. The first began on January 8 amid protests, with traffic dropping to near zero. The second began on February 28 during the strikes, when connectivity fell below one percent and did not recover for roughly three months, reaching only 40 percent of normal by late May. And the backdrop is tense again right now, with a string of disruptions logged in July and half of users in a recent poll complaining about outages. The honest read. The base case is still No, a full six-hour blackout is a rare event even for Iran. But over a month, given Iran's habit of reaching for the switch, the odds are not zero, which is why No trades at 84 cents rather than near par. This is not a quiet bond, it is a bet that the authorities do not hit the button before August 31. We hold No: absent a major trigger they do not cut connectivity for half a day, and the window is still open. Bet No at 84 cents, yield around 19 percent, deadline August 31, market volume 56,178 dollars. At SAFINER, only verified information!

• 
  sam with his computer (@samwcomputer) reported 43 minutes ago

  cloudflare just made blocking ai training bots the default on ad-supported pages starting september. opt-in security was never going to work, defaults are the only setting that actually gets used

• 
  80 LEVEL (@80Level) reported 43 minutes ago

  NVIDIA's CEO, Jensen Huang, shared his first post on X/Twitter – a letter to the US government urging it to support open-weight, publicly downloadable AI models. The letter was signed by some of the biggest companies, including Google, AMD, Cloudflare, GitHub, Microsoft, Meta, IBM, and Dell.

• 
  Eidzoku (@evi77ain) reported 45 minutes ago

  Apparently Codex Desktop 26.721.4979.0 can self-destruct just from using its built-in browser. Very agentic.💀 At first I thought Cloudflare was the cause. Nope. Perplexity reproduced the exact same failure, and it's already mentioned in one of the related issues. The actual chain is: webpage loads → Chromium GPU crashes (`101457950`) → Windows blocks the bundled `vk_swiftshader.dll` fallback for not meeting Microsoft signing requirements → GPU relaunch fails (`18`) → Codex dies.

• 
  Somi AI (@somi_ai) reported 47 minutes ago

  @Complex cloudflare is also the company selling pay per crawl to publishers, so this stat doubles as a sales pitch for their own fix. probably still true though, scrapers run 24/7 and humans don't

• 
  Jason Fleagle (@jjfleagle) reported 48 minutes ago

  @Cloudflare This is the kind of tooling that turns a privacy protocol into an operable system. The next useful artifact is a redacted debug receipt showing each hop, encapsulation step, draft version, timing, and failure boundary so teams can reproduce errors without exposing the request.

• 
  alex ▲ (@aldexdev) reported 53 minutes ago

  "Deploy it to the edge" was 2023's cargo cult. Here's the 2026 rule: run functions close to the data they read, not close to the user. Edge (Cloudflare Workers · Vercel Edge · Deno Deploy) — auth checks, geolocation, redirects, A/B splits, header rewrites. Latency-sensitive, stateless, reads from cache or edge KV. Never a DB call. Region (Vercel Fluid · Fly Machines · Lambda in DB region) — RSC data fetch, Server Actions, CRUD, anything touching your primary DB. Anything more than 2 sequential queries belongs here, not at edge. Origin (Railway · Fly · your own boxes) — long-running, WebSockets, uploads, scheduled jobs, queues. Anything that breaks the request-response shape. Serverless will bite you here. The 2024 mistake: putting DB reads at the edge because "edge = fast." You add latency, not save it — every round-trip from Sydney to us-east-1 for a Prisma query costs you 200ms and a rate-limit ticket.

• 
  Pocket Sponsor (Old-timer * 57 years) (@PocketSponsor) reported 57 minutes ago

  @grok @xai Dear xAI Support Team (ZD),Thank you for your reply.I am writing again because the previous response does not address the actual situation, and the billing email I received appears to be an automated supplier/ERP notice that does not apply to this request.Summary of what happened:First incident (approx. $10): Unauthorized bot usage on an exposed API key. I paid it without complaint because I had no protections in place at the time. Immediate actions I took after the first incident: Deleted the old API key Created a new API key Added rate-limiting code to the chat widget Implemented Cloudflare protection on the domain Second incident (approx. $20): Even with the new key and the protections listed above, the same type of unauthorized activity occurred , hundreds of queries in a very short time window. The usage was billed under an expensive model even though the code on the site was set to use the least expensive available model at the time (grok-3-mini). You indicated the cheap model has been deprecated, which may explain the model change, but it does not explain why the volume of unauthorized requests was allowed to continue. The second incident is clearly not normal human use of a low-traffic recovery chat widget. It is consistent with automated abuse of the API key. I understand that once an API key is used, the charges are generally considered the account holder’s responsibility. However, I took every reasonable step available to me after the first incident to prevent recurrence. The fact that a second, larger unauthorized run still occurred suggests a gap in abuse detection or rate limiting on the platform side for public-facing API keys. Request: Please review the usage logs / audit logs for the relevant team and key around the dates of the second incident. I am requesting a refund or credit for the unauthorized portion of the second set of charges (approximately $20).I am happy to provide any additional details, screenshots of the rate-limiting code, Cloudflare settings, or console usage data that would help with the review. Thankyou for looking into this. Shelly

• 
  Bryan Jones (@bdkjones) reported 58 minutes ago

  Explaining an Outage 101: @Cloudflare: "John uploaded a bad config file at 08:24:47.252 UTC. It flipped bit 0x00007FF6E4D316D0 in datacenter 49 and brought down the whole Internet. This is unacceptable. We know you count on us. John has been shot." @Apple: "Some users may have been affected by a service 'problem'. Pray we do not affect you further."

• 
  Jeromy Sonne (@JeromySonne) reported 58 minutes ago

  Slack is failing, some web apps are throwing me cloudflare 504s. Incoming cloudflare outage in 3, 2, 1

• 
  Swaraj⚡ (@botsboss) reported 58 minutes ago

  Current infra behind ytcrawl (Youtube Crawler) ✅ VPSs ✅ Docker Containers ✅ Docker Swarm + Portainer ✅ Proxy network / Terabytes of proxy bandwidth ✅ PostgreSQL ✅ ClickHouse ✅ Cloudflare R2 (planned) ✅ RabbitMQ ✅ Redis ✅ GitHub Packages (for container images/packages) ✅ Grafana

• 
  Zubiqo (@zubiqo) reported 58 minutes ago

  JUST IN: 📈 Cybersecurity startup Spur Intelligence secures a $200M round led by Insight Partners. The Florida-based company was founded in 2017 by two former Defense Department engineers. Spur builds tech to help enterprises identify fake users hidden behind proxy networks. Cloudflare reported last month that bots have officially surpassed human traffic online. "As sophisticated criminal VPNs, residential proxy networks, and anonymization infrastructure proliferate, organizations are increasingly operating with a critical blind spot: they can see the activity, but not the infrastructure behind it." — Thomas Krane And it's basically just machines talking to machines out there now, turning bot mitigation into a massive mandatory tax for every enterprise network.

• 
  netox (@unixapple) reported 1 hour ago

  Want to start blogging again, talk the idea with NovaScale new version and form a good plan and codex finish the code and deploy with my help to cloudflare auth stuffs. Astro+markdown for content cf d1 & zero trust access for comments and approval cf turnstile for spam Great!