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:

• 
  Gaurav Rai (@gaur_ai) reported 8 minutes ago

  There's a second problem underneath. Your robots.txt may not be making the decision. Cloudflare and Akamai rules sit in front of it. Cloudflare has a one-click Block AI Bots toggle that overrides everything below. Plenty of sites switched it on in 2024 and forgot.

• 
  Chirag Kulkarni (@chiraggkulkarni) reported 14 minutes ago

  We follow a 6-step framework to generate revenue for our $10M-$100M partners through AI Search There are 6 things we’ve found matter most. 1. Question mining Keyword research asks what someone types into Google. Question mining asks what someone actually asks ChatGPT or Google AIOs. The important part is going one step further. A long prompt gets broken into smaller searches (aka query fanout) before the model writes an answer. So the idea here is to understand those smaller searches too, not just the original question. We pull these questions from places like Search Console, People Also Ask, Reddit, Quora and customer conversations, then turn them into prompts we can actually track. The goal isn't to build a bigger keyword list. It's to understand the questions your buyers are already asking. 2. Answer tracking Once you know the questions that matter, track whether your brand actually appears in the answers. This is basically called the share of voice for AI search. On one healthcare SaaS account, 112 prompts produced 856 tracked responses across ChatGPT, Perplexity, Gemini and AI Overviews. The brand went from having no presence in one target topic to showing up consistently. This also lets you see whether visibility is actually changing over time. On another account, AI visibility increased 128% while LLM-referred views increased 229% over roughly four months. 3. Citation mapping Look at the sources AI search is already citing for your important questions. If the same 3-4 publications keep appearing, those are the sites worth getting mentioned on. We’ve seen this become much more important as Reddit's share of ChatGPT citations dropped from roughly 10-15% to around 2% on one account. Instead of trying to get mentioned everywhere, you can work backwards from the answers you actually care about. Find which publications are feeding those answers, then try to get your brand included in those specific places. 4. On-site content Your website still matters. The difference is that you need to answer the questions a buyer is likely to ask, including the follow-up questions, and make those answers easy to find. FAQs, clear takeaways and better internal linking can make the content much easier for a model to use. The interesting part is that some of the things Google no longer visibly rewards can still help AI systems understand a page. FAQ schema is a good example. It may not show up as a rich result anymore, but that doesn't mean that information is useless to an LLM. 5. Off-site presence Getting mentioned on the right websites matters more than simply getting mentioned everywhere. One men's grooming brand had a 24-backlink plan where every placement was tracked against the prompt it was meant to influence. The goal wasn't more links. It was getting mentioned in places that already showed up in the answers we cared about. This is where AI search starts to look a lot like old-school SEO again. There is roughly a 20% overlap between what ChatGPT surfaces and what ranks in Google, so the sites that already have authority in search often matter here too. 6. Test everything AI search changes too quickly to treat any tactic as permanent. One account had Cloudflare silently blocking AI crawlers from parts of the site due to which the crawlers simply couldn't reach the content. We've also seen teams block traffic because they thought it was low-quality bot traffic, without checking whether some of those bots were actually AI crawlers. You can accidentally block the systems you want to be able to read your site. That's why I think the biggest shift isn't "how do we do SEO for AI?" It's understanding that AI search gives you a new set of things to measure, investigate and influence.

• 
  Ben (@sosumisubmarine) reported 17 minutes ago

  @htmx_org I’m shifting my strategy thusly: Only purchasing lower-end consumer Mac hardware that I don’t mind upgrading (iMacs, MacBook Airs) that connect to storage and services run on a cobbled together Linux box in my house. Everything I need, Postgres, mssql, plex, file storage, next cloud, LLM services, forgejo… I’ll either do ssh tunneling or set up Cloudflare tunnels for remote access. I’m cobbling together such a system right now, partially from old PC parts I already had sitting around. A quad-core ryzen box with DDR4 is more than enough for any and all of this, and will be for a long time. I still get the userland and mainstream support of macOS, while I can grow, mod and cobble together commodity HW. The central idea is: data portability between systems. Then your userland and desktop environment starts to matter less.

• 
  Dmonty (@Dmonty28516998) reported 20 minutes ago

  @jeffdafo @AdamRackis You know who CAN imagine that curve in traffic? Cloudflare. Akamai. Fastly. AWS. GCP. And very ironically, Azure. We have an entire industry built around turning explosive growth in traffic, storage and compute into a capacity-planning problem. They all seem to be doing just fine. Software infrastructure is, famously, somewhat easier to parallelize than pregnancy.

