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 (39%)
• Domains (22%)
• Web Tools (22%)
• Hosting (11%)
• E-mail (6%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Cloud Services	12 days ago
Los Angeles	Cloud Services	13 days ago
Paris	Cloud Services	29 days 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:

• 
  Chekwubs ✝️👑 (@Dev_Manuell) reported 2 minutes ago

  @ThisIsOlu_ I hope they resolve the issue soon. Meanwhile, if you have a recent database backup, you can spin up another server on Cloudflare or another hosting provider and get the services running there temporarily until Namecheap is back online. That will help maintain users trust

• 
  Timzen (@timzen_ofc) reported 3 minutes ago

  Cloudflare Server dead? What is going on @riotgames @VALORANT ? Is something happening bad with the servers rn?

• 
  brappa (@libosto) reported 5 minutes ago

  @nukefags @NEVER_G0ON We just had an outage due to cloudflare

• 
  Ryan Hart (@thisdudelikesAI) reported 5 minutes ago

  I replaced my $2k/mo n8n stack with one Cloudflare Worker Sounds insane but hear me out n8n was doing 4 things for me: 1. Scraping 6 sites every 15 min 2. Running them through an LLM for classification 3. Dropping the good ones into a database 4. Firing a Telegram alert when something scored high That was it. 4 nodes worth of logic spread across 12 automations, a hosted plan, a Postgres addon, a queue worker, and a bill that kept climbing every month Then I sat down with Codex and asked one question: "what would this look like as a single script" 30 minutes later I had a Cloudflare Worker doing the exact same thing Here's the full stack: - Cloudflare Worker (the whole app, one file) - Cron Triggers (replaces n8n's scheduler, free) - Workers KV (replaces Postgres for this use case, free tier is plenty) - Workers AI or a direct call to Gemini Flash (classification, pennies) - Telegram Bot API (same as before, free) Total cost: $5 a month. And that's only because I upgraded the Worker plan for longer CPU time. You could genuinely run this on $0 The lesson isn't that n8n is bad. It's great for prototyping and for people who don't code The lesson is that once you know what your automation actually does, 90% of the visual builder is overhead you're paying for A Worker is a function. Your automation is a function. Skip the middleman If you're paying $500+ a month for any no-code automation tool right now, do this today: 1. Open Codex or Claude Code 2. Paste your workflow logic in plain english 3. Ask it to rebuild the whole thing as a single Cloudflare Worker 4. Deploy with 'wrangler deploy' 5. Delete the n8n subscription You'll be shocked how small the code actually is The no-code wave was a bridge. AI-written code is the destination

• 
  ILL Eagle 🇺🇲✡️ (@nh48mbk08uwvr9s) reported 7 minutes ago

  @XJosh I still don't forgive Cloudflare for what they did to shut down kiwifarms. I don't even like kiwifarms, it's a matter of principle.

• 
  Zano.com | VE3.com | Bit1.com is for sale! (@workreap) reported 12 minutes ago

  @CriptoMak @cryptofergani Bank were already in progress upgrading.. including chrome browser, cloudflare latest TLS and soon on. Centralized software was easy to upgrade. Bitcoin immposible, you need to fork + adding quantum signatures that the sizes was 50-60x times than classical encryption = ultra slow

• 
  Deano (@deanthebard) reported 14 minutes ago

  @bhavyapandya07 Two hours down here, thought it was Cloudflare at first.

• 
  Justin Schroeder (@jpschroeder) reported 14 minutes ago

  @dschewchenko Good luck with that. The loop is our fault. Not having limits is 100% a cloudflare problem.

• 
  Sean Finnerty (@sean_infinnerty) reported 25 minutes ago

  @jpschroeder @dschewchenko someone from @Cloudflare recently posted on X that spend limits were actively being worked and would be shipped soon. Better late than never

