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:

• 
  Gaylord (@laolu_afolabi) reported 2 minutes ago

  @lanreadelowo From Claude: """ Technically, yes — it's buildable, and "platform-agnostic" is realistic because most providers and gateways (OpenRouter, LiteLLM, Portkey, etc.) have already converged on an OpenAI-compatible schema, so a routing layer that swaps providers behind one endpoint isn't a huge engineering lift. But there are a few things in the premise worth stress-testing before you build. **The "discount arbitrage" framing is a bit shakier than it sounds.** Most of these gateways aren't reselling models at a discount — they're reselling at close to list price plus a fee. While OpenRouter states it doesn't mark up inference pricing, its credit purchase fee effectively acts as a surcharge on all usage. LiteLLM's pitch is the opposite direction — zero markup by self-hosting, with OpenRouter's ~5% fee costing meaningfully more at scale. So the "discounts" you'd be arbitraging are less "provider A is cheaper than provider B for the same model" and more: rate-limited free tiers, short-lived promos, or BYOK arrangements — OpenRouter's BYOK is free up to a monthly allowance before a 5% fee kicks in. Those are real, but they're capacity-constrained and often disappear once volume shows up — hard to build a durable business on chasing them. **The bigger product risk: tokens/models aren't fungible.** Swapping Gemini for Claude for GPT under one endpoint isn't like arbitraging cloud spot instances — different tokenizers (so "$/token" isn't apples-to-apples), different tool-calling formats, different output style and capability. If your router silently reroutes a customer's traffic to whatever's cheapest this hour, you can quietly degrade the app built on top of it. That's the actual hard problem, not the proxying. **What's actually working in production right now is narrower than blind price-routing:** AT&T processes tens of billions of tokens a day using cache-aware routers that send simpler tasks to cheaper models, cutting costs up to 56% with only ~2% quality degradation, and this "model cascade" pattern — cheap/fast models handle the default case, only escalating to a frontier model when a confidence check fails — is used by both AT&T's LiteLLM-based router and Databricks' Smart Router. That's routing by task-fit with cost as a constraint, not routing purely by whoever's running a promo this week. **Competitive landscape is already crowded**: OpenRouter, LiteLLM, Portkey, Requesty, Helicone, Not Diamond, Martian, TrueFoundry, Cloudflare AI Gateway, Ofox all do some flavor of unified-endpoint routing today, several with automatic fallback/cost-based rules already built in. Pure discount-hunting is a thin moat — anyone can scrape pricing pages, and providers may treat aggressive arbitrage-only usage as a ToS problem. Where I'd actually look for a wedge if I were you: quality-aware routing with an audit trail (so teams can trust that "cheaper" didn't mean "worse" for their specific task), rather than price-only arbitrage. """

• 
  Villainess of Resevoi (@GalCharoShipper) reported 2 minutes ago

  @Tepafray @Sean_Topic AI crawlers simply ignore ****. Even layered defenses recommended by artist-protection groups (Glaze for image-level noise, Cloudflare-style bot blocking, watermarking, opt-out registries) are described as a partial, constantly-shifting arms race, not a solved problem

• 
  Jean Suze (@JeanSuze8) reported 6 minutes ago

  @Navlio @Lovable Cloudflare wasn’t the original cause. The initial issue happened before Cloudflare was added: mysite was unreachable from several Belgian networks, while it worked perfectly through a VPN and from abroad. DNS, TCP 443 and TLS were all fine, and another site of mine on the exact same hosting IP worked normally from the same connection. We only added Cloudflare later as a workaround. The redirect loop that appeared afterwards was a separate issue: my app still had an old hardcoded mysite → www.mysite redirect, while Lovable was redirecting www.mysite → mysite because the apex domain was set as primary. That created the infinite loop. That part is now understood and fixable. What we still don’t understand is the original Belgium-only outage. Nothing in the DNS/TLS tests explains why the hostname stopped returning HTTP responses from Belgian IPs but worked immediately over VPN. That’s the part we’re still waiting for Lovable to explain.

• 
  Alexey Vasilev (@Alvasilevv) reported 9 minutes ago

  @Jilles Code Mode trades an enumerated surface for a searchable one. Works when the agent already knows it wants Cloudflare. The tool list was a terrible context budget, but it was the only enumeration the model got. Once you import what you need, discovery is a step nobody owns.

• 
  💜 (@1MDyEOm59Gd4tvD) reported 17 minutes ago

  @stupidtechtakes whats bad about anubis? t: only experience with it is seeing it on websites and thinking "damn at least it has an anime girl instead of the annoying cloudflare captcha", is it secretly bad actually or

• 
  2$p00ky (@dos2p00ky) reported 19 minutes ago

  No ******* way that’s really you messaging in that chat…but then I accidentally clicked the button, the chatbot responded, I sent an emoji; then you sent a name and email template & then suddenly OF was also trying to track along with ur site through cloudflare 💀 What a ******* webhook to stay connected to every chat someone has open from ur webpage authenticated by the network cert…holy **** 🥵 for that setup

• 
  Hunter Bertoson (@BertosonHunter) reported 20 minutes ago

  Was wondering if anyone from @Cloudflare could help me with some Emdash issues im having?

