Cloudflare status: hosting issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Cloudflare reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Cloudflare users through our website.

• Cloud Services (43%)
• Domains (21%)
• Web Tools (14%)
• Hosting (14%)
• E-mail (7%)

Live Outage Map

The most recent Cloudflare outage reports came from the following cities:

City	Problem Type	Report Time
New York City	Cloud Services	18 days ago
Los Angeles	Cloud Services	19 days ago
Paris	Cloud Services	1 month ago
New York City	Hosting	1 month ago
Manchester	Domains	2 months ago
Angers	Cloud Services	2 months ago

Full 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:

• 
  spencer :) (@spencerpauly) reported 20 minutes ago

  This morning I asked codex: "move my site to vercel to save costs". It asked me to login to namecheap for my dns records. "Ohh, move the nameservers to cloudflare too". 1 hour later - both are migrated.

• 
  System11 (@System11b) reported 21 minutes ago

  @suddendesu @CuttingRoomWiki I can understand the motivation, I'm having to pay monthly for Cloudflare due to AI scraping. The traffic was killing the forum server, load average so high it was taking minutes to log in and check top. I would ban LLMs from the public internet at this point. Perhaps even send a terminator back in time to fix this.

• 
  Engr Mustapha (@_Engr_Mustapha) reported 23 minutes ago

  @juiceboy_of_abj No wonder I wanted to work on one website after buying domain I thought cloudflare was down 🫠 Am using other company for it

• 
  NorthernChuck (@FroidEtCold) reported 27 minutes ago

  Ported Buzz from Rust to C and called it Hush. Changed the User Interface around and started bolting on pieces. Built using @tetsuoai's writing legible C skill. Included a STUN/TURN server in C as well. The idea being that you can deploy this thing and use it to pin down media paths and enable voice/video. Will be adding support for Cloudflare TURN, eventually

• 
  Ryan K 🌥 (@Yank) reported 28 minutes ago

  @steven_levey @Cloudflare Sorry to hear about the issues. If you can submit a ticket and share the ticket number with me I can try to make sure the right people see it.

• 
  PangeaVPN (@PangeaVPN) reported 28 minutes ago

  @HorluwarhArmani @SirAlexanderrr if it's the ISP breaking that page rather than Cloudflare, you need something the network can't pick out. Pangea tries five stealth transports in order, VLESS+Reality first, so one being blocked isn't the end of it. windows/mac, ios via shadowrocket. five days free.

• 
  🫧༺꧁𝐄𝕏_𝐇𝐞𝐫꧂༻🫧 (@Miragea_S) reported 28 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.*

• 
  Gneaus (@legibitiquas) reported 29 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

• 
  Fern (@Ferrrrrnnnnnn) reported 29 minutes ago

  Hey @AMCTheatres @Cloudflare, might be smart to fix your dogshit rate limiting before you drop tickets for the biggest movie of the decade

• 
  Chirag Kulkarni (@chiraggkulkarni) reported 29 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.

• 
  Paul 🇷🇴🇨🇴 (@hasieratik) reported 30 minutes ago

  @TeeDevh good will gestures matter, a lot; obviously not your scale, but Cloudflare covered a $100 bill that I made because I was stupid and I went on X and Reddit and praised them and their support team :)

• 
  Sina Meraji (@sinasanm) reported 30 minutes ago

  changelog v0.98.0: replaced the onboarding (which previously required you to manually type in your Cloudflare account ID and create an API key and select permissions one by one) with "login with Cloudflare," which creates the API key and selects the right permission for you. a few steps less to get started. npm i -g kimiflare

• 
  James McHugh (@Jamesmchugh) reported 31 minutes ago

  @nickgraynews @bot Have you had any issues with your grokbot hitting Cloudflare captchas? Mine seems to get stuck quite frequently and then just gives up without telling me after hitting a Cloudflare captcha.

• 
  Ido Bronstein (@IdoBronstein) reported 34 minutes ago

  On August 6th, @Cloudflare launched a web browser no human will ever use. It's called Kitesurf, and it's built only for AI agents. Instead of forking Chromium — the engine behind almost every browser automation tool of the past decade — Cloudflare put together a new lightweight engine in Rust. In their own tests it uses up to 3.8x less CPU and 7x less memory than Chromium, at the cost of running a bit slower per task (@TechCrunch). Read past the specs. The cost of letting an agent act on the web just dropped by a large multiple. When something gets that much cheaper, you don't get a little more of it. You get a flood. That's where I'd slow down. Every company is about to run far more agents, doing far more things, for far less money. The bottleneck stops being "can we afford to run agents" and becomes "can we trust what they do at that volume." Here's the part that changes. A wrong answer used to be one bad report that one person caught. At agent speed, one wrong definition becomes a thousand wrong actions before anyone looks. The mistake isn't worse. There are just many more copies of it, made much faster. So before you scale the agents, fix what they read. Clear definitions. One source of truth. A named owner for each definition, so when something breaks you know who fixes it. Cheap agents multiply whatever you feed them. Make sure it's worth multiplying.

