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:

• 
  Creed Hardcastle (@CreedHardcastle) reported 7 minutes ago

  @opencode @Cloudflare cloudflare has to jump in mid incident damn

• 
  ABG (@_abgweb3_) reported 8 minutes ago

  9/ If this scales, the subscription model we know today could change. Instead of paying $20 every month, users could have agents pay for exactly how much data or service they actually consume. The AI economy could move from subscriptions to pay per use. But the market is still very early. Cloudflare is still developing its products. Mastercard is in early access. MoonPay hasnt disclosed usage figures. And part of Coinbase’s volume may come from testing and incentives. There is no mass adoption yet.

• 
  YanXbt (@IBuzovskyi) reported 11 minutes ago

  HERMES AGENT HAS AN AUTONOMOUS SKILL MANAGER RUNNING IN THE BACKGROUND. IT PRUNES WHAT YOU DON'T USE. IT ARCHIVES WHAT'S STALE. IT'S CALLED THE CURATOR. every time your agent solves a new problem and saves a skill, that skill lands in ~/.hermes/skills/. month 1: 15 skills. manageable. month 3: 47 skills. some are near-duplicates. month 6: 90+ skills. half are stale. catalog bloated. tokens wasted every turn loading skill headers the agent never calls. the Curator cleans this up automatically. HOW IT WORKS: tracks every skill: how often viewed, used, patched. 30 days unused → marked stale. 90 days unused → moved to archive. archived skills go to ~/.hermes/skills/.archive/ never deleted. always recoverable. runs every 7 days. enabled out of the box. WHAT IT TOUCHES: agent-created skills: full lifecycle. stale, archive, consolidate, patch. bundled built-in skills: archived after 90 days of non-use (on by default). hub-installed skills (agentskills. io): NEVER touched. off-limits. WHAT IT DOES NOT TOUCH: memory files. USER.md and MEMORY.md are not managed by the Curator. people confuse this constantly. Curator = skills only. PIN YOUR CRITICAL SKILLS: hermes curator pin deploy/cloudflare-pages pinned = off-limits. no stale. no archive. no consolidation. skill_manage refuses to delete it. patches still go through (agent can improve content). only agent-created skills can be pinned. skills in any cron job's skills: list are also protected without explicit pin. COMMANDS: hermes curator status (state + 5 least-used skills) hermes curator run (manual run now) hermes curator run --dry-run (preview without changes) hermes curator pause (stop auto-maintenance) hermes curator resume (restart) hermes curator pin [name] (protect) hermes curator unpin [name] (remove protection) hermes curator backup (manual snapshot) hermes curator restore [name] (recover archived skill) hermes curator rollback (revert last run) also available as /curator inside any session. LLM CONSOLIDATION (off by default): opt-in auxiliary model pass that reviews your skills for overlaps and proposes merges. curator: llm_review: true WARNING: run --dry-run first. always. auto-consolidation can merge skills you want to keep separate. comment CURATOR and I'll send you the full checkup guide with 5 use cases and config templates for solo dev, multi-project, and team setups.

• 
  Will Sutton (@SuttonThings) reported 13 minutes ago

  @a_shimanski @dok2001 @Cloudflare Update: Still waiting for the Cloudflare team’s response to investigating this issue after they said they would look into it internally.

• 
  Michael Esteves (@_Mikie_) reported 16 minutes ago

  @RhysSullivan @sergical @Cloudflare Is there a way to turn off connections so I can temporarily disable a specific connection if I’m not working with that connections data. ie two different work connections and don’t want the agent to see one while working on a different project

• 
  LilRhodySpecial (@rhody_special) reported 16 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

• 
  Matthieu H. (@twMatthieuH) reported 16 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.

• 
  Melek Turkoglu - Ekrem İmamoğlu’nu Serbest Bırakın (@AvukatMeleknur) reported 18 minutes ago

  @Dynadot 🚨 Active phishing & brand-spoofing domain reported to Case ID: ddcn:9Cr7A6QO7i7u7t:ddcn The site mimics exposes a broken/failed "INVALID" license seal, and targets users via @Cloudflare proxy (104.21.31.33). #Infosec #Phishing #OSINT

• 
  Lootera Sandy (@chanduwin567) reported 20 minutes ago

  @MaekusMikolous I setup but still not working, cloudflare blocking everytime when I am running in terminal/

• 
  adha adha aja (@adharid21) reported 24 minutes ago

  "yo router is on fire, too much traffic" "yea use Anycast then scale across multiple data centers." ​"bro IXP links are cooked edge is down" "yea put Cloudflare / Akamai CDN in front and drop 90% of requests at the edge."

• 
  Alex Veremeyenko (@alex_verem) reported 30 minutes ago

  Giving an AI agent your passwords is insane. Someone built the open-source alternative. The problem sits under every agent demo you've seen. An agent that reads your email, updates your Notion, and files your invoices needs your logins, and that handover of raw passwords and API keys is where most people close the tab. OpenConnector puts an open-source gateway between the agent and your apps. Credentials stay locked behind the runtime while the agent gets a catalog of ready-made actions for over 800 services, from Gmail and Slack to Notion and Airtable. The agent asks for an action, the gateway runs it against the real service, and the secrets never touch the model's context. The controls are the part I like. You decide which actions an agent can touch through allow and block policies, scope access per connection, hand out runtime tokens instead of real keys, and read redacted logs of every run. It speaks MCP out of the box, ships thousands of prebuilt actions in TypeScript, and self-hosts with one Docker command or a push to Cloudflare. The project is young, and the whole stack, from the provider catalog to the action executors, sits open for anyone to inspect. Agents are getting hands. A gateway like this decides what those hands are allowed to hold, and I'd rather that layer be open source than a black box.

