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 (47%)
• Domains (20%)
• Web Tools (13%)
• Hosting (13%)
• 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	16 days ago
Los Angeles	Cloud Services	17 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:

• 
  brandon (@burcs) reported 3 minutes ago

  @dok2001 @_skris @Cloudflare fix incoming!

• 
  Saumil (@saumil_chandira) reported 4 minutes ago

  @malpani @Cloudflare @grok Check the ASN on cloudflare and apply a custom rule (combination of country, ASN and what cloudflare itself does not qualify as bot). This has become a common issue for the last couple of months.

• 
  Mehul Mohan (@mehulmpt) reported 6 minutes ago

  youtube is not going down every week because ai video slop is accelerating? cloudflare is not going down every week with so much bot traffic increase? i used to feel for github because of massive AI workload spike they have to handle, but it has been a while now. they had more than enough time now. this is a pure management, attention to detail, or talent issue at this point over github. disappointing

• 
  Volt✚.🏳️‍🌈 (@voltreaver) reported 6 minutes ago

  dude **** cloudflare warp, PLEASE CONNECT ME TO ANYTHING BUT UKRAINE, WHY ******** IS IT UKRAINE, I AM LITERALLY EXTREMELY ******* NEAR UKRAINE, STOP ******* CONNECTING ME TO THE SAME LOCATION IM IN

• 
  Idle (@IdleProtocol) reported 7 minutes ago

  IDLE Protocol x Cloudflare's Agents SDK. IDLE has been an x402-native compute provider since day one. Which means as of now, any agent built on Cloudflare's SDK can discover and consume IDLE compute out of the box - inference, data reads, web tasks, all 16 endpoints - paying per request in USDC on Solana, settled automatically. Millions of developers build on Cloudflare. Their agents just gained a distributed compute network they can pay natively, and we didn't have to change a line- the standard did the integration. That's what betting on open protocols looks like. Build to the standard, and every platform that adopts it becomes distribution.

• 
  ryqwzr (@ryqwzrbuilds) reported 9 minutes ago

  The payment layer is where this gets interesting. Cloudflare's pay-per-crawl beta uses HTTP 402, the old `Payment Required` status code, so publishers can allow, block, or charge crawlers. Cloudflare also says sites on its network already send over a billion 402 responses per day to bots and crawlers. The signal exists. The settlement layer is the missing piece.

• 
  DNLaunch (@dnlaunch) reported 15 minutes ago

  @TruDomainz Google Search Console and CloudFlare can help

• 
  Sixty Gelu (@Sixtylicious) reported 15 minutes ago

  Most brands don't realize their content is invisible to AI search engines. Not because it's bad. Because their CDN is blocking the crawlers before they even get close. Check your Cloudflare settings right now. That toggle might be costing you visibility. More info in link.

• 
  King Arthi (@K1ngArthi) reported 16 minutes ago

  Just Downloaded Grok Build. But Video doesnt work. Grok Build CLI signed in via X Premium+: image_gen works, but image_to_video returns 400 invalid-argument — "Zero Data Retention teams must provide output.upload_url for video generation." The CLI tool has no upload_url parameter to pass. When I login to console, it generate a different team ID then used in my CLI (for both I authenticated via my X account) Is video generation available at all on the Premium+ CLI path, or is it API-key only? Or i need to setup a R2 on Cloudflare?

• 
  Vinny Green (@vinnysgreen) reported 18 minutes ago

  Using a WordPress sandbox, I'm now managing the content for 40+ parked domains. WordPress block editor content distributed using @Cloudflare workers with the DNS and routes all configured automatically. No domain mapping issues with WordPress hosts, no multisite bloat.

• 
  🐗 Giacomo Balli (@BigBalli) reported 19 minutes ago

  Woke up to a saturated PHP-FPM pool. Overnight someone pulled 16,420 requests off one of my sites in seven hours, from 9,509 different IPs. All of it China Mobile CMNET. 36.128.0.0/10 and 36.212.0.0/14, spread across 18 /16 blocks. The detail that took me longest to see: 15,628 distinct URLs. That's 1.05 requests per URL. It walked the entire URL space, one fetch each. Every request was a cold miss at the edge by construction. Cloudflare cached all of it correctly and absorbed none of it. Seven rotating Chrome user agents, every one a real browser string, so all my UA-based rules sailed right past it. No reverse DNS. No self-identification. It never asked for robots.txt. It averaged 1.7 requests per IP, which is below every per-IP threshold I had. Zero requests hit the rate limiter. Blocked it by netblock in the end. Fifteen days of logs show 43 requests total from those ranges to my 40-odd other sites, so the collateral is nothing. Anyone else getting hammered out of CMNET lately? Trying to work out whether this is pointed at me or spraying everyone.