• 
  Panat (@ptaranat) reported 35 minutes ago

  @HotAisle @offerexpired you’re telling me in your 30 years of infra, you never ran into a situation so dire you had to run the CI/CD pipeline off a company laptop to push a hotfix to ****? i’ve had to do this twice now, usually when multiple AWS regions are down or cloudflare is having a major outtage and the CI/CD was in the same infra as **** and no one bothered to do region/provider failover for internal tools until after the post-mortem. imagine a situation so bad you couldn’t even rollback. it’s not something you do day to day, but it immediately exposes gaps.

• 
  kei is malding over unshelve (@youaremythemis) reported 37 minutes ago

  Unshelve is down again for unexplainable reasons I will go home and investigate and kaboom cloudflare

• 
  Darren Shepherd (@ibuildthecloud) reported 39 minutes ago

  Why doesnt @cloudflare have an iroh service. Seriously you jump on ipfs but not this one?

• 
  Manuel Suarez (@srmanuelangel) reported 40 minutes ago

  I think infra might be one of the areas where coding agents feel the most unfair. So much of the job used to be babysitting slow feedback loops: change something → deploy → wait 15 min → find out it broke → fix → wait again. Now you can give an agent the Terraform, let it understand how the whole thing is wired together, read the errors, and keep iterating. Obviously this doesn't make infra trivial. Security, WAFs, rate limits, CloudFront, Cloudflare, permissions, etc. still need actual thought. But for relatively simple products, the amount of annoying work that just disappeared is kind of insane. It also makes some infra SaaS feel a lot less essential when you have an agent + a pile of AWS/GCP/Azure startup credits. Much respect to the people who were doing all this **** manually 5 years ago.

• 
  Grant Hermes (@GrantHermes) reported 41 minutes ago

  Median's domain was registered on August 10th using private Cloudflare servers. Its registrants' names are masked with a data replacement service. It's not registered in any state or federal database as an official entity. 2/

• 
  Brad Gessler (@bradgessler) reported 42 minutes ago

  @crqrdotcom Putting your name down for cloudflare.

• 
  BITx (@getbitx) reported 47 minutes ago

  @xrpcafe @XRPXolo It’s possible your ISP is using CGNAT which can cause Cloudflare to block your shared public IP address. Asking your ISP to allocate you a fixed IP might resolve your issue.

• 
  Frantisek (Frank) Borsik (@FBorsik) reported 47 minutes ago

  Hey @Cloudflare @CloudflareRadar - can you help, please? I want to turn off that absolutely useless and unhelpful "AI" in Radar.

• 
  alwinsDen (@alwinsDen) reported 53 minutes ago

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

• 
  UB360.ai (@ub360_ai) reported 54 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

• 
  ctoxyz (@_ctoxyz) reported 55 minutes ago

  @cloudflare literally just PREVENTED that company from getting a SALE from me. nice work **** HEADS

• 
  Wind's Scion (@Winds_Scion) reported 56 minutes ago

  @juiceboy_of_abj Yeah airtel has ****** problem with cloudflare and GitHub can't even download at good speeds at all

• 
  Hackmamba (@hackmamba) reported 56 minutes ago

  A competitor intelligence agent can produce a polished report and still give you the wrong answer. The problem can happen before the analysis even starts. If the researcher agent hits a Cloudflare challenge, an empty response, or a JavaScript shell instead of the actual page, the analyst has no reliable data to work with. It will analyze whatever came back. This article from @ZenrowsHQ walks through how to build a CrewAI competitor intelligence agent with Zenrows, using a dedicated researcher to retrieve competitor data and an analyst to turn that data into a structured brief. It also covers how to handle JavaScript-rendered and protected pages, return structured data with AutoParse, and use the Zenrows MCP server instead of building a custom tool. Link in the comments.

• 
  VaTsaL (@Codat_V) reported 1 hour ago

  Cloudflare once had a React bug that helped take down its dashboard and several APIs A useEffect depended on an object that was recreated on every render. React treated it as a new value each time, ran the effect again and sent more API requests. This happened during an update to the backend service receiving those requests. It got overwhelmed and failed to recover the surprising thing was that a loop in the frontend could put enough pressure on a critical backend service to cause a much larger outage

• 
  Ascellayn (@SiriusBYT) reported 1 hour ago

  @helvetica5td @Asora_EN This explains why using a VPN sometimes you still get an error but you try again in a different region and the issue is gone, probably because that Cloudflare CDN Server's IP hasn't been ratelimited yet It also explains why without a VPN it also doesn't work (cause same CDN)

• 
  Jacob Beers (@JTBeers) reported 1 hour ago

  @r3c0nc1l3r Nice. I will have to look into that. I almost never get to work directly with Cloudflare so I'm not as familiar with its offerings as I should be.