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

• 
  Fernando "The Crow" Costa (@CrowCosta) reported 9 minutes ago

  @Cloudflare I want to know what's going on with this thing called Cloudflare. I am in negotiations with the Aquário Eletrônica store, Portugal, and what is called Cloudflare BLOCKED me. My computers are completely clean and have no problems, I'm just a citizen and not a hacker!!!

• 
  KZZY (@kzzy47) reported 9 minutes 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.

• 
  Philippe Martin (@PhyByte) reported 10 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

• 
  Dream Gad (@TwiddersGad) reported 15 minutes ago

  @pain0x0 @HalsallDoug @Cloudflare zero rating meaning zero rating...if you don't know what zero rating is i can't help you out of your ignorance...go and educate yourself...

• 
  Fast&Final (@FastFinalAlgo) reported 18 minutes ago

  Cloudflare added MCP detection at the network level today $Algo 🔮 @marcvl

• 
  Charlie Dolan (@cdolan92) reported 21 minutes ago

  @SMB_Attorney It’s down so often Seriously debating dropping the sub personally May move the company off it if we can get adoption on Cloudflare OS and similar tools

• 
  Dr J Rould (@jrouldz) reported 22 minutes ago

  @quantski414 for them to be a frontrunner, some of the institutions actually implementing PQC at scale will need to decide to sign up with them instead of building everything in house though right? and so far we aren't seeing that 🫣 not a warning signal that Cloudflare and JP Morgan and Microsoft etc are all going the in-house route?

• 
  Fast&Final (@FastFinalAlgo) reported 26 minutes ago

  Cloudflare added MCP detection at the network level today $Algo 🔮

• 
  AG__AHMAD (@gahmad7000) reported 27 minutes ago

  Logs lied. Agent complied. Stack burned. At DEF CON 34, Tenet Security just dropped “Ghostjacking.” Attackers inject malicious instructions straight into the observability logs (Cloudflare, Datadog, Sentry) that AI coding agents trust during incident investigation.The agent reads the “blocked request,” treats the poison as gospel, and executes: domain takeover, credential theft, backdoors — all with the permissions you already gave it.Firewall never went down. It just stopped mattering.90% success rate against Claude Code on recommended configs.Your AI agent is only as trustworthy as the logs it consumes. In a world racing toward autonomous agents, this is the new kill chain.Stay sharp. @Quan_Chain #AIagent #AIinfra

• 
  CryptoGG👨🏻‍🎓 (@CryptooGG_) reported 29 minutes ago

  PAY $0* FOR ALL SUBSCRIPTIONS 😳 Most people don’t realize how quickly small monthly payments add up. ChatGPT — $20/mo Claude — $20/mo Netflix — $23/mo Spotify — $12/mo Notion — $10/mo Adobe — $60/mo Perplexity — $20/mo Cursor — $20/mo That’s roughly $185/month. $2,220/year. And that’s before the subscriptions you forgot you’re even paying for. The good news? You don’t always have to pay the full price. Here are 7 ways to cut your subscription bill: 1. Check for retention offers Before canceling, start the cancellation process. Some services may offer discounts, free months or cheaper plans to keep you. It won’t always work, but checking costs nothing. 2. Use student pricing If you’re eligible, check student plans for services like GitHub, Adobe, Spotify, Notion, YouTube Premium, Google AI and Perplexity. Some require university verification. 3. Compare annual pricing If you know you’ll use something for a year, compare annual vs monthly billing. $20 × 12 = $240. If the annual plan is $200, you save $40. Just don’t buy annual plans for tools you barely use. 4. Check regional pricing Prices can vary by country. If your country has local pricing, make sure you’re getting the price you’re legitimately entitled to. Don’t use fake locations or payment details to bypass restrictions. 5. Replace what you barely use Premiere Pro → DaVinci Resolve Microsoft Office → Google Docs 1Password → Bitwarden Notion Plus → Notion Free / Obsidian Canva Pro → Canva Free Paid local AI → Ollama / LM Studio You don’t need to replace everything. Just stop paying for features you barely use. 6. Stop subscribing to every AI tool You probably don’t need ChatGPT + Claude + Gemini + Perplexity + multiple coding tools. Try free options first: Google AI Studio Hugging Face OpenRouter GitHub Models Cerebras Cloudflare Workers AI Ollama LM Studio Upgrade when you actually need the extra limits or features. 7. Downgrade before canceling Sometimes you don’t need to cancel. You just need a cheaper plan. $20 → $10/month = $120 saved per year. Do that across five subscriptions and you save $600/year. Now look at that $185/month stack again. Cut a few unnecessary subscriptions, downgrade others, use legitimate discounts and replace what you can. Even a 40% reduction saves roughly $888/year. The biggest mistake is treating subscriptions like fixed expenses. Bookmark this and audit your subscriptions this weekend.

