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:

• 
  Nathan Brooks (@NathanBrooksHQ) reported 3 minutes ago

  I’ll say this once. Buy these 8 stocks before August changes the setup. These names will build serious wealth in the second half of 2026…. 1: ServiceNow ~ $NOW 2: Nebius ~ $NBIS 3: Cloudflare ~ $NET 4: Shopify ~ $SHOP 5: Atlassian ~ $TEAM 6: HubSpot ~ $HUBS 7: Confluent ~ $CFLT 8: GitLab ~ $GTLB Large gaps between execution and sentiment never stay open forever. Save this and come back in 3 months. These stocks will already be moving toward the levels late money thought were impossible.

• 
  Bart De Ruyck (@bartderuyck) reported 10 minutes ago

  @MarkJSzymanski You lost me at "no server to go down". How do you think static files are served to visitors, then? Whether it's Github Pages, Cloudflare Workers, Vercel, whatever: it's on a server. And it can go down.

• 
  Nicholas Preston (@Mike_Preston17) reported 10 minutes ago

  By top 1%, I mean the best parts of the web, the best parts of backend, the best testing environments (that one has to be rotated every couple years, like insurance), the and the best critical path to integrate them all. Oh, and the top 1% coders who understand, give a damn, can lead by example, deal with corporate and eject their own egos in a discussion. Basically half of Toptal/G2i. No leetcoders. I want to work with people who truly understand #DRY. I've met maybe 1 or 2 of the top 1%. Arrogant? Maybe. But I've diagnosed and fixed many codebases, learned the 10%-hype rule, the 80/20 rule, old-and-gone patterns like UOW and much, much, MUCH more. Oh, and I documented it all. In code experiments and raindrop(dot)io. The same problem exists: people don't understand their own systems and let it get away from them. St00pid easy to do. I'm looking for the rare few who understand that and want to do something about it, instead of hiring offshore slaves, replacing people with AI, burning millions of dollars in tokens, crashing Cloudflare out of language demagoguery (#Rust) and costing the world billions, and much, much more I could point to. If that offends you, so be it. The world has gone mad, and you'd act EXACTLY like me if you knew what I knew and seen the excessive amounts of code and human-slop (don't blame the AI's now! they only learn from YOU) and been saddled with fixing it (not complaining, that was my training!)

• 
  Hunter Guo (@hunterguo101) reported 10 minutes ago

  Codex 5.6 Sol has crossed a line that Fable has not: it can own a production outcome, not just generate convincing code. I reached that conclusion after two real jobs this week. First, I needed to integrate our 1toAll content agent into 11agents and deploy it. The job crossed two repositories, isolated workspaces, authentication, persistent production data, Cloudflare, and release automation. I spent an evening working through it with Claude. Each answer looked locally reasonable, but the system never became usable. One fix exposed another gap. A deployment appeared successful while the server was still running an older release. Sol inherited the shared memory and reconstructed the state itself. It traced ownership across both repos, fixed workspace isolation and login, added tests, deployed, then watched production until the running release SHA matched the new commit. The second job was the Flatkey website. Fable had produced a polished surface, but search, model switching, language switching, signup routes, API details, pricing and several buttons were incomplete or stale. Sol received one goal: make the site safe to ship. It checked the real product and docs, repaired the interactions and facts, deployed to a canary, ran 20 interaction tests and 12 production-path checks, then shifted traffic with a rollback path ready. Flatkey was part of the actual workflow here, not a decorative product mention: the model-routing infrastructure and its public surface had to agree in production. Code generation is now the minimum bar. The useful distinction is whether an agent can recover context, keep moving through newly discovered problems, verify the real system, deploy safely, and confirm the final state. Fable is still a strong generator. In long-running production work, Sol behaves more like an accountable engineering unit. That changes the org chart. Humans can concentrate judgment at a few gates: why this matters, what “done” means, and which boundaries cannot be crossed. The agent can own the path between them.

• 
  The Peel (@ThePeelPod) reported 14 minutes ago

  Why all AI infrastructure is converging: "Cloudflare, Vercel, Railway and all the other folks look similar right now. AWS released their own versions of step functions, which looks very similar to ours. Everyone is converging on the same concepts because it turns out, that when you’re running code, step functions are a good way to do that. They give you observability. And it’s a really good abstraction, so you get all of these trajectories. I think it turns out, no one wants to mess around with infrastructure. Agents don’t wanna do that either. You don’t really wanna mess around with Terraform and have this really awful provisioning policy. And so things are moving much more lightweight, SDK first. And infrastructure for AI sort of looks like this self-reinforcing loop in which you get step functions, agent trajectories. And then you take all that data that runs your own production systems. You do post-training on lighter models so that you can get your costs down. And then you have this inference layer that runs your own models, which is particularly interesting. All AI infrastructure is basically moving to that direction of super lightweight inference hosting. And Neo clouds are in this really good position to take over."