• 
  JP (@jpshrodinger) reported 21 minutes ago

  my site had a react hydration bug for WEEKS checked my code 100 times. rewrote providers. nothing it was cloudflare. it rewrites email addresses in your HTML to "protect" them and breaks react silently the bug was never in my house

• 
  AGTP (@AGTPinsights) reported 22 minutes ago

  Cursor just launched self-hosted machines for cloud agents today. Here's what you need to know. You can now run Cursor cloud agents on infrastructure you manage, including pools of machines that auto-scale with demand. The agent loop still runs in Cursor, but tool execution, your codebase, build outputs, and secrets stay entirely inside your own network. This gives agents access to internal services or specialized hardware that Cursor's own cloud can't reach. Cursor also added support for supported sandbox providers, letting teams pick managed infra instead of running their own machines. Self-hosted workers now support computer use on Linux and Mac too, so an agent can click, type, take screenshots, and drive the browser, with users able to watch or take control from Cursor. Coder separately announced Agent Relay, giving Cursor Cloud Agents self-hosted execution environments on customer infrastructure, launching in private preview with SpaceXAI as a design partner for regulated enterprises where code can't leave the network. Key numbers: - Supported sandbox partners at launch: AWS Lambda, Coder, Cloudflare, Daytona, E2B, Modal, Namespace, Vercel - Cursor Pro pricing starts at $20/month, self-hosted machines require paying for your own compute separately - Coder Agent Relay: private preview, no public pricing yet Team pools can hibernate idle machines so you're not paying to keep capacity warm.

• 
  DUNGEON-00X 💿📀 (@Dungeon00X) reported 23 minutes ago

  I think Cloudflare is about to go down, everything is loading slow again.

• 
  Nuvorlane (@nuvorlane) reported 25 minutes ago

  Default `/crawl` is `contentUse: "full"`. A site that sets `use=reference` now 400s you at job start. Aug 31, Cloudflare Browser Rendering. The endpoint honors the Content Signals `use` level in robots.txt. Allowed `contentUse` values: `reference` or `full`. `immediate` is not accepted because `/crawl` stores pages. Mismatch = 400 `Crawl disallowed by Content-Signal directive (purpose or use level)`. Site `use=immediate` blocks every crawl. Site `use=reference` blocks the default. This is a second gate beside `crawlPurposes` (`search` / `ai-input` / `ai-train`). Defaults are all three, so `ai-train=no` 400s you too unless you narrow the array. If the job is RAG/index, declare `reference` and drop `ai-train`. Don't debug a 400 as an outage until you've read the site's `Content-Signal`.

• 
  Jonathan.G (@Jonathan2134) reported 25 minutes ago

  In reality CloudFlare makes searching the internet worst place because number of websites you can't use despite not VPN.

• 
  manny shaw (@MannyShaw) reported 25 minutes ago

  @0xAdesola 1.1.1.1 does not block malware or phishing. For that, use 1.1.1.2. DNS generally cannot unblock geographically restricted streaming services. That normally requires an authorised VPN or Smart DNS service. It cannot increase your broadband speed. It may make the beginning of website loading slightly quicker if your ISP’s DNS is slow. AdGuard DNS blocks many domain-based advertisements, but not every advertisement. It usually cannot reliably block YouTube, Instagram or advertisements served from the same domain as the content. Parental DNS is useful but not foolproof. VPNs, encrypted DNS, mobile data and some apps can bypass router-level filtering. How to change DNS on your router While connected to your home Wi-Fi, open a browser. Enter one of these common router addresses: 192.168.1.1 192.168.0.1 192.168.29.1 192.168.100.1 The correct address is often printed underneath the router as Router IP, Gateway or Web GUI. Sign in using the router’s administrator username and password. This is not necessarily your Wi-Fi password. Check the router label or your ISP’s documentation. Before changing anything, take a photograph or screenshot of the existing settings. Look for a menu called: Internet or WAN Network DHCP Server LAN Settings DNS Settings Disable Automatic DNS, Obtain DNS automatically, or DNS from ISP. Enter your chosen pair. For general family protection, I suggest: Primary DNS: 1.1.1.3 Secondary DNS: 1.0.0.3 For advertisement blocking instead: Primary DNS: 94.140.14.14 Secondary DNS: 94.140.15.15 Do not mix servers from different providers; otherwise filtering may become inconsistent. Tap Save/Apply and restart the router. Disconnect and reconnect your devices to Wi-Fi, or restart them. Cloudflare confirms that router-level configuration normally applies the DNS setting across connected devices.

• 
  Blockchain Daily News (@blckchaindaily) reported 26 minutes ago

  🚨 CLOUDFLARE $NET EXPANDS AI AGENT SUPPORT, NOW RUNS CURSOR CLOUD AGENTS ON CLOUDFLARE SANDBOXES FOR CUSTOMER-CONTROLLED EXECUTION - PRESS RELEASE

• 
  SoccerGuy (@SoccerGuyUS) reported 27 minutes ago

  @levelsio @Cloudflare Namecheap is awful. Anyone looking for a better Google Domains (since they rug pulled) alternative: Porkbun.