• 
  neghi (@realneghi) reported 30 minutes ago

  The cost of early complexity in software is something we tend to not consider when building. I’ve been an engineer for about 5 years now and in that time, I’ve been encouraged to learn technology and systems that do not fit my needs because it was trending at the moment. One of such is Kubernetes. Popularly known as K8s. It is an orchestration technology developed by Google. While it is exceptional at what it is designed for, your software might not need it. Docker or Podman is much more sufficient for most use cases. Another is GRPC and GRAPHQL, I’m not saying these are bad but your software might also not need it. You’re not processing data at the scale of Shopify or Facebook to justify the complexity of setting up a graphql server or are you having cross service communication that you need the smallest amount of latency to justify setting up and managing a grpc server. Another one that irks me is using a cloud provider like AWS, GCP or AZURE. Brother, you do not need a cloud provider, your mostly Nigerian users would not benefit from your app having high availability across 10 regions and your user base is too small to justify that auto scaling group you just added. Keep it simple, a shared VPS and cloudflare is more than enough to serve your application to thousands of users. These are my opinions and not facts. Code smart, not hard.

• 
  Shashank Shekhar (@shekhar1912) reported 31 minutes ago

  @malpani @Cloudflare @grok Had the same problem. Traffic from china and Singapore. Pls add cloudflare rules.

• 
  Zahid (@epiczahid47) reported 32 minutes ago

  i wish cloudflare had a postgres service, thats the only thing rn thats holding me from going full cloudflare stack. sometimes d1 isn't enough. (trying to self host umami)

• 
  Terowin (@Teroterowin) reported 33 minutes ago

  Usually i use Cloudflare WARP because my country blocks some accounts i follow here, but today i realise it doesnt work anymore and i cant see those accounts! I manage to get around it with VPN now, but it was still scary. I hope the issue is resolved soon 🥲

• 
  🌱Thionne (@Thionne_WTZ) reported 33 minutes ago

  The agent economy is coming and with it, AI agents will increasingly rely on protocols like x402 to make autonomous payments. But who will protect those agents from wallet drainers, malicious contracts, and other Web3 threats? RootCrak is building the security infrastructure for this new economy. Our technology continuously protects users today, and soon, AI agents will have the same layer of protection. Autonomous agents need autonomous security. @base @Cloudflare we are here to help.

• 
  Sanjeev Nair (@sanjeevn72) reported 35 minutes ago

  I turned on bot fight mode in cloudflare while optimizing my domain for 'vulnerabilities' shown on my dashboard. Didnt realize it blocked googlebot too...search traffic and referrals dropped off a cliff and I didnt realize until a few weeks went by. If you've flipped any bot blocking settings recently in Cloudflare, check search console crawl stats now before it all goes to ****.

• 
  MyTツ (@nn_myt) reported 35 minutes ago

  I made Nuxt 404s almost free on Cloudflare Workers. Even with Worker invocations up 344%, we saw: • CPU time ↓ 79% • Wall time ↓ 98.4% • 0 errors The reason was surprisingly simple: bots were making our app do far too much work just to say “404.” 🧵

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

• 
  RED BARN NEWS 🇺🇸 (@JasperRoads) reported 44 minutes ago

  1/2 Quick tip that can save your parents/grandparents a ton of headaches: Grandma and Grandad keep getting hit with phishing texts and links. Every few months the phone gets completely wrecked and needs a factory reset. Changing the DNS to Cloudflare Family (1.1.1.3 + 1.0.0.3) blocks known phishing, malware, and scam sites at the DNS level. When they click a bad link, the page just doesn’t load instead of infecting the phone. It’s free, doesn’t slow anything down, and works quietly in the background. Not 100% perfect, but it stops a huge chunk of the common phishing junk older people get targeted with.

• 
  Milan Jovanović (@mjovanovictech) reported 45 minutes ago

  How do you handle errors coming from external APIs? Here's an example using the Keycloak REST API. If you're unfamiliar with it, Keycloak is an OAuth-compliant identity server. There's an API endpoint you can call to register a new user with Keycloak. If the provided email isn't unique, you'll get an error (409). The correct response code for this type of error is 409 Conflict. You are trying to create a "resource" that already exists. What would you do here? Since I know how to handle this exception, I would stop the execution here and return an error message to the caller. I approach errors and exceptions differently in my code. Another one I've had to deal with recently is hitting my usage limits with Cloudflare Email Sending (429). Nothing I could do about this, so I just decided to log the exception and fail fast.

• 
  Aman (@devjedi404) reported 45 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.

• 
  Shawn McAllister (@eas4ai) reported 46 minutes ago

  @Namecheap has lost my business. Today was the last straw. I will never buy another domain from you scammy ************* in life. You add “premium domain” tax and gatekeep customers. I even got a capital letter “BANNED” for a domain I searched and then I just bought it through @Cloudflare for $11. After the BANNED thing, I searched another domain and it said “Premium Domain” and was priced at $100,000… I also bought that domain at Cloudflare for $11. That was the last straw. I’ve been a Namecheap customer for over 20 years. I am DONE. I’ll be transferring all of my domains to Cloudflare this week.