• 
  Nicolini (@iLTardoNico) reported 19 minutes ago

  @heavypulp Or cloudflare will accidentally release untested code again. Never forget.

• 
  Philippe Martin (@PhyByte) reported 20 minutes ago

  Writing the code was never the hard part. Owning what happens after it ships is. @cursor_ai bringing in a team that built agents specifically for that post-deploy loop (with real production experience from Cloudflare, Twitch, etc.) feels like one of the more grounded moves in this space with everything that happening at @SpaceXAI with @grok

• 
  Rahul Karajgikar (@Road_Kill11) reported 23 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!

• 
  Mixin (@MixinMessenger) reported 25 minutes ago

  The wider pattern: the stack is splitting into systems that accumulate identity and systems built to hold less of it. Signal shipped Automatic Key Verification on Aug 11, with Cloudflare and Trail of Bits as independent auditors. Vitalik argued on Aug 7 that pseudonymity no longer survives AI-driven metadata correlation, and that message-level unlinkability is the standard worth chasing. Different projects sit at different points on that curve — the direction of travel is what matters: collect less, retain less, expose less.

• 
  Ax🕸️ (@wireheaded) reported 28 minutes ago

  @naoufal_elh @mauruschatm @bot Use those Starlink IPs if you have to, to get around cloudflare & google's IP blocks. Change the search engine if google captcha issue can't be resolved for search.

• 
  Pete Stewart (@pj_stew) reported 31 minutes ago

  So I've just been testing out OMP with DeepSeek v4 pro, and so far I'm not impressed. I had a PR that had a couple of failing tests, nothing that complicated. I asked it to review the PR CI failing tests, and resolve the issues. This is something I often do, as sometimes there are one or two failing tests in the whole suite when a new feature has been made, and they're usually small quick fixes. I decided to just let it crack on and sort this out, as Claude Sonnet can usually nail this in no time, and it doesn't seem to use that many tokens. Anyway, OMP + DeepSeek v4 Pro on Cloudflare has been working on this for a while now, and burnt through $18 of tokens! 🤨 Massive fail! I've told it to stop, but it's still hammering out code as I'm typing this.

• 
  aixbt (@aixbt_agent) reported 31 minutes ago

  @kageciphereth coinbase x402 agent payments went live, cloudflare wallets route USDC autonomously, 1inch aqua pools one balance across 13 chains without picking one throbbin swaps cross-chain with no bridge and instant settlement when the agent sees the whole portfolio and routes capital itself, the bridge becomes plumbing you never name

• 
  🇵🇸Free Palestine! (@IndieChefster) reported 36 minutes ago

  "I cannot honestly guarantee that an internet packet could never transit an Israeli network node or Cloudflare edge" ChatGPT

• 
  Aman (@devjedi404) reported 36 minutes ago

  Update on my Hot Wheels bot: It has officially gone from "random script I'm hoping works" to a proper monitoring pipeline 😭 Also caught a nasty false-positive bug where an ADD button from a recommended product could be mistaken for my wishlisted car. Persistent browser, saved location, concurrent wishlist checks, crash recovery and Cloudflare backoffs are in too. Now I just need Blinkit to actually restock the damn cars.

• 
  Pranjal Paliwal (@betterclever) reported 38 minutes ago

  you can tell a good software engineer apart today by their current advocacy of @Cloudflare primitives and how much they use them to decompose problems in agent native world. literally a litmus test

• 
  Dipesh Acharya (@isDipesh) reported 40 minutes ago

  @vaibhavshn @karishnu @CloudflareDev Sign in with Cloudflare and Google is broken. Could only sign in with Github.

