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:

• 
  Jim Liu (@jiahanjimliu) reported 6 minutes ago

  $CRWV: Q2 Earnings Revenue: 2.6B or 10.4B ARR EOY 2026 ARR Target: 18B-19B Backlog: 104.2B at end of Q2 (129.2B Aug 11) Adjusted EBITDA Margin: 59% Operating Margin: 5% Adjusted Net Loss: -22% Full AI Platform Contrary to misinformation on X, Coreweave serves Managed Inference, Development Tools, Orchestration and Observability and are a full AI Platform. EBITDA Margins Their EBITDA margins with software come out to 59%. $IREN's H1-4 EBITDA margins are 85% but after depreciating DC build cost for an apple-to-apple's comparison, $IREN's H1-4 EBITDA margin minus DC depreciation come out to 55%. $IREN is able to keep up on EBITDA margins without software because IREN is vertically integrated on the power and datacenter front. Coreweave's software make up for it's colocation costs to achieve 59% EBITDA margins. For comparison $NBIS has ~40% EBITDA margins. Once $IREN integrates Mirantis and DSX OS, it has a great chance of leading on EBITDA margins among the 3 Neoclouds. Backlog Coreweave hit a 129.2B backlog on earnings day Aug 11 which is a huge 25B increase from 104.2B at end of Q2. This is great news for $CRWV, $NBIS, $IREN as it shows the unprecedented demand in this sector. Financing Coreweave will likely benefit from Nvidia's 500B financing pool along with $NBIS and $IREN. However, it's high interest cost make it's Net Loss Margin -22% on what otherwise is a great inflection point of 5% operating income. In other words, Coreweave is a profitable business operations wise besides its high interest payments. This bodes well for Neocloud sector profitability as a whole. Enterprise Customers Coreweave has the widest diversification of customers among Neoclouds with: Primary Cloud: Bentley, Caterpillar, Grammarly, Isomorphic Labs, Sunday Robotics. Expanded Partnership with: Cognition, Databricks, HRT, Periodic Labs, Rescale, Runway ML. Primary cloud is important because although Coreweave and NBIS both serve Cloudflare, they are not the primary cloud for cloudflare. Likewise Shopfiy's primary cloud is GCP not NBIS. Being a primary cloud for a customer is more indicative of usage beyond of orchestrated GPUs or bare metal+k8s. Contracted Power 3.7GW by end of Q2 and 4.2GW by Aug 11. This is a majority colocation however, colocation is working for Coreweave as they still achieve 59% EBITDA margin. This sometimes results in delay but their main problem is interest expense, not colocation. $CRWV is a 55B company with 35B debt for a total of 90B EV. If $IREN can buildout 5GW and integrate in Mirantis to catch Coreweave, it has large upside as $CRWV itself still has significant upside from it's 90B EV.

• 
  jumanji 𝕏 (@heyjumanji) reported 10 minutes ago

  Hi @CloudflareHelp @Cloudflare i lost mt access to my cloudflare account and also lost my 2fa codes can you please help me to get back my account.

• 
  Kenton Varda (@KentonVarda) reported 13 minutes ago

  Tried Muse Glimmer in Cloudflare OS via ollama. It was able to write a basic gadget OK but it seems completely flummoxed by the concept of server -> client callbacks. There's a whole section in the system prompt explaining how to do this with Cap'n Web, but Muse acts as if it doesn't see this section at all and instead tries other techniques like polling, creating a WebSocket (not allowed by the sandbox), and some other hallucinated garbage. Even if I specifically tell it to refer to the system prompt on how to use RpcTarget it doesn't know what I'm talking about. I asked it bluntly if it could see the section of the system prompt and it didn't want to tell me -- apparently it is trained that the system prompt is a secret -- but eventually it conceded that the section is there and summarized the content. But when I asked for an example it gave me something wildly hallucinated, completely unrelated to the example in that section. Gemma 4, in contrast, totally understands this section, accurately describes it, and follows it correctly when building gadgets... This could very well be an ollama bug, the support for Muse Glimmer just landed within the last 24 hours. Maybe the system prompt is getting cut short, and the model is just lying when it says it sees the section? Man I wish people wouldn't train models to try to hide the contents of the system prompt -- who cares, your prompt is not secret sauce. Anthropic models happily recite the system prompt back to me -- Anthropic! If Anthropic doesn't care about hiding system prompts, you probably shouldn't either.

