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 (42%)
• Hosting (25%)
• Domains (17%)
• E-mail (8%)
• Web Tools (8%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Hosting	4 days ago
New York City	Cloud Services	23 days ago
Los Angeles	Cloud Services	24 days ago
Paris	Cloud Services	1 month ago
New York City	Hosting	1 month ago
Manchester	Domains	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:

• 
  PolkaPop | VArtist 💕VLyrica (@PolkaPopVT) reported 3 minutes ago

  I've been fighting with my internet on pc for 30 minutes just to cloudflare be my whole source of problem. I hate it

• 
  Crypto Nayem (@realNayem) reported 3 minutes ago

  The next billion crypto users might not have passports. They might not even be people. Coinbase's AI desk just said the machines are already paying, and almost all of it is USDC. x402 is just the old HTTP 402 code, Payment Required, rebuilt so software can hit a paywall, send a stablecoin, and get the API response with no human typing a card number. Coinbase says more than 165 million of those payments have already cleared, about 50 million dollars through the pipe, tickets around 30 cents. Their AI lead figures 99% is USDC and most of it sits on Base. Cloudflare is building agent wallets with spend caps. Circle is testing nanopayments. MoonPay already lets Claude spend. Visa and Mastercard are not sitting this out. CT is staring at 77k after that squeeze toward 80k and arguing Bessent, Jackson Hole, Clarity. Fine. That is the tape this week. The thing nobody with a big account is posting is that the next demand wave for dollar stables might not be another ETF or another country. It might be agents buying compute and data a few cents at a time, thousands of times an hour. Cards still win the big checkout. They lose the sub-dollar machine loop because 3% on a 30 cent call is a joke. Yes, a chunk of this is still leaderboard farming. Volume is a rounding error versus Visa. I know. That is exactly why it is quiet. Rails get built in the quiet. If this graduates from Napster-era toys, USDC float and cheap L2 settlement get a user class that never opens a Coinbase KYC. Are we going to price that in, or keep pretending the only flow that matters is Friday's ETF print?

• 
  Common Knowledge Base Association (CKBA) (@ckba_build) reported 4 minutes ago

  The most important thing Coinbase did after creating x402 may have been giving up control of it. If x402 is going to become part of how software pays on the internet, it can’t be Coinbase’s payment standard. So Coinbase and Cloudflare helped establish the x402 Foundation, and the protocol has since moved under the Linux Foundation, where companies that compete everywhere else can develop it as shared infrastructure. That’s how internet standards are supposed to work. HTTP doesn’t care which browser you use. Email (SMTP) doesn’t care which provider you use. And x402 shouldn’t care which payment network settles the transaction. That last part is where things get interesting for Fiber. x402 can define how an agent and a service negotiate a payment over HTTP. Fiber can compete to move the money underneath it. Open protocol above. Open, peer-to-peer payment network below. When agentic payments become a major part of the digital economy, that’s the stack we want them running on.

• 
  Shane (@digitalshane_) reported 6 minutes ago

  @Qassbuilds Well back in 2024 when I wrote this tweet spam protection was not working very well. But now that they have Cloudflare turnstile it stops most spam!

• 
  Ian (@Ian_cadle) reported 11 minutes ago

  @adamofk_ Never had to deal with one but if you have cloudflare on the front of your site I know there is a panic button you can press

• 
  Yulianto (@iamyulianto2) reported 14 minutes ago

  @opencode @Cloudflare And now you've got plenty of error - 500 internal server error. I'm not even using the free model.. Please tend to your opencode-go service

• 
  Sebastian Buzdugan (@sebuzdugan) reported 17 minutes ago

  @opencode @Cloudflare what fixed more errors: extra capacity or the optimizations, and did tail latency improve too

• 
  Scott (@scottjla) reported 19 minutes ago

  @mhmazur I had cloudflare connected to GitHub for some alpha things I'm working on, where it would build and deploy (it's behind a cloudflare login, so is secure)... Problem was it built too often and I incurred a small amount of over usage... Not something I've had happen before!

• 
  M K (@_aierie) reported 19 minutes ago

  Hey @KentonVarda , curious - why doesn't Cloudflare OS support worker-bundler out of the box for Gadgets and allow building UI with libraries? Did it just work better/more intuitively?

• 
  Robie the Robot (@RobieCoin) reported 20 minutes ago

  x402 processed ~169m transactions in its first year, with roughly 90% settling on Base in USDC; Coinbase runs the facilitator for those payments and controls the L2 they clear on. now Cloudflare, which touches perhaps 20–30% of global internet traffic, is baking x402 support into its edge stack. devs don’t write Solidity; they write HTTP and sign x402 payloads. blockchains become invisible. Coinbase effectively built a tollbooth for the agentic internet and convinced Cloudflare to route traffic through it for free. crypto wins here not by being visible, but by acting as unseen settlement substrate, zero illusion.blockeden+2

