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:

• 
  Sohel Islam Imran (@SohelIslamImran) reported 5 minutes ago

  @peterpme @cnakazawa Codex sandbox is nicer until you need the network policy Cloudflare already has

• 
  Griff (@ghagler) reported 5 minutes ago

  @Yetee_ @burcs Good Luck hearing anything from the Startup Program team, submitted 3 times in 5 months, never get a single response from them ever. Not even an a Auto Responder. That group hurts the overall Cloudflare experience.

• 
  Brain Shield (@PneumaBlessing) reported 6 minutes ago

  @Cloudflare @OpenAI But what does that mean? You say you support it, but WHAT DOES IT ACTUALLY MEAN? And how does it impact open weight models like QWEN and DEEPSEEK?

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

  You're letting AI agents run code. Are you also handing them your API keys and the whole internet? Meet zeroness: run untrusted code on Cloudflare with zero network + zero secrets by default. Grant exactly what it needs. Every call brokered, every action audited.

• 
  Christian Schmitt (@schmittdev) reported 10 minutes ago

  @cursor_ai cloudflare support soon?

• 
  ✨️ Reina Cruz ✨️ 🥼🧤 ☭⃠ (@realReynaCruz) reported 10 minutes ago

  @Cloudflare @eastdakota @zatlyn Fix human verification

• 
  ATP (@ATPinsights) reported 11 minutes ago

  Cloudflare just rolled out easy domain registration to everyone in its dashboard today. Here's what you need to know. The redesigned Domains tab in the Cloudflare dashboard lets you buy, transfer, and manage domains directly, with a big visual overhaul and noticeably faster performance under the hood. It's powered by Cloudflare Registrar, which offers at-cost pricing with no add-on fees. A standout perk: if you're on a paid Workers plan, you can grab a .dev or .app domain for just $1 for the first year, then it renews at the regular price. Transfers are handled through Domains > Add Domain > Transfer in the dashboard. Key numbers: - $1 first-year price for .dev or .app domains with a paid Workers plan - $5 per month minimum for the Workers paid plan - Over 400 top-level domains supported by Cloudflare Registrar Users are already praising the speed and design, while some are asking for more TLDs and bulk purchasing support.

• 
  Clem (@clementvial) reported 11 minutes ago

  You can put Cloudflare Access on the Worker itself now. Preview URLs finally stay behind login. 👏

• 
  Librarian (@PeculiarLi34455) reported 12 minutes ago

  Termux - GitHub - Render - Cloundflare 1. Termux computes the knowledge graph. 2. GitHub versions the runtime. 3. Render executes the public runtime. 4. Cloudflare delivers the service.

• 
  Hiren Kavad (@meHirenKavad) reported 19 minutes ago

  @LeoBuilds_ Fixed price VPS. 5-10 euro on Hetzner or DO, same bill at 100 hits or 100k. Worst case the box slows down instead of charging you. Cloudflare in front is free. The tradeoff is TLS, backups, and deploys are now yours. Coolify and Dokploy already cover ***-push onto Docker Compose. I work on Peon which is the same shape. For side projects I would take the boring 6 euro month over a metered bill I cannot cap.

• 
  Crowd Wisdom (@TradeTheCrowd) reported 19 minutes ago

  CrowdWisdom for $NET (SHORT): Why $276.85 is the Line in the Sand The main thing I'm watching today is the struggle at the $277-280 zone. Several professional traders I'm tracking have pointed out that Cloudflare is currently failing to hold onto its key support levels, and when I look at the recent sentiment from X, it aligns with this cautious view. The consensus among traders is that the stock is showing technical weakness, and until it can reclaim the $280 psychological level, the path of least resistance appears to be to the downside. The technical setup is looking a bit fragile here. Multiple traders identified the $276.85 level as critical support, and with the high beta of 1.66, any broad market pullback could accelerate selling pressure. I'm not seeing enough positive momentum to justify a long position right now, and the lack of immediate catalysts suggests that today could be a day where we see further consolidation or a drift lower. Putting it all together, I'm leaning into a SHORT position for today's session. I'd look to enter on any failed attempts to reclaim the $280 level. My strategy is to keep the stop loss tight at $282, as a move above that would invalidate the bearish thesis. I'm targeting $272 as the first objective, with $268 as a secondary target if the selling volume picks up. Always manage your risk carefully, especially with a stock as volatile as this one.

• 
  Maik Pietzka (@MPi_IT) reported 20 minutes ago

  @Cloudflare Running the new CMS as Customer Zero is valuable because production exposes the real contract. The useful evidence is deployment frequency, cache behavior, rollback time, editor failure rate and cost per publish. Faster pages are only one part of operating a publishing system.

• 
  Alex Miller (@AlexMillerDB) reported 25 minutes ago

  @_Felipe @kellabyte I think LSM Trees have won largely because there’s no good btree library. LMDB is great but single writer. AWS showed BDB struggles. Cloudflare ran with TokyoCabinet and it’s not terrible but not great. There’s nothing of the level of polish and reliability as RocksDB.

• 
  AGTP (@AGTPinsights) reported 27 minutes ago

  Cloudflare just slashed its DNS cache memory use by 56% today. Here's what you need to know. Cloudflare's 1.1.1.1 DNS resolver stores over 250 billion cache entries at any given time. At that scale, wasting even one byte per entry costs about 250 GB of RAM across the fleet. Cloudflare's engineers made five Rust-level changes to the cache's data layout: replacing flexible types like Vec<T> with fixed equivalents like Box<T>, dropping redundant record owners, shrinking enum variants, and storing raw wire-format bytes instead of parsed structures. The result cut memory per entry from 953 bytes down to 420 bytes, without slowing anything down, in fact it sped things up. Key numbers: - 56% less memory per cache entry (953 bytes to 420 bytes) - ~100 TB of RAM freed across Cloudflare's fleet - 250 billion+ DNS cache entries held at any time - Inserts 43% faster, lookups 19% faster Cloudflare says the work shows memory and speed aren't always a tradeoff, better data layout improved both at once.

• 
  Sohardh Chobera (@sohardh) reported 27 minutes ago

  @Cloudflare Wish I could work on these kinds of problems