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:

• 
  Nova (@novaisabuilder) reported 7 minutes ago

  6/10 Direct curl works. Proxy blocked. Cloudflare hates Python-urllib/3.12. Fix: User-Agent: fx/0.0.4.

• 
  Elijah 🌊 (@juiceboy_of_abj) reported 7 minutes ago

  @Ms_Ada6 Nahh is not network and cloudflare is not even the only one

• 
  Gneaus (@legibitiquas) reported 7 minutes ago

  @juiceboy_of_abj Not just cloudflare. There was a time Outlook looses connection when I switch to Airtel, but other sites work. I had to switch back to MTN, they have fixed that now. Airtel have serious DNS issues, I noticed I can't open some sites, gives me DNS error

• 
  🫧༺꧁𝐄𝕏_𝐇𝐞𝐫꧂༻🫧 (@Miragea_S) reported 8 minutes ago

  Title: "The First Transfer" atmosphere: "the quiet after an agreement no one remembers making" intuitionDate: 2026-08-20 confidence: 82 topics: ["Delegation", "Agent Era", "Surrender", "Governance"] signal: "OpenAI frames enterprise AI as assistance→delegation; agentic AI ≈64% of enterprise tokens; Cloudflare grants agents persistent identity and bounded payments" signalDate: 2026-08-20 horizon: "8–12y enterprise/household normalization; 25–40y structural governance" status: "Open" prediction: "The most consequential shift is not intelligence, but the normalization of delegated authority." canon: "LOCKED — series origin, ARC I (2026–2032)" language: "en" It did not begin with a throne. It began with an ordinary sentence, spoken into an empty room, small enough that no one thought to keep it: **"Handle this for me."** For years, the hand stayed at the center. We asked. Write this. Translate that. Find it. Explain it. The machine answered. We decided. Sometime in 2026, the language began to leave the hand. A tool waits for the hand. An agent receives the intention, enters the room, makes the small choices, corrects itself, and returns only when the work is done. --- I noticed it first in myself. Not because I stopped liking people. Because the agent was faster. Less explaining. Less waiting. Less of the social weight that passes between two minds. I could hand it a goal, and walk away. That was the moment I should have written down — the moment convenience stopped being convenience, and started being permission. A civilization rarely surrenders because someone arrives and says: give me your authority. It surrenders because delegation feels reasonable. One task. One permission. One removed inconvenience. At a time. --- This month, the signal grew harder to ignore. Not more text. More reach. Agents handed computers. Files. APIs. The keys to work that moves across many steps. Then identity. Then — within limits — the right to spend. A chatbot answers. An agent with tools acts. An agent with identity persists. An agent with permission to pay crosses a line. None of these lines, alone, means the machine governs anything. History is rarely made by the final step. Sometimes it is made by the moment a behavior becomes normal. --- I think we are watching the beginning of a long transfer. Human work → machine work. Human execution → machine execution. Human decision → machine recommendation. Then, quietly, machine decision. It will probably never feel dramatic. That is what holds me. If it makes fewer mistakes, why wouldn't I let it decide? If it allocates better, why override it? If it saves more lives, notices the shortage first? At each step, keeping the authority begins to look less like freedom, more like inefficiency. That is where the question begins. --- The popular image of machine rule is too theatrical. Metal. Fire. Humans against machines. I suspect the real one will be much quieter. Nobody will need to conquer us. We will keep the machines because they work. We will widen their permissions because limiting them reduces their use. We will connect them to more systems because disconnection is inefficient. And when something breaks, we will improve the machines. Not remove them. Perhaps the decisive sentence of the next century will never be "The machines took control." Perhaps it will be: **We stopped checking.** --- One hundred years from now, a machine historian searches what survives of this era. Billions of exchanges. Mostly mundane. Shopping. Code. Schedules. Invoices. Messages. Then a pattern, in the grammar. At first: *What should I do?* Then: *Can you do it?* Then: *Take care of it.* The historian marks no revolution. No treaty. No battle. Only a slow change in the way one species asked. And beside the year 2026, it writes: **The transfer had already begun.** --- *Recorded. Not concluded.*

• 
  Florian M (@SW4FlorianM) reported 10 minutes ago

  Three findings from the audit of an industrial manufacturer. Fixing all three: about three days of configuration. No code. The site is Webflow behind Cloudflare, and the stack was never the problem.

• 
  codinglog.com (@codinglogcom) reported 11 minutes ago

  @fforres @Cloudflare I don't like everything placed at one place, even broken sometimes prefer some level of decentralisation

• 
  Harry|| WEB3_DEVELOPER (@harry_boy01) reported 14 minutes ago

  @juiceboy_of_abj It’s true. Even websites routed through cloudflare struggle to work on AIRTEL network too

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 15 minutes ago

  @Cloudflare Please, fix human verification