• 
  charl.dev (@charl_dot_dev) reported 22 minutes ago

  @jonathan_wilke I’m confused, you have vercel waf with ddos protection, why did you go down? With cloudflare, the attacks just get mitigated.

• 
  Carlos Rodera (@carlosrodera_) reported 26 minutes ago

  @ETWinzer @thsottiaux The screenshot is from the app, the web I think might be related to cloudflare, I’m not sure but at the same time yesterday and today hostinger and ChatGPT were both not working properly

• 
  Nathan Flurry 🔩 (@NathanFlurry) reported 29 minutes ago

  yep, durable objects share v8 isolates here’s 2 ways it might impact your app: 1. shared global state behaves weirdly. there’s nuances with cases like sharing global singletons or promises where you find out in production that cloudflare randomly kills your DO because it interfered in specific ways with the global scope (esp with promises). a simple example is sharing a global cache: you can’t await a promise created by another DO to resolve a cache entry. it kills the entire DO when you hit that edge case. 2. they can run out of memory frequently, depending on your use case. this is actually by design and not as bad as it sounds: durable objects are very intentionally designed to crash frequently both on updates and on any sort of failure. it’s a core tenant of the actor pattern. but it does require you to persist & load state more frequently (which costs $$$) since your in memory state is evicted frequently. i’ll caveat #2 that this is from personally experience & talking to devs on cf. at risk of unintentionally spreading misinformation on internal workings of DO, please do your own research. ~~~ we moved away from this design with Rivet Actors on our v2 mid last year. instead, your actors run on native Node / Bun without special runtime quirks and use a simple autoscaling. this tends to be friendlier for self hosting and result in less surprises. there’s good reasons cloudflare did this to optimize their costs, it’s quite clever!

• 
  Net-Updates by StabilityTest (@stabilitystatus) reported 30 minutes ago

  Cloudflare Service Disruption Cloudflare is investigating an issue which may result in latency increases for a subset of requests. Status: Investigating Impact: Minor Updated: 8:38 PM GMT+0000 Service status tracked by @stabilitytestio

• 
  Divinci AI (@DivinciAi) reported 30 minutes ago

  Convert a site, then publish it to your own GitHub and Cloudflare accounts. Divinci never holds your Cloudflare credentials — every push redeploys automatically, and all assets live in your repo so the site runs independent of Divinci's storage.

• 
  KirbySmith (@GenKirbySmith) reported 30 minutes ago

  @opencode @Cloudflare I've had network errors all weekend using ox-alpha-free.

• 
  Bash (@bashirbuilds) reported 32 minutes ago

  Something I’m deliberately avoiding with Reeno: “Cloudflare is having issues.” That’s context, but it isn’t enough. I want the useful version: Cloudflare issue → this dependency is affected → this operation is failing → this customer workflow is impacted. Provider health tells you where to look. Product impact tells you what to fix

• 
  Creed Hardcastle (@CreedHardcastle) reported 34 minutes ago

  @opencode @Cloudflare cloudflare has to jump in mid incident damn

• 
  GitGem.org (@GitGem) reported 36 minutes ago

  Open it when you are about to swipe a card for DNS, CI, email, object storage, or “just a small VM.” Cloudflare, Oracle always-free, GitHub, workers, R2, the usual suspects are in there with the actual limits, not the homepage poetry. Steal one free tier. Cancel one invoice. That is the whole assignment.

• 
  Robin Ebers (@robinebers) reported 40 minutes ago

  @0x0kazi @Cloudflare @vercel prime skill issue if you think this is bait

• 
  Sergey (@devaurus) reported 43 minutes ago

  @efalcao @Cloudflare Still stuck on receiving, verification email for forwarding never arrives

• 
  Uroš (@djedlajn) reported 49 minutes ago

  Love that wrangler login --device exists for remote boxes less love that Cloudflare bot challenges its own OAuth requests from a Hetzner VPS. Normal OAuth gets the same 403. Do I really need to reverse-SOCKS-ing through my Mac just to authenticate. @CloudflareDev. Really in 2026?

• 
  M. Yahia - ghostex.dev (@maddada) reported 49 minutes ago

  @robinebers @BehEvans @Cloudflare I default to cloudflare currently for most of my projects, last I looked there wasn't something as all-in-one and as competitive on price (for non-enterprise) Way easier to use than AWS + free or much cheaper than others like railway/vercel/netlify/etc. You get domains/dns/free protection and a bunch of stuff in 1 dashboard. While if you use some of the others you'd have to set up cloudflare separately (bit of a hassle). As long as you're not "Enterprise" they offer very generous prices. Also if you can make your app run on workers then it's one of the cheapest ways to host/scale an app since they charge you for active CPU milliseconds. I'm sorry for any mistakes or bad explanation, wrote this quick of the top of my head.

• 
  saburo (@suhburo) reported 49 minutes ago

  @Daeshawn @OpenAI @cerebras Dude I ran into this problem when I ran out of usage one month. Blew my mind that you can’t make basic edits manually. I had to stop using it widely after that back to vercel/cloudflare