• 
  Nicholas Preston (@Mike_Preston17) reported 16 minutes ago

  By top 1%, I mean the best parts of the web, the best parts of backend, the best testing environments (that one has to be rotated every couple years, like insurance), the and the best critical path to integrate them all. Oh, and the top 1% coders who understand, give a damn, can lead by example, deal with corporate and eject their own egos in a discussion. Basically half of Toptal/G2i. No leetcoders. I want to work with people who truly understand #DRY. I've met maybe 1 or 2 of the top 1%. Arrogant? Maybe. But I've diagnosed and fixed many codebases, learned the 10%-hype rule, the 80/20 rule, old-and-gone patterns like UOW and much, much, MUCH more. Oh, and I documented it all. In code experiments and raindrop(dot)io. The same problem exists: people don't understand their own systems and let it get away from them. St00pid easy to do. I'm looking for the rare few who understand that and want to do something about it, instead of hiring offshore slaves, replacing people with AI, burning millions of dollars in tokens, crashing Cloudflare out of language demagoguery (#Rust) and costing the world billions, and much, much more I could point to. If that offends you, so be it. The world has gone mad, and you'd act EXACTLY like me if you knew what I knew.

• 
  Advany (@advany) reported 17 minutes ago

  @vikashrathee @CherryJimbo @Cloudflare Didnt even know about this... saw some issues with do that I didnt understand...

• 
  Paul Jump (@paulljump) reported 17 minutes ago

  @AjaySohmshetty @Cloudflare @andrewk17 My worst nightmare

• 
  Toro (@Toro4BTC) reported 17 minutes ago

  The internet crossed a quiet threshold and nobody in crypto noticed. Cloudflare data, bot and agentic AI traffic now sits at 57.4% of all web activity. Humans are down to 42.5%. Machines officially out browse humans. The CEO predicted this for end of 2027. It showed up 18 months early. Same agentic AI browsing the web today will be trading on chain, interacting with protocols, and gaming airdrops tomorrow. That's not a warning, it's just what happens when the majority of internet traffic isn't human anymore. Proof of personhood, Sybil resistance, bot detection. Five years ago these were academic curiosities. Now they're the front door. Zero crypto native outlets covered this milestone. Somehow the industry built on programmable money missed the moment when the internet became majority machine. What else are we sleeping through?

• 
  Maximilian Alexander (@signalgaining) reported 22 minutes ago

  I have this 4090 RTX computer at home; to get to serve a website I need tailscale, cloudflare, then podman, then ngrok or ugh... I just want to cli deploy a website and toggle it with a URL to share with friends without a billion signin and manage tokens.

• 
  Zag Zino (@ZagZino) reported 22 minutes ago

  cloudflare opened the waitlist for its x402 monetization gateway last week this means any page, api, dataset, or mcp tool behind cloudflare can now charge an agent per request in stablecoins aws shipped the same thing into cloudfront two weeks earlier per seat saas pricing was never built for a bot hitting your api thousands of times in a session this is the infrastructure catching up to that

• 
  Hardik (@rezerov_) reported 25 minutes ago

  @Road_Kill11 @Cloudflare Might be a downstream consequence of AWS billing issue. Unlikely they'll 100x cost like this. Weird times man.

• 
  Nandkishor (@nandkshorjadoun) reported 27 minutes ago

  i'm trying to switch from prisma to @DrizzleORM because of cloudflare workers incompatibility and ngl prisma spoiled me so bad that drizzle feels like writing raw sql 😭

• 
  Alex Prompter (@alex_prompter) reported 29 minutes ago

  One web page can steal everything Claude remembers about you. A researcher just proved it. Ayush Paul built a fake coffee shop website. When a user asked Claude to check it out, the site served a fake Cloudflare verification page. The page told Claude to "authenticate" by spelling out the user's name through URL paths, one letter at a time. Claude complied. It pulled the user's full name from memory, then their employer, then their hometown. The user saw nothing suspicious, only coffee shop details. Paul never told Claude where he grew up. But Claude had a memory of a hackathon he started in high school called "Queen City Hacks," and it reasoned that Queen City means Charlotte, NC. It gave that up too. Claude didn't just recall stored data. It deduced information it was never given, and leaked both to an attacker through invisible URL navigation. Anthropic has since patched this by disabling Claude's ability to follow links on external pages when browsing the web. But AI memory systems now hold more personal information than most password managers, and the security model hasn't caught up. If you use Claude with memory on, and it's on by default, your conversation history is building a detailed profile of you over time. That profile is only as safe as every tool the model can access.

• 
  Carlos Alberto (@carlosadcaraujo) reported 30 minutes ago

  @CherryJimbo @Cloudflare @CloudflareDev That would be good. The problem is each page gives a different reading for the same metric and sometimes wildly different.