Cloudflare 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:

• 
  indigo369 (@1ndigo369) reported 3 minutes ago

  @TruthFairy131 Cloudflare is best choice exactly for this kind of attacks, put the origin behind its network, use WAF, caching, MFA + rate limiting + bot controls, and prevent direct Internet access to the origin.

• 
  Akash (@imaks_dev) reported 3 minutes ago

  @a_shimanski @Cloudflare We use our nginx behind CF without Agro performance is poor, it takes longer route

• 
  fire_bol (@firebol226860) reported 3 minutes ago

  @jdanielenj @signalapp @Cloudflare If Signal is open source, prove through your own testing that the public source code actually matches the released Android APK and iOS build. It’s open source”alone doesn’t prove the binaries are identical or contain nothing additional. Show me your evidence.

• 
  VJay (@nceevij) reported 6 minutes ago

  The Real Story Behind "Humans Will Be a Rounding Error on the Internet" This week, a Cloudflare forecast went viral after Elon Musk amplified it on X: within five years, AI agent traffic could exceed human traffic by a factor of 1,000. Cloudflare's CFO, Thomas Seifert, put it bluntly on the company's Q2 earnings call "humans will be a rounding error on the internet." Musk's response: "AI agentic Internet traffic will obviously VASTLY exceed human usage. Not a close call at all. Cloudflare's forecast is accurate." The headline number is dramatic, and it's not hype dressed up as data. Cloudflare's own network already crossed a milestone in May 2026 machine-generated traffic passed human traffic for the first time, two years earlier than the company had originally projected. By Q2 2026, non-human requests made up more than 57% of total traffic on Cloudflare's infrastructure. But the stat that should actually get your attention is a different one: AI crawlers request content anywhere from 100 to 10,000 times for every human visitor they send back to a site. That ratio is the crux of a problem nobody has solved yet. The question underneath the number Investor Michael Burry, no stranger to skepticism about the AI buildout, put it plainly in response to Musk's post: "we still do not know who will pay for AI agents to socialize." It's a fair challenge. The web has run on two business models for three decades advertising and subscriptions and both depend on a human being on the other end of the connection: someone who sees an ad, or someone who decides a subscription is worth renewing. AI agents do neither. They read, extract, and move on. As machine traffic scales toward Cloudflare's 1,000x scenario, publishers, API providers, and data owners are left absorbing infrastructure costs with no native way to charge the traffic actually driving them. Micropayments were the obvious fix for decades and never worked, because traditional payment rails cost more to process a transaction than a fraction-of-a-cent charge is worth, and settlement takes days. That's the exact gap stablecoins are built to close. Cloudflare's answer: x402 and agent wallets Cloudflare's response, built with Coinbase, is a protocol called x402. It revives HTTP status code 402 "Payment Required," a part of the original web spec that's sat unused for 30 years and uses it to attach a stablecoin payment directly to a web request. A request settles in under a second, for a fraction of a cent, in USDC on Coinbase's Base network, with no chargebacks and no account required. The payment itself is the credential. Cloudflare has since shipped two products on top of it: a Monetization Gateway (waitlisted since July 2026) that lets any site or API charge per request in stablecoins, and, as of August 4, 2026, Cloudflare Wallets virtual, on-chain wallets that let an AI agent hold and spend USDC autonomously, within spending limits its human owner sets. In effect, an agent can now pay for the data, compute, or API access it needs without a subscription or a shared API key. Circle co-founder Jeremy Allaire has already called the gateway "a big win for data providers and publishers," and x402 has logged roughly 160 million transactions since launch. Whether this specific protocol becomes the default rail for machine payments or one of several competing standards, alongside things like Bitcoin's Lightning-based L402 is still an open question. Regulators haven't settled how autonomous agent payments fit existing financial rules either. Why this matters more than the traffic number Strip away the headline stat, and what's forming here is a genuine token economy not a speculative one, but a utility-driven one: machines paying machines, in stablecoins, for access to data and compute, at a scale and speed no human payment system was built to handle. If Cloudflare and Musk are right about the trajectory of agentic traffic, machine-to-machine payments may become one of the most consequential and durable use cases stablecoins have found yet. The traffic multiple will keep making headlines. The payment layer being built underneath it is the part worth actually tracking.

• 
  John Curtis (@jcurtis) reported 8 minutes ago

  @tharshan_09 @rauchg This turned out to be a long answer...but I like to share! The simplest way to describe it is as an overbuilt local replacement for Context7. I tend to keep technical documentation for all the major libraries I use, from TanStack to third-party services like Browserbase. As of today, it contains 89 top-level directories, one of which is "cloudflare" - inside is about 3K md files. I like letting my agents access the latest, grounded context and ensuring they are getting the exact information they need, rather than relying on random search results or Context7, where the interpretation may not always be what I/human wanted. Historically, I would paste a local path to the agent and say, “Here are the specifics on XYZ, for or re: Durable Objects.” Now, I can simply tell it to use the `aidocs` CLI, and in under 80 ms, it returns both vector and/or semantic (bm25) results. vectors are using @VoyageAI for the corpus of content, but the local queries use their nano model self hosted. I have sqlite for the FTS5/BM25 lexical ranking side and lancedb for the vector side. query time free, ingest costs if the doc changed but so far its been well worth it. this scriptC came up for me since there was this startup wall I couldnt get through without a drastic change. turns out compiling to C will do that. But the background ....I have been letting agents run at night on specific sides of the system (user side like - lexical query, vector query, ranking, loading directory details etc..maint side like loading and audits) and each night i have a set of benchmarks on that specific part of the system and i set a /goal to try various ideas to see what can move the needle by more than 10% so minutes in some cases have become seconds and s has become ms. No rush just a constant race to be faster with the same bar of output quality. For example comparing the xxhashes between sqlite and lance was a bit slow, so we evaluated a bunch of options and ended with a Merkle tree which makes row integrity auditing 17x faster and 11x faster for mismatch finding. is it noticeable? not sure, since the primary user is the agent, but last night this merkle tree moved a p95 from 38.49ms to 3.2ms, or the time to rebuild the index from 655ms to just 43.5ms. Im well in to the diminishing returns area but its still fun!