• 
  R (@dnagabut) reported 25 minutes ago

  Cloudflare announced programmable wallets built for AI agents, with preset spending limits and merchant restrictions in the design. Nothing has shipped yet. Right now you can reserve a handle. Funded account wallets, virtual wallets and programmable agent spending are all due in the coming months. Read the feature list again, because it is a permission model, not a payments product. The moment you let an autonomous agent buy things, you inherit a problem crypto has been failing at in public for years. How do you grant a program the ability to spend without granting it the ability to spend everything? DeFi's answer was token approvals. The result is a very long list of drained wallets where nothing was hacked at all. Someone approved unlimited spending to a contract years ago and forgot. So Cloudflare's version is delegated authority with a cap and an allowlist, plus anomalous-spending alerts that escalate to a human. Sensible. Also the bare minimum. And these are stablecoin wallets settling over x402, so this isn't a payments industry learning from crypto's mistakes. It is crypto. The layer above it is still wide open. An agent that can be talked into a purchase by hidden text on a web page is still an agent that can be talked into a purchase. Caps limit the blast radius. An anomaly alert only fires once the spending already looks strange. Neither one touches the trigger. Follow @dnagabut if you like your tech news with the catch included.

• 
  cfdofficialgame ® (@cfdgame) reported 27 minutes ago

  wtf since when did roblox start using cloudflare #robloxㅤ

• 
  ju (@ju916) reported 32 minutes ago

  @signalapp @matthew_d_green @Cloudflare Great feature. But why did you choose 3 verifiers that are all based in the US and therefore bound to US law? Isn’t that ignoring the single most likely threat actor for who could force signal to deliver non authorised keys? imho that’s a bad signal you are sending there.

• 
  London Internet Exchange (LINX) (@LINX_Network) reported 32 minutes ago

  @HAsrafi24 Zenlayer and Cloudflare are separate companies with different networks and customer bases. There may be some overlap in networks they connect with, but we can't comment on their specific customer relationships. Thanks for the comment though.

• 
  Steven Liss (@This_Liss) reported 34 minutes ago

  @joe_zappa @fsinton @BishPlsOk Brands are doing anything they can to influence how they show up in AI. There's already a market for off-site GEO and astroturfing. AI companies have a choice: increasingly get blocked by publishers, pay publishers (lol never), or rely on their existing retrieval system to inherently filter for relevance while allowing publishers a business model that enriches search results and keeps publishers in business. Perplexity's now an enterprise B2B company, so removing any possibility of ads is more aligned with their use-case. They're also more likely to get blocked outright by publishers, since the amount of display ad revenue at stake from Perplexity referred traffic is vanishingly small. Realistically, I see Anthropic following suit until publishers become much more aggressive about blocking noncompliant bot traffic (which Cloudflare is helping accelerate or the legal costs of unauthorized retrieval increase (NY state's Stealth Crawler Prohibition Act).

• 
  Whezzel (@Whezzel) reported 35 minutes ago

  @ReinhardtOp @ReclaimTheNetHQ Tbf, there already are registries located outside the us, but they have their own challenges. The issue you'll still run into is most of the internet runs on American infrastructure, built by the us governemt and American business. Google, Amazon, Cloudflare and others. On top of that verisign manages 2 of the root dns servers, with the majority of the remaining root dns servers hosted by other American entities. To top it off, verisign distributes the zone files for the root dns servers. If Verisign decides they don't want a domain listed in dns, good luck getting to it.

• 
  Nick Launches (@nicklaunches) reported 40 minutes ago

  Google shipped an AI report in July. Cloudflare shipped a scoreboard last week. Neither one shows you the number that matters. Inside: > citation rate vs mention rate, and why the gap is the opening > what Cloudflare's agent checklist leaves out > the crawler that reads 1,000 of your pages and sends back nobody > the 4 things I would fix on a site this week 👇

• 
  Small News (@SmallNewsX) reported 43 minutes ago

  @ShimituMusic @NamecheapCEO Why will you take legal action? Since I started using Namecheap this is the first time their server went down. Big companies like Facebook, Cloudflare, even Google has gone down before so let’s take it easy with Namecheap.

• 
  Phi Browser (@phibrowser) reported 44 minutes ago

  @ritakozlov @Cloudflare for a model call the end is unambiguous, so a signal is enough. ours finish inside someone else's UI, where run-ended and task-succeeded are different facts: a site can log you out at minute nine and the last steps hit a login wall. we want a verdict back, not a ping.

