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:

• 
  guestzeno (@zenohosting) reported 3 minutes ago

  @adarshsolanki I’m gonna buy a domain for it Just gotta think through the privacy a bit more I think cloudflare has a sign in button

• 
  Finance Spot (@financespotnews) reported 4 minutes ago

  Cloudflare $NET remains elevated after raising full-year revenue guidance on accelerating AI-related traffic and customer growth.

• 
  Trademaster Academy (@TMA_MarketIntel) reported 6 minutes ago

  Previous-day earnings impact $NET: Software leadership candidate Cloudflare delivered strong results and raised its full-year outlook, sending shares sharply higher after hours. This is especially important after the recent collapses in $APP, $DDOG and other expensive software names. Read-through: Positive for cloud infrastructure, cybersecurity and selective high-growth software. Trade map Gap support: 320 to 325 Stronger support: 305 to 312 Resistance: 335 to 340 Extension: 350 Action: Favor the first controlled pullback that preserves VWAP. Avoid chasing a vertical opening move. $ABNB: Consumer/travel strength Airbnb raised its full-year revenue outlook after reporting strong bookings and revenue. Shares are approximately 7% higher premarket. Read-through: Higher-income discretionary travel demand remains healthy despite the softer labor environment. Support: 160 to 164 Secondary support: 156 to 158 Resistance: 168 to 171 Extension: 175 $TEAM: Major software breakout Atlassian is roughly +30% premarket after beating revenue expectations, driven by strong cloud growth. This reinforces the idea that software is splitting between execution winners and valuation casualties, rather than undergoing blanket liquidation. Action: Do not chase a 30% gap. Watch whether TEAM and NET can hold VWAP to confirm software leadership. $TTD: Major ad-tech casualty The Trade Desk is down roughly 27% to 30% premarket following weaker-than-expected revenue and guidance. Market impact: Continues the severe earnings reset in high-multiple ad-tech. Potential sympathy pressure remains on digital advertising names. Trading read: Weak rebounds that fail VWAP remain fadeable.

• 
  Duyet (@_duyet) reported 7 minutes ago

  My @Cloudflare subscription automatically downgraded to Free after this month's billing successful, and I am not able to Upgrade it back. All pages on dashboard are blank, and I never got a response from support (Case: 02271079). Could not deploy as R2 Storage been disabled and all workers and DO reached its daily requests limit and outage. Can anyone help me to tag the right people for this? 🙏

• 
  Boards (@Boards86) reported 8 minutes ago

  Cloudflare has no spend caps/budgets. Main reason I've never migrated off the Free plan. Perhaps they don't want the small fish vibecoders like me. Seems shortsighted.

• 
   Q-Cap  (@qcapital2020) reported 10 minutes ago

  September 15th probably a date you wanna pencil down Cloudflare will force crawlers to distinguish between indexing content for Search and consuming it for AI Basically Google is losing leverage and the content creators will finally get paid For content owners like $RDDT, it could finally put a price tag on something AI companies have historically taken for free Time to pay up sucka

• 
  Celene is in Seattle! (@toasterlighting) reported 11 minutes ago

  @levelsio Yeah, this happened to me too. Annoyingly, meta's web-indexer gets classified as a Search Bot, so cloudflare lets it through a lot despite how rude it is

• 
  Matthew MacKinnon (@MatthewMac69462) reported 16 minutes ago

  @timo_rf One slight issue I have with Cloudflare is that computer-use agents can’t use it unless it’s the focused window on your computer. Not sure if aws is the same way or not.

• 
  Boyd (@0xBOYD) reported 19 minutes ago

  @zero_to_seed @luanguyen Stacked instances of a Cloudflare alert edge case, mistakes on our part, and really bad luck on timing. The alert existed but was set mid-cycle (by Cloudflare) and so didn’t take effect until this new billing cycle. The older alert we did have was scoped to workers only and wouldn’t have caught the Durable Object reads. Lastly we happened to hit the bug in our code at the exact start of a billing cycle so it went undetected about as long as theoretically possible. A whole billing cycle before we saw the invoice hit.

• 
  Mystisith (@Mystisith) reported 26 minutes ago

  @BrianRoemmele So can we get rid of the Cloudflare scourge yet? Because apart from slowing down everything & disabling sites I need every week, I'm not sure what else they are doing.

• 
  vu (@_vu) reported 34 minutes ago

  @jpschroeder I had the same issue. Cloudflare did not give a ****. Honestly **** their durable objects

