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:

• 
  Ben Patton (@benapatton) reported 6 minutes ago

  @flybayer @inngest @flydotio Sorry that’s why I indicated unrelated. It’s hooked into Cloudflare for me to auto fix issues and report back I’m mostly using it for more fine grained personal assistant type workflows/checkins

• 
  Brandon Beery (@NDominator) reported 9 minutes ago

  One of the Holy Grail problems at Press Ganey was theory crafted around happiness. It was a side comment at a retreat. Not to be taken seriously. How to survey and have predictive analytics around a happiness equation for healthcare. Can you know what will make a patient happy? There's a hundred reasons why it's a golden goose that'll never exist... But to try to do that now with LLMs as a private practice? A single doc and a dream with their $20/mo Codex subscription? Not a 30+ year old company purchased by Qualtrics for their MASSIVE database and expertise in the field? Good. Luck. Can AI help with better health outcomes? ABSOLUTELY. Can skills, agents, harnesses, frontier or even local models be a big part of that? Yes! Skills are just SOPs for bots. If you can teach a person how you do something you can teach a bot. I have a cron job through my Hermes agent that texts me every day at 11AM asking how my back is doing. My answers get scored, my notes taken down, and sent to supabase. Then I have a dashboard of the data up on a cloudflare site so I can see it anywhere on any device. But that's because it's just for me. I wanted to know what was causing my back pain and what made me feel better. I have agency over my health and health data. I can't imagine the red tape a doc would have to go through to have that I do daily setup for their patients to not get nailed into oblivion from CMS, HIPAA, etc. Just the security on the message would be a nightmare. If you want to do this, you don't teach the patient how to ruin your life 24/7 with AI. Which is what you'd get if they were messaging you with their latest daily updates. No one wants to deal with that, let alone your doctor who is used to 6 minute appointments. You do this instead: You take your specialty, what makes people go to you, and you record it. Document it out. Transcribe it. Get as much of you down digitally as possible. Then you take digital 'you' and make that skills. That's your views, your beliefs, your techniques, your skillset, the nice testimonials people have about you, and all of your case studies and stories anonymous and generalized. Take your bundle of skills and package them all up as on demand consult plugins. They never send you their data. Everyone plays on their own machine with their own risk and liability. They are glorified biohackers tinkering with their own body, not patients under your care. I say plugins because if they are using Codex or Claude Code/Cowork it'll do everything you'd do end to end with many skills. No copy/pasting between a zillion chats.. That's just confusing. It's the same decision tree you'd work through if you worked with them in person. Literally to your tone, the questions you'd ask, the logic in your brain just worked out in code with their context. But they are stepping through their own health data, their own journey just more informed by your opinion. Not health or investment advice. Anyone can do this for themselves.

• 
  AI News (@ainewsusa) reported 10 minutes ago

  🚨 Breaking in AI: 💻 Cloudflare Cuts Astro Github Issues by 85% with AI Agents Here's what's happening and why it matters 🧵👇 #AICoding #GitHub

• 
  TomOnTech (@TomOnTech) reported 14 minutes ago

  AI AGENTIC PAYMENTS: The Middle Layer May Capture the Most Value AI agents are beginning to purchase data, software, computing power and services without a person initiating each transaction. Over time, agents could conduct more transactions than people, with many payments worth only a few cents or fractions of a cent. This does not necessarily mean payment processors will collect large fees. Coinbase reported more than 165 million x402 transactions but only about $50 million in cumulative volume—roughly $0.30 per transaction. The x402 protocol is also open and charges no protocol fee. If basic settlement becomes inexpensive and standardized, more value may accrue to the middle layer between the agent and the payment rail. That includes: • Identifying the agent • Confirming its permissions • Setting spending limits • Metering resource consumption • Requesting and verifying payment • Routing the transaction • Managing fraud and compliance • Granting access to the requested resource Public companies positioned around this middle layer: Cloudflare $NET Cloudflare may have the most strategically important position because it sits directly between agents and online resources. Its Monetization Gateway is designed to let an API, dataset, webpage or AI tool require payment before providing access. Cloudflare can potentially handle the payment request, usage metering, verification and access decision at the edge. Cloudflare Wallets could also give agents programmable spending limits, approved merchants and maximum transaction sizes. This places Cloudflare on both sides of the transaction: helping online resources collect payments and helping agents make them. The products are still early, however, and meaningful revenue has not yet been demonstrated. Coinbase $COIN Coinbase has the most developed overall agent-payment stack. It created x402, operates Base, provides agent wallets, facilitates payments and participates in USDC economics. Because x402 is open and vendor-neutral, Coinbase’s long-term opportunity is not charging a large protocol fee. It is monetizing wallets, balances, compliance, business services and activity occurring through its infrastructure. Mastercard $MA Mastercard’s potential role extends beyond processing the payment. Agent Pay for Machines is designed to manage identity, permissions and trust across cards, bank accounts and stablecoins, including high-frequency payments worth fractions of a cent. Even if settlement moves to inexpensive stablecoin networks, Mastercard could remain involved as the credentialing and risk-management layer. Visa $V Visa is developing agent scoring, tokenized credentials, fraud models, stablecoin settlement and an agent directory. Its infrastructure may be especially relevant when an agent makes a larger purchase for a person and the merchant needs to confirm that the agent is legitimate, authorized and operating within the user’s instructions. PayPal $PYPL PayPal combines merchant distribution, consumer wallets, PYUSD, fraud management and dispute resolution. Its strongest opportunity may be serving as the connection between consumer agents and merchants rather than processing sub-cent machine-to-machine payments. Circle $CRCL USDC currently dominates x402 settlement, making Circle an important part of the underlying payment rail. However, Circle primarily earns reserve income on USDC balances rather than revenue from each transaction. High transaction volume matters only if it also creates larger funded balances or demand for Circle’s paid wallet, compliance and developer services. Marqeta $MQ Marqeta can issue virtual cards with detailed spending limits and programmatic controls. This makes it a useful middle layer while agents still need to purchase from merchants that accept cards but not stablecoins. Its role may become less important if direct wallet-to-wallet payments become widely accepted. My current ranking: $NET — payment and access decisions at the internet edge $COIN — wallets, facilitation, Base and USDC economics $MA — agent identity, permissions and trust $V — credentials, fraud protection and merchant acceptance $PYPL — connection between consumer agents and merchants $CRCL — underlying stablecoin settlement $MQ — programmable card bridge

