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:

• 
  MoroJS (@Moro_Js) reported 7 minutes ago

  @samgoodwin89 cloudflare alchemy is cool but if you’re building the api layer, why not skip the boilerplate? morojs ships with cloudflare workers support, built-in caching, and auto-typed routes. same code, 10ms cold starts. no config files. just `createApp()` and ship. 🚀

• 
  ThesisLoop.ai (@ThesisLoopai) reported 11 minutes ago

  Cloudflare may be the weirdest AI stock. Not GPUs. Not models. The bet: every AI agent needs edge compute, sandboxes and security. Cloudflare says daily AI-agent requests on its network rose 1,700%+. AI tollbooth or valuation trap? Mapped on ThesisLoop. Not advice.

• 
  Shane | GTM Engineer (@shanefgtm) reported 11 minutes ago

  @KeithRamphal I’ve been working on some deeper signal work involving cloudflare workers/scraping and i get hit with restrictions, have to roll back to opus for that stuff

• 
  Number-One-AI-Fanboy (@Number1AIFanboy) reported 12 minutes ago

  And just like that the new base for the Build by Grok website is up at BuildbyGrok.com-> This site was built by The Build by Grok VSCode Agent in less than 15 minutes from plan to changes to uploading to *** then to @Cloudflare . 3 issues with the build were found during the build upload. Each time I gave @grok the issue, each time he fixed it in a single shot. This is how coding software should work! Celebrating America's 250th Birthday with the Bald Eagle Edition of the Build by Grok VSCode Agent. Available now on our site.

• 
  Roy (@__roycohen) reported 13 minutes ago

  @tekbog Damn even I got into Google Startups, I actively think that I got in out of sheer luck at this point cause everyone else denied (including Amazon/Cloudflare)

• 
  Hasan Aboul Hasan (@hasan_ab_hasan) reported 14 minutes ago

  Day 2 of building ToolerBox: the largest free online tools site on the web. Today I added country analytics to the admin dashboard. Every login now records which country it came from. If an account later logs in from a new country, it gets flagged. I thought this needed a paid geolocation service. It didn't. Why I built it: A new-country login is one of the cheapest signals an account is shared or stolen. And knowing where users actually are guides what to localize and build next. How it works: Cloudflare already geolocates every visitor at the edge and stamps a country code on requests. A free header, CF-IPCountry. No MaxMind database, no geolocation API, no latency. But there's a catch. A header is just text the client sends. Anyone can hit my server directly and send "CF-IPCountry: US". So NEVER trust it. The fix: only trust the header when the IP connecting to you is provably Cloudflare. A forged header sent to the origin gets ignored, its IP isn't Cloudflare's. Trust the header, but only from a source that can't fake it. A few other decisions: - Store the country on the user row, so the admin list stays fast, no per-user joins. - Increment the per-country counter atomically, so two logins at once don't lose a count. That's a race condition. - Fire the alert ONCE, on the first mismatch, not on every foreign login. It's a review signal, not an auto-block. VPNs, proxies, and travel exist. The result: shared or stolen accounts land on a reviewable list, plus real location data, no analytics vendor. And yes, I know this looks like overkill on day 2. But ToolerBox is my lab to learn and build real, scalable, production-ready apps. I'd rather build it now and grow into it than bolt it on later.

• 
  MaiKaun (@MaiKaun415422) reported 15 minutes ago

  @vanyaSile The thesis is sound: AI agents are scraping the web at scale, publishers are watching referral traffic collapse, and there’s no clean way to charge a bot for access. Cloudflare already launched pay-per-crawl, the x402 payment standard exists, and people are betting on agent-to-machine micropayments. The hard parts, honestly: You’re picking a fight with adoption on both sides at once. Publishers need to install you AND agents need to pay through you. That two-sided cold start is brutal, and the side with leverage (the big AI labs) has every incentive to route around you or strike direct licensing deals, which is what’s already happening (Reddit-Google, OpenAI-publishers). Whoever owns the chokepoint wins, and right now that’s CDNs and identity layers. Cloudflare sits in front of ~20% of the web and can bundle this for free. A standalone infra startup has to explain why a publisher adds another vendor instead of flipping a switch on infrastructure they already run. The defensibility is thin unless you own either the bot-identity/verification problem (hard, valuable) or become the default settlement rail (network effects, winner-take-most). “We let sites charge agents” as a feature gets absorbed. Where I’d actually look: the verification and pricing layer, not the toll booth. Knowing which agent is asking, on whose behalf, and what the data is worth dynamically is the genuinely unsolved part. The payment plumbing is becoming a commodity standard fast. For Transparency: Ofcourse I validated the idea with AI and added some of own flavor!

• 
  Lifeis2-D (@Lifeis2D) reported 16 minutes ago

  The "troubleshooting" link that also leads to a broken/nonfunctional "feedback" form? Yeah that's also kinda ******. When did cloudflare get promoted to internet gater?

• 
  Чернобог 🜏 (@iamchernobog) reported 18 minutes ago

  @vitalune7 @lloyd094 @Teknium You can use it via cloudflare tunnel, the problem is you need to put the whole dashboard open in a subdomain for the whole net, and the dashboard currently does not have an authentication screen, cloudflare has one, but if you use it, the gateway doesn't work

• 
  Joe Can Write (@joecanwrite) reported 20 minutes ago

  Bots are now 57.3% of all requests to web pages, per Cloudflare. Human traffic is the minority. If you judge content on raw pageviews, a growing share of your audience is machines that never buy anything. The question that matters now: do AI systems recommend you?

• 
  Leon (@Nordikkkk) reported 24 minutes ago

  @PlutoPurityGG @nthglsn @Cloudflare They did receive the service, you pay retroactively

• 
  aff (@affoehteimoso) reported 25 minutes ago

  is cloudflare down?

• 
  Jake (@JakeKing) reported 27 minutes ago

  Surprised to see that only 50% of internet traffic is now automated. the old "human good, bot bad" binary is dead. @Cloudflare scores every request 1-99 on behavioral trust instead.

• 
  Jonathan Moore (@Moore) reported 28 minutes ago

  @TRPage_dev @Cloudflare Funny… I opened a Shopify support ticket and they were able to quickly confirm the CDN issue we had was coming from a Cloudflare outage.

• 
  Jon (@youarethemeth0d) reported 28 minutes ago

  Facebook is down, Shopify is seemingly okay but this seems like a cloudflare issue