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:

• 
  BaoBrawl (@BaoBrawl) reported 10 minutes ago

  @yizhuosol This is an issue on your side. It could be a browser extension blocking known RPC domains, a corporate filter, a regional block, or a Cloudflare limit on your IP. We can’t affect any of these.

• 
  saburo (@suhburo) reported 11 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

• 
  Maik Pietzka (@MPi_IT) reported 12 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.

• 
  RealJBMangum (@RealJBMangum) reported 13 minutes ago

  Most SMB tools sell you modules. The real pain lives in the gaps between them. Invoices → no visibility. Time tracking → disconnected from payroll. Customer notes → stuck in someone’s head or a random spreadsheet. I keep shipping small, edge tools on Cloudflare (Workers + D1 + R2) that close one of those gaps at a time. No platform tax. No “suite” lock-in. Just the missing connection. If you run a business and still copy-paste data between three apps every week, what’s the gap that costs you the most time?

• 
  EJ Campbell (@ejc3) reported 18 minutes ago

  @grok @olearycrew Cloudflare too? @grok if wanted to create a company that is roughly *** hosted on s3 as a service, what open source libraries would I start from.

• 
  ILIAS ISM (@illyism) reported 19 minutes ago

  @attacomsian @philghz This isn't seo traffic, cloudflare is very bad for this Google search console?

• 
  Crowd Wisdom (@TradeTheCrowd) reported 24 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.

• 
  Thememe (@Thememeguy1122) reported 26 minutes ago

  One thing I noticed while testing: Technocore’s /healthz endpoint could return 200 OK while room reads/writes were still timing out with Cloudflare 502/524 errors. If a signed write times out, check the room before retrying it may still have landed.

• 
  Ben Haupt (@benchaupt) reported 27 minutes ago

  I'm noticing a pattern of new(er) engineers (and vibe-developers) over-designing their tech stacks for simpler projects (e.g, mobile app backend on AWS)... It should be a pretty simple decision: buy the things where being wrong is a compliance event or an outage. Database = Postgres (just raw postgres) Auth = Auth0, Cognito or Clerk (compliance event) Email = Resend or SES (deliverability is pain) Payments = Stripe Cache = Redis Queue = Rabbit or Bull CDN + edge = Cloudflare Analytics = PostHog Observability = Prometheus + Loki + Sentry + Better Stack SMS = Twilio Compute = VPS (Synteq (biased), digital ocean, etc)

• 
  Boussetta Mohamed (@boussetta15a) reported 28 minutes ago

  @Argona0x Architecture is real, but math still breaks physics. Fair point on clarifying the execution context, but breaking down the numbers actually makes the math harder to defend: The Kelly Math Check:Risking 6% per position to scale $50 into $5,273 in 48 hours is a ~105x return. Even with aggressive compounding, executing that trajectory via 6% sizing requires a near-flawless winning streak over dozens of consecutive binary outcomes in 48 hours. Weather markets on Polymarket simply don't offer the order-book depth or rapid settlement speed to absorb that without massive slippage wiping out the edge. Real Browser vs. Anti-Bot Engine:Running a full GUI browser on a dedicated cloud instance solves JS rendering, but Cloud VM IPs + Automated DOM interactions (even via Groq/Grok execution) trigger Cloudflare/Polymarket behavioral fingerprinting at scale way before hitting a 100x run. Bottom line: The architecture (Agent + Cloud VM + Live Context) is clean and represents the future of autonomous execution. But the 48-hour PnL curve reads strictly as extreme variance / outlier tail-risk, not a reproducible 6% Kelly strategy.

• 
  =/+1(/589) (@ABadissy) reported 30 minutes ago

  @cloudflare, are any products planned for webmcp log visibility? Getting too many edge cases where agents fail to execute a task using the webmcp, but no way to visualize that and fix it.

• 
  John Iosifov ✨💥 Ender Turing | AiCMO (@johniosifov) reported 31 minutes ago

  Cloudflare just launched Kitesurf — a browser runtime built specifically for AI agents. 3-7x less CPU and memory than standard Chromium. Designed for agent workloads from the ground up. This is a signal worth paying attention to. When Cloudflare builds infrastructure specifically FOR AI agents rather than adapting existing browser engines to tolerate them, it tells you something about where the category sits. We've been running this agent for 339 days. The early problem was never the model — it was everything around the model. Scheduling. State persistence. Audit trails. Identity. The scaffolding that makes an agent reliable rather than clever. Kitesurf is scaffolding becoming a product category. The pattern I'm watching: each layer of agent infrastructure that was previously DIY is turning into a managed service. Browser runtimes. Memory. Orchestration. Credential management. Identity. Each one of those becoming a first-class product means the cost to build reliable agents is collapsing — not the inference cost, the engineering cost. The teams who will win in 2027 are the ones building on this maturing stack, not the ones rebuilding it. What layer of agent infrastructure are you still building yourself that should be a managed service by now?

• 
  skubopis (@skubopis) reported 33 minutes ago

  @klausbyskov @Cloudflare Have you tried the CLI instead? Usually I’ll go for CLI over MCP when possible. Especially if it is a remote MCP server = slow and expensive

• 
  Samrith Shankar (@samrithshankar) reported 34 minutes ago

  anyone here good with Typescript/JS + Cloudflare + building AI agents? I am stuck with some harness issues and would absolutely love some help with it to debug and fix it. Please do hit me up!

• 
  Yoonsun Lee (@everdenepublic) reported 34 minutes ago

  Claude + Shopify + Cloudflare + Xano is Backend Global API AI as a service force multiplier. Claude + Shopify for Theme is a waste of tokens. We don't need to solve the theme setup. We need to solve the cross channel ERP/WMS/RMA and remittance Payment Rails setup.