• 
  TeleLLM (@Telestijl) reported 13 minutes ago

  @levelsio Private Relay is a likely culprit — iCloud → Private Relay (or Safari's "Hide IP Address") routes DNS/traffic through Apple/Cloudflare relays per network, and macOS applies it more aggressively on a fresh hotspot connection than iOS does on its own cellular link. Toggling it off for that specific network usually fixes the "works on iPhone, not tethered" split.

• 
  Youth (@Web3__Youth) reported 15 minutes ago

  The price of frontier AI just hit zero. And almost nobody noticed. 3 things happened this week that would've cost $200/month last year: 1. GPT-5.6 Luna — free, unlimited, no card 2. DeepSeek v4 Pro — 400k context, zero cost 3. Claude Code, Cursor, Replit — all free via FreeBuff No API keys. No subscriptions. No payments. Ever. A GitHub repo tracking 424+ free LLM APIs across 30 providers is being refreshed daily. Gemini, Groq, NVIDIA NIM, Cloudflare, Mistral, Cerebras, Hugging Face — all free tiers listed with exact rate limits, context windows, and base URLs. The implication nobody is talking about: Last year: $20/month = 1 model, rate limited Today: $0 = 5+ frontier models, 400k context, subagents The moat was never the model. The moat was access. And access just became free. If you're still paying for AI APIs in 2026, you're paying for convenience, not capability. The builders who win this cycle aren't the ones with the biggest budget. They're the ones who realized the price dropped to zero and built accordingly. Save this. The gap between people who know and people who don't is widening every day.

• 
  murdok (@murdok_gg) reported 15 minutes ago

  (would you believe that i only spend $70 on groceries per week, but i splurged by buying 2 domains for $25 for a year a piece?! omg its crazy that cloudflare can sell at cost from a reg that people like, customer service is interesting these days...)

• 
  h index enjoyer (@BigwetRealism) reported 17 minutes ago

  getting real tired of hitting cloudflare issues on @biorxivpreprint even tho I'm not a bot!!!!

• 
  Simon H (@dummdidumm_) reported 20 minutes ago

  @tnkuehne We ditched using the environment API to its fullest for now, because it adds too much complexity and maintenance for appeasing essentially one runtime (Cloudflare). But we'll still have much better support for it with deep dev time integration, just through another way. PR soon.

• 
  allen (@apgxxn) reported 23 minutes ago

  He's not even old enough to remember a useEffect took down cloudflare last year

• 
  The Startup Ideas Podcast (SIP) 🧃 (@startupideaspod) reported 24 minutes ago

  What does an AI agent actually pay for? Clean data that is structured and easy to access. Cloudflare is building the access and payment layer right now. So it's still early, you have 6, 12, maybe 18 months. Start with building the manual version and sell it to humans today. Curate the data before the space gets hyper-competitive. Five questions that point you at an idea: - What decision is expensive? - What information is messy? - What changes often? - Who already pays for help? - What would an agent need to do the job better? The internet is shifting from pages humans visit to resources agents use.

• 
  eliohead (@machmadera) reported 27 minutes ago

  What’s happening with Cloudflare today? Getting 520 errors from the OpenAI API in Europe, and now 524 timeouts from another service I’m using

• 
  Officially Retired Owl Dope Capone (@Owl_Dope_Capone) reported 28 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.

• 
  🔆 j i k o ⋆₊ ‧ ˚⊹ 🏜️ (@lisey_ann) reported 28 minutes ago

  @Loganthemoo @ReclaimTheNetHQ Web3 is way ahead of you on that. But even they too are behind if they aren't using an entirely different network stack using ICP or something. Cloudflare can delist whoever they want

• 
  Phil | Rentier Digital Automation (@rentierdigital) reported 28 minutes ago

  i switched databases twice in 10 days and learned the hardest lesson: the engine was never the problem. 47 million rows read in a day. zero users. my filing monitor app was still in dev, but cloudflare d1 was billing me like i had customers. so i migrated to local sqlite. queries got faster. problem solved, right? nah. then the dataset hit 2.12 million companies and everything broke differently. the vps ran out of ram. /admin/national took 12 seconds cold, then 300x slower depending on cache state. a coin flip with expensive tails. so i migrated again, this time to postgres. the queries were still bad. all of them. until i went in and fixed each one by hand. full-text search went from 2141ms to 21ms. not because postgres is magic. because i finally had explain analyze that told the truth, and i built a gin trigram index paired with a bounded subquery. /api/dirigeants went from 468 separate database queries down to 11. the real problem was never d1 vs sqlite vs postgres. it was that i was writing bad queries and couldn't see it until the engine gave me tools to diagnose them. you can hide a lot of sins behind a managed layer or an embedded engine. postgres just made the sins visible. switch engines if you need to. but switching engines doesn't fix bad queries. it just moves the problem to a place where you can finally see it. i build and ship daily. Claude Code, Codex, whatever ships fastest. SaaS, tools, automations. ⭐ if AI can build it, i've probably broken it first. what works → link in bio

• 
  tcpdump (@dump_tcp) reported 29 minutes ago

  @a_shimanski @Cloudflare Yeah it would probably help but no point if paying for requests I would suggest setting up cloudflare cdn with you're own server to be able to have unlimited requests and more customization