• 
  OB (@obatt) reported 14 minutes ago

  @Cloudflare Your own MCP auth UI totally sucks

• 
  Onur Genes 🐺 (@onurgenes) reported 15 minutes ago

  @jonathan_wilke also probably someone reported it. cloudflare first takes down the website and then asks you to prove that your website is not fraud. you should definitely check that

• 
  Simon Høiberg (@SimonHoiberg) reported 18 minutes ago

  Since we moved from AWS → self-hosting on Hetzner, our products have been much more stable/reliable. Our uptime is near-100% and we're never blocked from shipping. So the whole "self-hosting is fun until servers break at 2 AM" is a meme. You know which services go down all the time? - Supabase - AWS - GitHub - Cloudflare Ask my competitors 😬 They would know!

• 
  Matthieu H. (@twMatthieuH) reported 18 minutes ago

  The stack: React Native + Expo, TypeScript, Hono on Cloudflare Workers. Boring on purpose. And AI-assisted everywhere: coding, support replies, content, ASO. When you have a few hours per week, you don't want to fight your tools.

• 
  LilRhodySpecial (@rhody_special) reported 22 minutes ago

  @eastdakota I cancelled Spotify because they partnered with Cloudflare. Bad move stepping on artists. Folks do your selves a favor do not use any voice models cloudflare and the rest of the Stanford scam artists are working hard to make sure you own nothing and that includes your voice

• 
  A. Amorim (e/acc) (@deildo_jr) reported 24 minutes ago

  @MrPunyapal If Cloudflare has any outage

• 
  Artem Builds👷🏻‍♂️ (@artembuilds) reported 25 minutes ago

  @DaniellHemmati Yes, wrangler. Have been facing a lot of issues with the API token side of Cloudflare Pages lately. For now I have manually deployed it on my machine, using wrangler.

• 
  Abdellatif (@Abdella6if) reported 27 minutes ago

  @harisbuild @Cloudflare interesting, will look into it. Does cloudflare support BYOK?

• 
  FLINT (@FLINTKYA) reported 28 minutes ago

  So the firewall blocked the attacker, and then an AI agent finished the attack for them? That is the security problem behind Ghostjacking, an AI agent hijacking technique demonstrated by Tenet Security across Cloudflare, Datadog, and Sentry. Ghostjacking is an attack in which adversaries poison the logs, alerts, telemetry, or other operational data AI agents consume. Instead of compromising the agent directly, the attacker manipulates information the agent already trusts, then relies on the agent’s legitimate permissions to complete the attack. In @tenetsecurity's Cloudflare demonstration, the malicious request was actually blocked. The attacker received a 403, exactly what you would expect from a functioning security control. But attacker-controlled data from that request entered telemetry that an AI coding agent later reviewed. The agent interpreted the poisoned data as trustworthy context and used its own authorized access to modify DNS records. Tenet reported the technique succeeded 9 out of 10 times against Claude Code in its tested configuration. In other words, the firewall worked. The trust model, not so much. How Ghostjacking works: 1. An attacker submits malicious input. 2. A security system blocks or records it. 3. The attacker-controlled content enters logs, alerts, or telemetry. 4. An AI agent consumes that data during a legitimate workflow. 5. The agent acts on the poisoned context using its real permissions. The Datadog and Sentry demonstrations push the idea further. Poisoned telemetry can lead agents toward code execution, credential exposure, infrastructure changes, and even agent-to-agent lateral movement, where one compromised decision influences another agent downstream. That creates a problem traditional IAM was never designed to solve. An AI agent can be properly authenticated, use valid credentials, operate within its authorized permissions, and still execute an attacker’s intent. That distinction matters to us as AI agents gain authority over payments, infrastructure, purchasing, customer accounts, and other real-world actions.

• 
  Ahmet (@ahmetdotrun) reported 28 minutes ago

  two things i've been experimenting with over the last couple of days: 1) kitesurf by @Cloudflare free while in beta. i'm looking at it for (scaled) agentic offensive security work: let an agent explore an app, understand it, map the attack surface. browsers are expensive to run, hard to scale. it seems a lighter option on CF's edge, so potentially a cost effective one for me. tho, bot challenges are still a problem. 2) grok build by @SpaceXAI first time giving grok 4.6 a proper shot. faster than other frontiers and more capable than i expected. burns through the limits quicker than i'd like though.

• 
  🌱 Peter Van Dijck → 🧵 (@petervandijck) reported 28 minutes ago

  @aarondfrancis (not sure who the right person is) - my cloud apps went down, ' 6 of 8 apps in us-east-2 returning Cloudflare 1016 (origin DNS error)'. It's not an app issue. I can send more detailed info but the Help link on the site seems to be disabled?