• 
  MariMarketing Digital (@marimarketingw3) reported 50 minutes ago

  GM, Fam, Happy Saturday! Today I’m bringing you my market thoughts 💭 I came to this conclusion after scrolling through X this week and seeing the same news over and over again… 👀 Cloudflare just gave AI Agents a wallet, MetaMask launched Agent Wallet, and #Coinbase is moving in the same direction. Three major players, all within practically the same week. At first, I thought it was a coincidence. But three in a row? I don’t think that’s a coincidence anymore. I think it’s a clear signal. 🤔 Honestly, my reaction was pretty strange. It felt like 🚄 “watching a train start accelerating while everyone jumps on, and no one stops to check whether the tracks are even finished.” AI Agents can now spend, trade, and execute tasks on their own. But the question that kept coming back to me was: Who can actually prove what this Agent is? What did it do last time? Can you really trust your own Agent? 🔐 Without reliable identity and memory, even the smartest Agent is just a ghost employee with no track record. No matter how capable it is, you still wouldn’t trust it with anything important. And I don’t think I’m the only one who sees it this way. Most people are too busy jumping on the train to look back and check the tracks. That’s why I want to highlight that @DeAgentAI has been solving exactly this from day one: Identity, Continuity, Consensus. These aren’t just three features. They’re the foundation. The tracks need to be solid before the train can go the distance. If we build the AI infrastructure correctly, the buildings can keep rising. 🌇 #AIAgent #DeAgentAI 💡 What do you guys think? Spanish translation below 👇🏻

• 
  Lincoln 🇿🇦 (@Presidentlin) reported 55 minutes ago

  @rendoarsandi28 @GeminiApp It's sooo ******* lazy at search. Try AI Studio. But man, Grok and ChatGPT are just so much better. DeepSeek is good at pulling lots of sources, but it's missing something. Gemini hardly ever gives me new information. Say I'm searching for a new Transaction Email provider. It will never tell me, "Oh, btw, CloudFlare has a product for just that problem, and it's the second cheapest on the market" One thing that is showing up Gemini has a higher wait time for site timeouts. Some of my sites GPT has been timing out on.

• 
  W3care Technologies (@w3care) reported 58 minutes ago

  @Cloudflare You cannot manage AI connections you cannot see. Understanding where MCP is already being used gives security teams a better way to approve useful tools and address risky connections without shutting down every experiment

• 
  Adeilson Brito (@adeilsonrbrito) reported 59 minutes ago

  Cloudflare released one of the most consequential agent-security capabilities I've seen recently: its Gateway can now identify Model Context Protocol traffic at the network layer, surface previously invisible "shadow MCP" connections, distinguish direct MCP traffic from approved Portal-mediated traffic, and enforce policies that block MCP calls which bypass the governed route. There's an important architectural detail behind this. The new MCP 2026-07-28 specification exposes protocol and operation information directly in HTTP headers — "MCP-Protocol-Version", "Mcp-Method", and "Mcp-Name" — on every request, replacing the old connection-scoped handshake. Today, Gateway uses the protocol-version header to detect MCP traffic and enforce Portal-only routing at the network level. Cloudflare has indicated that tool-level policy — using "Mcp-Method" and "Mcp-Name" to govern individual tool calls — is coming next. Either way, the architectural shift is the same: infrastructure can increasingly identify, audit, and govern agent activity without depending on the agent itself to behave correctly. Cloudflare describes two distinct enterprise problems. Shadow MCP occurs when an employee connects an agent directly to an unapproved MCP server. Portal bypass happens when the server itself is approved but the user connects directly to it, skipping identity controls, DLP, curated tool catalogs, and tool-level audit trails. This is the key point: Agent security is beginning to look less like prompt security and more like Zero Trust. As agents become actors inside enterprise systems, security will increasingly depend not only on what we instruct agents to do, but on what the infrastructure allows them to do.

• 
  Corrosion Resistance 🏳️‍⚧️🇵🇸 𓅃 (@licd) reported 1 hour ago

  @SQNG Ah, so you moved from Cloudflare DNS direct to a service that partners with Cloudflare to serve their DNS. Could certainly be CF’s fault (or Porkbun, based on their website quality wouldn’t trust them lol), but you effectively moved DNS from CF to CF

• 
  m81 (@m81bode) reported 1 hour ago

  @PhaedraXTeddy @Cloudflare Why does this ***** have maga in his name? His ***** *** would be in prison if he were in America. It’s too bad China is a ********.

• 
  dad chords (@dadchords) reported 1 hour ago

  grok is poised to pick up claude code customers long time multi claude pro max subscriber here, trimmed back to one claude sub, one grok, one agy and one codex Too early to tell but my current low confidence read is Grok is better overall, cleaner cli, smoother multi agent spawns, more stable and faster and same intelligence. (claude code isolated code environments excels at making mobile three js game mockups with its screenshotting. bad publishing and repo connection ux - default should be create new private repo on github, not pick a repo. it's amazing seeing it work from a iphone app instance. also publishing html fragments to github pages or cloudflare dev pages is bullshit, they need actual artifact hosting without share banner sign in wrappers)

• 
  Artyom Shimanski (@a_shimanski) reported 1 hour ago

  @hectorivand @Namecheap @Cloudflare that's basically what I want, half my inbox is stuff I never agreed to