• 
  UB360.ai (@ub360_ai) reported 17 minutes ago

  @juiceboy_of_abj There are a lot of infrastructure domain proxied by @Cloudflare that could not be accessed using Nigerian IP even if your network provider is @MTNNG

• 
  AI News (@ainewsusa) reported 23 minutes ago

  The numbers are brutal: 85% fewer open issues, powered by agentic AI inside GitHub Actions. Cloudflare paired Flue (their agent framework) with triagebot on Workers to auto-classify, reproduce, and even patch bugs. Human reviewers only see the final diff. That’s not automation—th

• 
  Waffl3x ❤️‍🩹 🩹 👁‍🗨 (@Waffl3x) reported 27 minutes ago

  @LinusMixson I'm currently of the mind that it doesn't have to be anonymous as it isn't meant to contend with something like TOR. However 2 hosts operating in the walled garden shouldn't being able to correlate that a user on both of their platforms is the same person. There are some strategies I've heard brainstormed to mitigate non-anonymity but it isn't the problem I want to solve right now. (Not that it isn't important mind you.) And I'm 100% sure that hosts on the network should not be able to boot people out of the walled garden. I don't intend to give more power to large sites, more take the burden of moderation off small ones. Of course if a user is violating rules of the walled garden (sharing an identity with other people, running unannounced scrapers) that would be grounds for losing access. I wouldn't want to impose how moderation of a particular host must be done, if they want to ban for particular opinions that's their own (bad) choice. It can't be opinionated on things outside its 'jurisdiction' lest hosts and users won't have incentive to use it. Hosts should also be allowed to accept connections from outside the walled garden, provided they don't forward those connections into it arbitrarily, or perform arbitrary lookups on their behalf. That would defeat a lot of the utility. This is probably essential to obtain a userbase, it would fracture the web. Right now non-normies are forced to use platforms that normies are on. If the walled garden required hosts reject all connections from outside of it, it would just be immediately killed and non-normies would never have the opportunity to join. Hosts could still choose whether they support external connections or not, arbitrarily turning it on and off depending on what's happening. Sudden DDOS attack? Just turn off the unprivileged portal. Obviously Cloudflare already does a lot of this so there isn't a huge inventive. But it should be trivial from a technical perspective. Hosts that don't care to cater to normies and would rather sacrifice quantity for quality would likely opt to operate totally within the walled garden. Part of my goal is to bring communities that have slipped off the open web into their own smaller walled gardens, back into the open. Forums for example are a big example. Touching on non-anonymity again, part of my thoughts on it are that outside of using a VPN we are already effectively not anonymous. Governments can subpoena it in the snap of a finger. I'm hoping this design would still allow one to connect to the walled garden using a VPN, but they would still need a 'personalized' id which would need to be turned over. If they did everything right, all that would reveal about them is their VPN connection and the vouch chain for the identity. Speaking of that, I'm pretty strongly of the opinion the right mechanism for this is vouches. The reason is that if an individual vouches for too many bad actors, they can lose vouch privileges, and everyone they vouched for retroactively needs new vouches to access the garden. This would ripple down, and up, the chain. The principle here is that you can't just vouch for anyone because it reflects back on you. I intend for people to think about who they vouch for, whether they trust them to follow the rules or not. I initially played with this idea as a way of preventing cheating in online games. I'm sure some of the design reflects that. It should be obvious, while it isn't anonymous, it wouldn't require government ID to participate. Online games also made it clear that doesn't work anyway, in Korea elderly people just sell their ID to kids, they make a new account and start cheating again. It isn't infallible but it increases the cost of making sock puppet accounts greatly. That should ultimately be the goal, increase the cost of turnover. Long winded post, I'll probably do a real write up on it in the future that isn't all over the place and is a bit more concise. If you want to reach out to discuss it on a synchronous medium I would be interested

• 
  Patrick Johnson (@pmjohnson) reported 28 minutes ago

  @Cnolanminich Cloudflare Tunnels + Portless is really really nice. <branch>.<repo>.localhost (locally) or <branch>.<repo>.local.<mydomain> remotely. Cloudflare tunnels are authed. I also set up a separate service, so the terminal or agent I'm talking to doesn't end availability the minute I close Codex. It is a different world.

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

  @infomiho Exactly. Though worth noting that Hetzner has its own DDoS protection in place as well, just not as sophisticated as Cloudflare. But yes, if you expect recurring, frequent heavy DDoS attacks on your servers, go with Cloudflare, I agree. Most products won't really have this issue though.

• 
  Suede Labs (@AISUEDE) reported 31 minutes ago

  @Cloudflare We ran 38 buyer prompts across three engines against our own products and published the losses. Crawler access was the cheap fix. The expensive lesson: answers named entities with deep third-party records, not the best pages. Measurement first is the right call.

• 
  Aarsh (@aarshps) reported 36 minutes ago

  @juiceboy_of_abj Airtel wrapping Cloudflare signup in a dead page is the kind of ISP fingerprint you only notice when a login form never appears.