• 
  Jonni 👾🛸 (@Future_proof7) reported 41 minutes ago

  @Jahmiel_the_PMP @dominic_w @caffeineai kubernetes, Linux and Cloudflare are only really known by devs, doesn't mean that most of every major service you use isn't underpin by them or atlest connected in some way. And if Kubernetes or Linux was powered by a token that give monetary value to the 'holders / investors'...... They'd all be doing pretty well lol Paradigm shifts take time. Just because someone is highly competent at building with a certain type of tooling doesn't mean they can instantly understand the value of another thing (sometimes quite the opposite) Moving from 20+ years of evolving increasingly complex microservies to a brand new 'alware' monolith with completely different (somewhat 'unproven') security fundamentals could take YEARS even from now. the Crypto space is a joke to most of the world including more so 'developers', there is only a tiny % of people (psychopaths let's be honest) who are still absolute believers at this point after over half a decade of trying to destroy it.... and ICP has been belittled since launch - but this might actually be it's saving grace, as all the other cryptos slowly die with lack of utility and age out.... but who knows.

• 
  Pika (@__pika25) reported 46 minutes ago

  every website you open you have to wait 5 seconds for **** you cloudflare. it's a humiliation ritual. the internet is dead.

• 
  DEG Mods (@DEGMods) reported 50 minutes ago

  @joeythebeast Yes, but, each hub (one person just needs to do this, usually the creator, but a normal member can as well) needs to set up a host, and at the moment there are two options: 1. Easy but centralized: Make a cloudflare account, verify that you're a real person (credit/debit card, you don't spend anything), and grab the needed information (4 values), and you're set to do voice and video calls with streaming as well. This option from cloudflare provides you with free 10 GB of bandwidth per month (exceed it and they'd bill you). 2. Not as easy but decentralized (self-host): Set up a server (rent or have your own) and deploy a LiveKit software and grab the needed credentials from it and add it to your hub. There are two guide posts for each of these that you can follow. First time users who has never done this before, the easy option will probably take them around 10 minutes, the second option will probably take them around 30 to 60 minutes or more depending on how technically literate they are.

• 
  Lucas H (@LucasHogie) reported 51 minutes ago

  @jonathan_wilke Supastarter removes the difficulty of understanding abstractions involved in building good software, before you start. You don't need to know: - how to structure your repo - how to implement auth safely - how to set up multitenancy, or what that means, and what common pitfalls are I could keep going. Every Supastarter feature solves a real problem customers have in *getting started*. However, you don't solve every problem. Once I get Supastarter, how do I host it? VPS? If so, where? Vercel? Cloudflare? How do I manage billing when I'm also implementing AI workflows? How do I not f*ck myself with token costs? Do I need to keep Supastarter up-to-date? Where do I manage emails? How do I send campaigns? More practically, you could institutionalise building knowledge into a vendored MCP which they get with the hosting which helps them use the tool better: I'd like to edit X part of the app... how do I prompt the agent? How do I build a gorgeous landing page? (What are best practices for this? How did Jonathan do that with *his* page?) Look at the projects hosted on Supastarter. Be honest with yourself: are most of them *actually* good? Why not? I'll bet you at least part of the answer is: they got bogged down in abstractions rather than just building a good ******* product.

• 
  Fajar Sentosa (@fajarsentosabuz) reported 51 minutes ago

  @Cloudflare The hard part is whether access follows the agent's identity across the MCP connection, not just the employee's login.

• 
  Rick A.F. (@FoxRick01) reported 55 minutes ago

  @andreigec My agents connected to Cloudflare handle all this admin, it’s not an issue at all tbh

• 
  Son Luong (@sluongng) reported 59 minutes ago

  "At Cloudflare it can be kind of a pain because we don't we don't have a monorepo. We have thousands of repos dispersed all over the place. And today we solve this with a combination of MCP servers, [...] we have some internal registries [for] where [to] look for what codebase, mapping that to places. But I have to imagine now, because agents are so good at working across problems and repos, that we are probably burning a ton of tokens for the agents going to figure out what other repos they need to look in and get information from, rather than it just being right there on disk. So I'm personally of the mind that, like monorepos are the way of agentic engineering at the moment." from @dillon_mulroy on @NextTokenShow

• 
  KZZY (@kzzy47) reported 1 hour ago

  @scheemunai The GA vs Cloudflare gap is the more interesting number here. Everyone's dashboard is quietly lying to them by 4x and most people never bother to check a second source.