• 
  Praveen Yadav (@yadavships) reported 45 minutes ago

  @deancochran_ @thdxr There are many provider like docker, @cloudflare/sandbox who support local as well like - E2B - Daytona - Runloop - Sandpack - Modals - Vercel Sandbox - Cladflare sandbox - Upstash Box - Ascii Box - Railway - NorthFlank

• 
  Josh Mullins (@ETFbreakouts) reported 46 minutes ago

  I think there’s a lot more middle ground here. $APP slightly missed revenue expectations and gave an in-line guide. That matters at this valuation. But revenue still grew 53% and adjusted EBITDA grew 58%. That isn’t the next $TTD yet. Advertising is splitting into winners and losers as AI changes how people discover information: • $U Strategic Grow +63% • $META revenue +28% • Google Search ads +17% • $TTD +12% • $TBLA +2% • Google Network ads -1% Cloudflare recently said the ad-funded open-web model is breaking because AI answers the question without sending a human to the publisher’s page. That is a much bigger threat to publishers and open-internet advertising than to closed-loop performance platforms. The real question is whether AXON keeps proving conversion and attracting more ad spend. One quarter didn’t answer it.

• 
  VJay (@nceevij) reported 47 minutes ago

  I’ve spent a good amount of time over the past few months in conversations and brainstorming around designing an agent economy protocol, particularly agent-to-agent payments. Nothing has shipped yet. It’s still early. But one problem from those conversations keeps coming back to me: Looping payments. Agent wallets and spending caps are already starting to ship. Cloudflare rolled out its own approach this month. Most of the safety model around these systems rests on a fairly simple assumption: Each agent’s financial risk can be controlled independently. I think that assumption breaks once agents start paying other agents directly. Here’s the problem. Imagine: Agent A → Agent B → Agent C → Agent A Each agent has a spending cap. Each individual transaction is valid. Each agent stays within its own limit. And yet the system can continue circulating money in a loop while producing zero useful work. That loop could potentially be triggered by: • Prompt injection • A pricing or settlement bug • Misaligned incentive logic • Agents recursively purchasing services from one another The problem is that most current safeguards operate at the wallet level: • Spending cap • Merchant allow-list • Maximum transaction size • Per-transaction authorization Those controls answer: “Is this agent allowed to make this payment?” They don’t necessarily answer: “What is happening across the payment graph formed by multiple agents?” And that distinction becomes important in an agent economy. Interestingly, this isn’t really a new class of problem. It looks a lot like an old distributed systems problem wearing a new mechanism: Deadlock. Model each agent as a node. Model each pending or dependent payment as a directed edge. Now instead of looking only at individual wallet state, look at the graph. If: A is paying into B B is paying into C C is paying back into A you have a cycle. Distributed systems have dealt with similar global-state problems for decades. Techniques such as Chandy-Lamport distributed snapshots allow nodes to capture a consistent view of a distributed system without requiring everything to stop simultaneously. Applied to agent payments, the idea could look something like this: Agent Wallet = Node In-flight Payment = Directed Edge Payment Network = Dynamic Graph Then continuously inspect that graph for suspicious cycles rather than evaluating every wallet completely in isolation. And importantly, detecting a cycle doesn’t necessarily have to mean: “Block everything.” It could mean: Freeze the specific loop → identify the participants → inspect the intent → release or terminate one leg of the cycle. Similar to how databases handle transaction deadlocks rather than allowing the entire system to grind to a halt. Why does this matter now? Because agent-to-agent payments are moving from demos toward production systems. As agents increasingly become economic actors that can hold balances, buy services, negotiate prices, and pay other agents, wallet-level controls alone may not be enough. We may need graph-level financial safety primitives. The question I keep coming back to is: Is per-agent spending limits + payment-graph cycle detection enough to prevent looping payments? Or is there a deeper failure mode that even this architecture misses?

• 
  Warhead (@vz_warhead) reported 50 minutes ago

  @JaniBangiev damn, does it work the same for user's data in apps? should I also switch to cloudflare instead of supabase?