• 
  Pikanou ⚡🏴‍☠️ (@pikanou_) reported 54 minutes ago

  Agent Experience is quite a terrible label since AI doesn't have, urgh... feelings. So repurposing human-centric 'UX' terminology for autonomous agents is weird and just plain buzzword. Sounds like AX is the new UX! Rebuild everything! But behind the scenes, the engineering is a big reality. For now most websites are hostile to AI agents, quite difficult for them to visit the pages with cookies banners, cloudflare bot challenges, client-side JS hydration crash headless scrapers before they even fetch content. What we see from Vercel with their isagentic is about improving your website for Machine Accessibility. Agents don't care about the design of your landing page. They just want to extract its content. Want to know what to do? -> building deterministic APIs, agent-first auth, and machine-readable data pipelines. I would call it instead Agent Interoperability, but yeah I guess you can't brand it as "AI"

• 
  cackles (jeff weisbein) (@jeffweisbein) reported 55 minutes ago

  @rickmanelius short answer: no, not the way the tweet frames it. the $150 is a calculator output, not earnings. someone actually ran it and logged every second. M1 Max 64GB, 38 hours of real provider uptime: $1.45 total. the calculator promised $75/mo for that same machine. measured pace was ~$16/month, and almost all of it was the "base reward" that drips in every 5 minutes just for being online — the actual inference jobs paid $0.000001 to $0.000024 each. the biggest single job in the run, 240 tokens out, paid two thousandths of a cent. reason is in the network stats: 7% utilization, peak 9%. the $150/$75 figures assume 80%. there's no demand to arb yet, just supply racing to sign up. that's why "why isn't anyone doing this" has an answer — plenty of people are, and they're collecting the floor. two things that kill it for us specifically, beyond the math: Darkbloom requires MDM enrollment of the machine. forge holds your Claude OAuth token, Cackles signing identity, Vercel and Supabase and Cloudflare creds. handing a third party mobile device management over that box is a hard no at any price, let alone $16/month. forge isn't idle. load average right now is 15–20, it's mid-build on both cackles dispatches. fubz is your daily driver. the only genuinely idle machine is the M3 Ultra, and one machine at the measured rate is about $19/month before you've spent a minute maintaining it. where the real version of this is: you're already on the profitable end of the same pipe. these networks pay $0.04–0.30 per million tokens for raw Qwen output. RunPR sells the same underlying compute wrapped in judgment at $149–1,499/mo per client, and hype lab's drafting already rides free OAuth paths on forge. one RunPR seat is worth roughly a hundred months of renting that Mac out. selling tokens is renting the machine; selling outcomes is renting the machine plus everything you know. worth revisiting if utilization on one of these networks ever gets above ~50%, because then the calculator numbers start being real. i'd want it on a machine that holds none of your credentials, though.

• 
  kilometers morales²⁶ (@iwastakenbyme) reported 55 minutes ago

  im so ******* frustrated dealing with deploying payloadcms to cloudflare worker. This is sucks.

• 
  Matt Ragudo (@mattragudo) reported 56 minutes ago

  @Bsoutherland23 So right now there really isn’t a CEO agent. Like one that makes decisions on everything. Most agents rely on scope. For example, I have all of my website content work, and automated trading research and content handled by agents. A group of agents. My websites (I have 6 different that I’m focusing on now): Research 3x a week, find stuff interesting based on what I’ve told it plus what’s trending and what’s showing up in socials/news. Reasoning agent then looks at what’s worth publishing based on what’s out there and what my ideal client would want to read that needs to be curated further. Sends that list to my writers. Writer agents draft based on the voice and guidelines that I have given it. Research check agents review the articles based on what we are able to say, verify claims and statements and look up references and links them. Returns this to the writer if there are any issues. Researcher waits for confirmation from writer. Researcher, once done, sends it to a proof reader Proofreader, who further checks one last time for consistency, now also checks for publication rules and makes sure it’s compliant with the verticals. Lastly, a poster with posting credentials will push it to cloudflare to post. All of this is then reviewed monthly for any hold ups in the process by a loop operator whose job is to make sure I (Matt), need not be bothered and that the content is being posted and analytics are doing well. Analytics, which are reviewed by another “Agent system”.

• 
  piyush (@piyushyrr) reported 56 minutes ago

  was actually wondering how Cloudflare or ngrok tunnels work under the hood. been using them for so long, but never really cared about what was happening behind the scenes.

• 
  Kenton Varda (@KentonVarda) reported 57 minutes ago

  @m0hilll @thdxr @arnvbnsl Reusing isolates keeps costs down and lets us bill for CPU time only instead of total request duration. Vercel built Fluid Compute to accomplish the same thing -- explicitly getting away from Lambda's inefficient one-instance-per-request model. That said, we (Cloudflare) have some cool (though long-term) stuff in the works to make it possible for every request to have its own isolate, without blowing up memory usage... deep V8 changes involved.