• 
  Rahul Karajgikar (@Road_Kill11) reported 21 minutes ago

  most agent harnesses are not built to run in the cloud. this is why we rebuilt dexto from the ground up. we had a coding agent CLI similar to claude code, dexto a long time ago, but we were more interesting in making agents run in the cloud on a persistent computer. we started off by running dexto inside a cloud sandbox (e2b). this had some problems: 1. the runtime is heavily coupled to the sandbox. any sandbox outages or issues would kill the agent and were very hard to recover from. 2. credentials. we needed to give dexto access to many external integrations and tools. but we also needed to ensure that credentials weren't readable by the agent. we solved this by making an egress proxy (adds credentials on top of outbound requests from the sandbox so agents never see them). but this was painful and for every external integration we needed to maintain some code 3. price. we realized that for many of our use-cases (content creation, research, monitoring automations), the agent actually didn't need to read or write files. this pushed us to think that maybe it would be better if dexto ran OUTSIDE the sandbox, but could use the sandbox whenever it needed to write a file or run some command on the computer. while researching how agents could run outside the sandbox, i was very impressed with cloudflare's primitives. durable objects and workflows seemed extremely promising for what we needed and had good pricing. so i tried to deploy dexto on cloudflare. while doing this, i realized that our entire harness was designed assuming the agent would be running on a persistent machine and stored everything in-memory. this wouldn't work in a serverless environment. and interestingly, pretty much EVERY open-source harness you see (codex, opencode, etc.) has this same problem. so we redesigned our core primitives from the ground up, with the goal that these primitives should be able to power a local cli, webui, or desktop app, but ALSO be able to run on any cloud environment (cloudflare, railway, vercel, etc.). we changed every single primitive we had in dexto/core (storage, approvals, system prompt, skills, compaction logic, model registry, tool implementations) to be injectable from consumers so that they could define exactly how they needed dexto to run based on the required environment. while core just defined the shapes and the agent loop logic. now we're running dexto cloud fully outside the sandbox on cloudflare's stack, which has some amazing advantages: 1. dexto gets a persistent cloud computer with a browser and a terminal - but it only uses it when it needs to. this means that for requests that don't need a sandbox (like generating a video, or searching the web), our users spend $0 in compute costs. 2. the compute is now replaceable. it's not really an issue if we the sandbox has issues, or gets sandbox gets corrupted. we just replace the sandbox and move on. and only file writes/reads really are affected. 3. the agent loop is fully durable and resumable at any point, and don't cost extra while waiting. this means that dexto can wait 365 days for an approval, costing you no extra money. it also means if dexto fails something at any point, it can easily resume from the last safe point instead of having to re-run everything from scratch again. 4. credentials are easy! since the agent runs on a serverless environment, we don't need an egress proxy for 99% of normal requests. credentials never live on the sandbox, agents just hit internal apis and the credentials are managed separately so agents never see them. now we only use an egress proxy for a few specific CLIs that run on the sandbox (gh cli) if you're interested to learn more about harness design, and maybe see some cool demos and feature releases, follow along!

• 
  Rock (@Rock4754) reported 23 minutes ago

  @retiredbhondu Go to ur network settings and in DNS-> Private DNS hostname add -> 1dot1dot1dot1.cloudflare-dns. com *Remove the space before .com when entering it

• 
  Waffl3x ❤️‍🩹 🩹 👁‍🗨 (@Waffl3x) reported 23 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

• 
  Mike Choi (@guard_if) reported 25 minutes ago

  if you want to run a series A startup: Rails = the entire app. Postgres = source of truth. ClickHouse = analytics. Kafka = getting one into the other. (MSK) Sidekiq = everything async. ECS + EKS = deploys your own models. (GPUs, lol) Terraform = all of it, in code. Grafana + Sentry = knowing what broke. Statsig = flags + experiments. Stripe = money in. Mercury = money out. Loops = email. Intercom = support. Cloudflare = DNS. Vercel = marketing website. Linear + Graphite = shipping. Claude = coding / artifact generation total monthly cost: definitely not $20.

• 
  Anshu (@101xanshu) reported 28 minutes ago

  Dear @Cloudflare, hire me. I have a growing list of Wrangler issues on Windows/WSL that I'd very much like to fight professionally 😭

• 
  Shan Ali🇵🇰 (@shanaliniz) reported 30 minutes ago

  Dear Vibecoders, I need some help. I want to turn my Windows laptop into a hosting server. I want to host my webpages, such as "index.php" and "index.html", directly from my laptop and then point my domain to my laptop’s IP address. I also don’t want to depend on Cloudflare.

• 
  Alex Garcia (@alex_here_now) reported 30 minutes ago

  I'm having a cloudflare issue I think I should speak to a cloudflare person about. What's up: I built an entire setup in my personal gmail before getting my work email. I'd like to transfer basically everything to the work email. This feelss... delicate.

• 
  Ragnawr.btc 🌍☮️ (@findingragnawr) reported 31 minutes ago

  If you’re building with AI and you use all the best free services, you may have been noticing a trend of late, or I have enough that I’ll tweet about it to the ether. Agent consumption outscales human interest. That’s basically the issue. Your free versions won’t remain free much longer. Supabase? Pro version. Cloudflare? X402 paywall on hosted pages. Maybe I’m wrong but I can say that the era of services of services that make other services easier to use is upon us. Convenience era. Pay for it.

• 
  alwinsDen (@alwinsDen) reported 32 minutes ago

  @sudo_overflow @Cloudflare it would be ironic if this API to check bill itself might be getting billed. never ending cycle.

• 
  Jonathan (@jonniefive) reported 32 minutes ago

  I'm getting so much AI / bot traffic on my Shopify store that I have no idea what the conversion rate is anymore. I tried using @Cloudflare with O2O and AI Labyrinth, bot blocking and a bunch of WAF rules but the AI bots keep coming and inflating my session data. Anyone at @liam_at_shopify can help? Screenshot shows sessions today so far - I don't have a Chinese locale and don't ship to China.

• 
  IdeaPlan.io (@ideaplanio) reported 34 minutes ago

  Cloudflare says most web requests are now automated, not human. Your analytics can't tell the difference. Your activation rate, bounce rate, and last A/B test winner all include traffic that was never going to convert. Segment agent from human before you trust the number.