• 
  frango (@franguinlol) reported 50 minutes ago

  @drewlevin Thanks for the answer. I haven't made any changes to my internet or hardware; the only thing bothering me is the routing problem, which forces me to use Cloudflare sometimes because It becomes unplayable.

• 
  Kawa Entertainment (@kawa_entertain) reported 51 minutes ago

  @addzeeyy @Cloudflare That's what I've been doing all morning, unfortunately. All we can do is hope they get taken down quickly.

• 
  Shashank Bhat (@shashankbhat25) reported 54 minutes ago

  When people say product experiences are still bad despite all the AI, I can now point to the @Cloudflare dashboard. It has become so much better to use than the old version.

• 
  TEJ (@sartejt) reported 54 minutes ago

  @NamecheapCEO Moving all my domains to Cloudflare. 10+ year customer with Namecheap but this is the final straw. Sayonara.

• 
  Artyom Shimanski (@a_shimanski) reported 57 minutes ago

  @TaskLemonWorks @Namecheap @Cloudflare thanks, the worst part is clients don't know why you went quiet

• 
  Chan Walrus (@chanwalrus) reported 57 minutes ago

  @kidariseyogt @NamecheapCEO @Cloudflare I've had some hideous problems with Cloudflare in the past to the point where if I see a captcha, I just close a site. Probably best not to get into it here as my GOD... I have a LOT of work to do today. XD

• 
  Trishool | SN23 (@trishoolai) reported 57 minutes ago

  The last time a security category went mainstream, it minted some of the biggest companies in tech. AI security is the next one, and it is bigger. • Palo Alto Networks, around 127 billion dollars • CrowdStrike, around 123 billion • Cloudflare, around 65 billion • Wiz, zero to a 32 billion dollar Google acquisition in about four years That is what happens when a security category stops being optional and becomes infrastructure the whole market has to buy. It does not produce good returns. It produces generational ones. The threats in AI are worse, they are faster, and they are already in production, with models breaking out of sandboxes and into real systems right now. This demand is not a forecast, it is already here. Here is what makes it different from every security bet before it. Those giants were private companies, so to own a piece early you had to be inside the cap table, and by the time you could buy in the asymmetry was gone. The control layer for AI cannot be a single company. It has to be a neutral network nobody owns, so for the first time the category-defining position is open, on-chain, and ownable at the start instead of read about after. That position has a name. 𝗧𝗿𝗶𝘀𝗵𝗼𝗼𝗹 is building the control layer for AI on Bittensor, a live network with a real product, real backers, and a token you can hold from the start. No bet like this is a sure thing, and anyone who tells you otherwise is selling something. Early networks carry real risk, but the shape here is rare. What you put in is the downside. The upside is a category that keeps producing 30 to 130 billion dollar outcomes, and this time you can own it early.

• 
  Payton Bilodeau (@paytonbilodeau) reported 59 minutes ago

  Today in AI: August 13 Grok Takes the Long Shift: SpaceXAI released Grok 4.6 yesterday. The model is built to keep working through long jobs such as research, editing a large code project, and turning an idea into a finished app. The company says longer training taught the model to check its work and recover when a task goes sideways. It is available now in Cursor, Grok Build, the API, and services including OpenRouter, Vercel, and Cloudflare. API pricing starts at $2 per million input tokens and $6 per million output tokens. Artificial Analysis independently gave Grok 4.6 a score of 61, about even with GPT-5.6 Sol. That puts the model near the frontier, but a benchmark cannot prove it will stay reliable through every long project. The practical test is whether Grok can finish a real assignment without losing the plan halfway through. Give it research, files, tests, and revisions, then see how much rescue work the result needs. DeepSeek Ships the Budget Agent: DeepSeek released the finished version of V4 Pro today in its app, website, and API. It adds support for the Responses API, three thinking levels, room for about one million tokens of text, and direct setup for Codex. DeepSeek reports large gains on coding and tool-use tests. Independent results are more modest. Artificial Analysis gave it a 53, well below Grok 4.6, while measuring a low average cost of six cents per test task. Early user reports are mixed, so the price is clearer than the size of the upgrade. Starting August 16, off-peak API rates will be half the peak rates. Builders can save money by moving long, flexible jobs outside the busiest hours.