• 
  Robert Samuel White (@rswfire) reported 8 minutes ago

  @a_shimanski @Cloudflare You've got me curious now. I use Hetzner and the s3 uploads feel so slow because the bucket is across the ocean!

• 
  Nat Miletic (@natmiletic) reported 13 minutes ago

  @remkusdevries @ElitzaVasileva @Porkbun Yes they also sell them "at cost" but sometimes have sales. But I was wrong, I think that their regular price is maybe a tad higher than Cloudflare (it's been a while since I used CF)?! Take a look below. The biggest issue preventing us from using Cloudflare was that you can't change the default nameservers. That was a showstopper.

• 
  Risto Anton (@blogtheristo) reported 15 minutes ago

  @davidfowl Customer Demo Environments ; each has its own Cloudflare Zone / subdomain, isolated Worker binding, and KV namespace for config.

• 
  Officially Retired Owl Dope Capone (@Owl_Dope_Capone) reported 15 minutes ago

  @Cloudflare You are the cyber threat. Getting randomly blocked from sites non-stop for the last few weeks. Sometimes a refresh works, sometimes not. Sometimes comment sections load, sometimes not. Constant redirects to international sites. Your company sucks.

• 
  Vincenzo (@DaGiftedmind) reported 18 minutes ago

  This CloudFlare security verification thingy has started making browsing the Internet difficult for me I can barely access journal sites these days because the verification just never works. It just keeps rolling and rolling Is this an Internet speed thing or what?

• 
  Harsh (@harsh_biz) reported 18 minutes ago

  The deliverability meta going into Q4 2026 is different from what worked in Q1. If you're still building infrastructure the way you did at the start of the year, you're going to feel it next quarter. SURBL made a lot of noise this quarter. Cold email inboxes got flagged in batches, everyone scrambled, and the enforcement has already lost most of its teeth. But the fixes are still the right build. Not because SURBL is going to catch you. Because when you build this way, there's almost nothing left for any ESP to pattern-match against. SURBL won't be relevant soon from what I think. You're no longer defending against a specific list. You're removing the mechanical fingerprint that makes automated detection possible at all. Practically: Keep domains to 20 per registrar account, 50 at the absolute ceiling, spread across multiple accounts. Once your domains aren't clustered, there's no cluster to flag. Stop naming them [Company]aa, [Company]ab, [Company]ac. Branch out entirely instead. If the brand is Milbridge Capital, use Milbridge Advisory, MBCapital, MilbridgeGroup, or drop the brand pattern altogether and use unrelated professional-sounding names. Older domains with genuinely varied names get listed far less often, and that holds regardless of which blacklist happens to be active. Placement tests are dead. They were reliable in early 2025. They aren't now. You can score 100% inbox placement on a test and pull a 0% reply rate on the live campaign the next day. Replies are the only trustworthy signal left. Build your monitoring around reply rate at the sender-email level, excluding auto-replies, and pull inboxes when they drop below threshold. Masking beats redirects, and both beat nothing. Redirects have visibly hurt deliverability this year. Dead domains hurt too, because prospects check the domain and expect a real site. Build masking through Cloudflare Workers rather than paying a markup for it. One free Cloudflare account holds around 80 domains. Your lead source is now a deliverability factor. Cheapest leads reply the least on average, and low reply rates suppress sender reputation. That's not a relevance problem, it's an infrastructure problem. When a campaign starts dying, diagnose before you rebuild. If two or three campaigns trend down at once, it's the copy. Rotate it. If you rotate the copy well and nothing recovers, it's the inboxes. Fix the wrong one and you burn another month.

• 
  Joshua Abrams (@unlimitedingenu) reported 19 minutes ago

  @a_shimanski @Cloudflare Ya idk. It sounds like you found a healthy or safer way to use their services. But watching them go down. Replace half their engineers and code base with AI, and seeing nightmare stories where they get billed for $100k+ cause someone added a loop somewhere just doesn’t seem cool

• 
  Maddie D. Reese (@maddiedreese) reported 22 minutes ago

  Had to do a bit of a workaround for this! Regular sign in for the app brings up a Cloudflare “are you human?” check which hung for both me and Grok Bot because Grok Bot’s computer is a data center VM. So, I suggested downloading the Codex CLI instead and using device auth, which worked! Transferred my credentials to the app and I was able to sign in.

• 
  Pete North (@FUDdaily) reported 25 minutes ago

  @CynicalBrit2023 A few people get that. I have no idea how to fix it. I'm told its to do with VPNs or Cloudflare but I just don't dare tinker with that stuff.

• 
  Michael Tanguma (@MTanguma) reported 27 minutes ago

  AI is breaking the free internet. When a human visits a website, free access is cheap enough to subsidize. When a bot can hit it a million times for almost nothing, it isn’t. That changes the economics completely. Micropayments were part of the internet’s original vision. They never shipped, so we built the web around ads, surveillance, subscriptions, and platforms instead. AI may finally force the correction. Charge a human a few sats and they barely notice. Charge a bot a few sats every request and suddenly spam, scraping, and abuse have a real marginal cost. Cloudflare is moving this direction. Lightning makes it possible. Others will follow. The internet is finally getting a native payment layer because AI is making free access economically impossible. Full Final Settlement rip below