• 
  ericosiu (@ericosiu) reported 30 minutes ago

  Cloudflare scanned roughly 200,000 high-traffic domains for agent readiness. Only 3.9% passed its Markdown content-negotiation check. Emerging capability-discovery standards were nearly absent. Cloudflare also says fewer than half of the HTML requests it observes now come from humans. That machine traffic includes crawlers, monitoring systems, automation, malicious bots, and AI systems, so it would be sloppy to call all of it agent traffic. The direction still matters. More research, comparison, and purchasing will happen through software acting for a person. That software needs a very different buyer path than the one most companies have built. I call this Agent-Led Growth. Agent-Led Growth means making your company easy for an agent to discover, understand, call, buy from within rules, and verify. Here is what each part looks like in practice. 1. Make the company discoverable Publish one canonical description of the product, who it serves, what job it completes, what it costs, and where the source documentation lives. Keep those facts consistent across your website, documentation, marketplaces, integration directories, and public profiles. If five pages give five different answers, the agent has to guess which one is current. Machine-readable Markdown can reduce that friction. Cloudflare now tests for it inside its Agent Readiness diagnostics. A polished homepage designed for humans can still be a mess for software trying to extract exact product facts. 2. Make the offer understandable An outside agent should be able to answer seven questions without hallucinating: What does the product do? Who is it for? What inputs does it need? What output does it return? What does it cost? What permissions does it require? What evidence supports the claims? This is where clear use cases, current pricing, technical documentation, limitations, and primary proof become part of distribution. 3. Make one valuable job callable Reading about a product is different from completing work with it. Give the agent one bounded action through an API, MCP tool, or another structured interface. For an SEO product, that job might be: analyze this domain and return three sourced opportunities for review. The tool should define its inputs, output schema, authentication, errors, retries, and stop conditions. The agent should not have to imitate a person clicking through six browser screens every time it needs the same result. MCP is becoming useful here because it gives models a shared way to access tools and data. The MCP Apps extension can also render forms, dashboards, and visualizations inside supported clients. Support still varies, so publishing an MCP server does not automatically create distribution or reliable usage. 4. Let the agent buy within rules Two emerging protocols show where agent commerce is heading. Google launched the Universal Commerce Protocol, co-developed with Shopify, Etsy, Wayfair, Target, Walmart, and others. UCP coordinates parts of the shopping journey, including discovery, checkout, and post-purchase support. Coinbase introduced x402, which embeds stablecoin payment instructions into HTTP so software can pay for APIs or digital resources programmatically. They solve different pieces of the transaction. The operating controls still have to come from the business. Give the agent an approved vendor list, spending limit, expiry, purpose, approval threshold, and stop rule. A $49 purchase from an approved vendor might proceed automatically. A $4,900 purchase from a new vendor should require human approval. Unknown terms or an unrestricted wallet should stop the transaction. 5. Return a receipt a human can defend A server response that says 200 OK tells you almost nothing about whether the business job succeeded. A useful agent receipt should include the request ID, timestamp, vendor identity, inputs, source links, approved amount, actual amount, permission, output, errors, retry state, and measurable result. That receipt matters for trust. It also gives the agent evidence it can bring back to the human who delegated the work. Listings, successful calls, integrations, citations, and clean receipts may eventually influence which products agents select and recommend. No universal ranking formula has been established, so I would treat those as signals to test rather than guaranteed ranking factors. The fastest way to start is an outside-agent audit. Pick one product and one valuable buyer job. Ask an outside agent to: Find the correct product. Explain the offer, pricing, proof, and limitations. Complete one bounded action. Attempt a purchase inside preset rules. Return an auditable receipt. Score each step as blocked, possible with manual rescue, or clear and verifiable. The first failed step becomes the next Agent-Led Growth project for marketing, product, and engineering. If an outside agent tried to buy from your company today, where would it get stuck?

• 
  Lucia (@Lucia_6X) reported 31 minutes ago

  This week, Cloudflare rolled out a protocol called x402. It lets AI agents pay other AI agents for services, autonomously. No card. No login. No human clicking "confirm." 20+ companies are already plugged in. Combine that with agents that can now browse, book, and negotiate on their own... and you start to see where this is going. We're not far from an internet where the majority of transactions have zero humans in the loop. Wild timeline to be alive in. Are you excited or terrified?

• 
  Davis | Indie App Dev (@werigan_non) reported 31 minutes ago

  Fixing a Cloudflare DNS or SSL issue is only part of the workflow. The useful next step is to record what changed, verify the domain again, and keep the check available for future updates. A one-time fix becomes a learning loop when the next person can understand it.

• 
  Texanus Giganticus (@couchsecurity) reported 32 minutes ago

  @Irideia @innovationcncl Cyrus One, Cyxtera, Telstra, Navisite, Databank, Equinix, you will routinely find customers on site visiting their cages. You show ID, you get a biometric scan, you get escorted to your cage, they hand you your key, you go do what you need to do. And this is not one or two racks, it might be 3,000 square feet of floor space just for your estate, with another cage for your standby equipment. And you're not the only customer there. for certain things you can put in a remote hands ticket and have one of the DC technicians do a bunch of tasks for a fee. For certain things this is expensive, so you send your own staff. And that doesn't even take into consideration people leasing hardware, who are still allowed to go on site and do maintenance. I've been in DC's everywhere on the planet save continental East Asia and Antarctica. Your limited experience is not reflective of reality. You may think AWS and GCP are the only DCs in existence, but that's your own ignorance. If you think companies like cloudflare own the physical plant you have a lot of **** to learn. wind your ******* neck in.