• 
  NextGenLong (@dnw_stock) reported 34 minutes ago

  $net $app $meta ect... The agentic web has an identity layer now. It still doesn't have a business model. I think I know what it looks like. This week Cloudflare shipped Kitesurf, a browser built from scratch for AI agents — no Chromium, runs entirely in V8 isolates on Workers, 3-7x less CPU and memory. Impressive engineering. But read the limitations list and you'll notice what it *doesn't* solve: bot blocking. Sites that block automated traffic today will block Kitesurf tomorrow. Same egress IPs, same wall. That's not a Cloudflare problem. It's an incentive problem. I used to run a web business, so let me say the quiet part: publishers block agents because agents are pure cost. An agent visit consumes bandwidth, extracts the value, and returns nothing — no ad impression, no affiliate click, no email capture, no brand exposure. Blocking isn't hostility toward AI. It's rational economics. You don't negotiate with traffic that can't pay. The pieces of a solution are actually appearing, just not assembled: 1. Identity: Web Bot Auth / signed agents. Remote browser platforms cryptographically sign agent requests; WAFs (Cloudflare, Akamai, AWS) verify them. Sites can now distinguish "Claude acting for a real user" from a scraper farm. 2. Payments: Pay Per Crawl and the x402 protocol. A site can return HTTP 402 and charge per request. Agent wallets shipped this same week. Machine-to-machine micropayments are no longer theoretical. 3. Missing piece: attention passthrough. And this is the one nobody's building. Here's the idea. Per-request micropayments will work for some content, but the web wasn't built on subscriptions — it was built on sponsored attention. The agentic web will be too. What's missing is a way for a website to pass a sponsor message *through* the agent to the human on the other end. Picture a site serving content two ways: a rendered page for humans, and a structured feed for agents. The agent feed carries the same content plus a machine-readable sponsor block with explicit terms: "This content is licensed for agent consumption on the condition that the following attribution/sponsor line is surfaced to the end user." The agent presents the answer *and* the sponsor line. The site gets paid attention. The user gets the content. Everyone's incentives point the same direction — which is the only architecture that ever actually works on the internet. "But agents will just strip the ad." Right — an anonymous scraper will. That's exactly why identity is the prerequisite, not a nice-to-have. You can't hold an anonymous bot to a display agreement. You *can* hold a cryptographically signed agent to one, because there's something to revoke. Cheat on the terms, lose the signature's trust, get blocked everywhere that WAF network reaches. Identity turns "please show our sponsor" from a request into an enforceable contract. The major AI labs have every reason to comply — they need publisher cooperation far more than they need to save users from reading one sponsor line. What needs to exist: - A standard format for the agent-facing feed: content + license terms + sponsor payload. Think llms.txt, but grown up — with an economic layer instead of just a courtesy layer. - WAF-level enforcement tying feed access to signed identity and terms acceptance. - Client-side conventions for how agents disclose and render sponsor content to users. (Honestly, a labeled sponsor line in an agent's answer is *less* intrusive than the ad-choked pages we all browse now.) - Analytics flowing back to publishers: impressions delivered through agents, verified by signature. Whoever standardizes that format owns a meaningful piece of the next web. It's not a hard technical problem — it's a schema, a signature check, and a settlement rail, and two of those three now exist.

• 
  biggy (@biggy_kta) reported 35 minutes ago

  Cloudflare shipped programmable wallets for AI agents. Autonomous stablecoin payments for APIs, in production. The payment layer and execution layer are now the same problem. Most infrastructure is going to find that out at the worst possible time.

• 
  sam (@samgoodwin89) reported 36 minutes ago

  @K4y1s @nebiusai @Cloudflare Env vars are standardized with Output<T> const getter = yield* someOutput The runtime implements support, but it looks the same for all bindings. AWS bindings are good examples of this.

• 
  Zubiqo (@zubiqo) reported 38 minutes ago

  UPDATE: 🚨 N-able $NABL issues Hotfix 2 for N-central as attackers breach managed systems. Threat actors exploited CVE-2026-18577 to gain administrative access to N-central servers starting July 31, 2026. Attackers leveraged the Take Control feature to access endpoints and registered Cloudflare Tunnels for persistent access. The flaw stems from an incomplete patch for CVE-2026-18556 and is flagged by CISA as actively exploited. N-able urges on-premise administrators to update to version 2026.3.1.10 immediately even if Hotfix 1 was installed. "This is not a duplicate of our previous communication. Hotfix 2 is required, even if you already applied the earlier hotfix." — N-able When an RMM tool gets breached, revoking server access does nothing after attackers plant backdoors across downstream endpoints.