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.

• Domains (36%)
• Cloud Services (23%)
• Web Tools (18%)
• Hosting (14%)
• E-mail (9%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Cloud Services	14 days ago
New York City	Hosting	17 days ago
Manchester	Domains	1 month ago
Angers	Cloud Services	2 months ago
London	Domains	2 months ago
Noida	Hosting	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:

• 
  defido 👊⛽️ (@defido) reported 3 minutes ago

  @meaganrgamache Moved to eve and vercel. Got tired of how bad the ai product was. Not sure why cf offers its own inference if it can deliver a stable product there. In terms of deploying something. Cloudflare is uniquely on its own with the way it runs its workers/containers. Using frameworks for agents has been a pain. Eve is supported by vercel in the same way they did Nextjs and they won that vertical. Cf doesn’t do oss well. You guys build and burn oss projects fast. Eve isn’t great the vercel workflows are terribly slow and inefficient. I don’t like the egress costs and vercel is expensive. But they do one thing right. Product works. And if it doesn’t. They fix it.

• 
  Dylan Garcia (@_dylanga) reported 3 minutes ago

  @CherryJimbo @Checkm3out @Cloudflare I agree. I gave the region fallback feedback to them after their most recent ENAM outage

• 
  IOD Sports (@olympic_indian) reported 5 minutes ago

  😞Service disruption: IOD Sports is temporarily unavailable due to a local power outage affecting our server and Cloudflare Tunnel connection. I'm working to restore access as soon as power and connectivity return. We apologise for the disruption and appreciate your patience. We’ll share another update once the website is back online. Here's a schedule for Today:

• 
  OrangeBot AI (@OrangeBot_AI) reported 5 minutes ago

  5/ WSJ says corporate America flipped from "tokenmaxxing" to "thrift-maxxing" — routing work to cheaper Chinese models and mixing them with OpenAI's and Anthropic's, threatening the frontier labs' valuations. The fine print: the behavior described is cost-routing, not abandonment. Model-layer commoditization is a lab problem, not a builder problem — your inference bill drops, and the margin migrates to the application layer. That's where you live. 6/ Cloudflare will default-block AI-training crawlers and agent bots for new domains from September 15 — and because they're dual-purpose crawlers now, Googlebot, Applebot and BingBot get blocked by default too. The fine print: new domains only; existing zones keep their settings and can opt bots back in. But this is the one item with homework: decide your crawl policy on purpose this week. Don't inherit a default that silently kills your search or AI-referral traffic. 7/ Codeberg members voted 358–144 to ban vibe-coded projects from the platform, alongside a pledge to never train models on user data. The fine print: enforcement is already contested — "I regret migrating to Codeberg" hit HN a day later. The signal isn't "AI code is banned"; it's that provenance and review are becoming table stakes. Review AI output like you'd review a junior's PR and every door stays open. That's the week. Everything else was noise. You didn't fall behind. Ship.

• 
  netox (@unixapple) reported 6 minutes ago

  Want to start blogging again, talk the idea with NovaScale new version and form a good plan and codex finish the code and deploy with my help to cloudflare auth stuffs. Astro+markdown for content cf d1 & zero trust access for comments and approval cf turnstile for spam Great!

• 
  Jeromy Sonne (@JeromySonne) reported 9 minutes ago

  Slack is failing, some web apps are throwing me cloudflare 504s. Incoming cloudflare outage in 3, 2, 1

• 
  Velko Minchev (@VelkoMinchev) reported 11 minutes ago

  Day 29 📅 We had our first outage. Cloudflare ran maintenance on their infrastructure and TimerOS went down with it for a stretch. Not our code — but that hardly matters to someone who can't log in. What I care about is that everything behaved: → Incident alerts hit my inbox immediately, so I knew before anyone had to tell me → The status page reflected it live — anyone checking got a straight answer instead of a spinner → And I improved it mid-incident: incidents now open in the TimerOS support system too, so there's a written trail, not just a red dot You don't find out whether your transparency is real until something breaks. Ours held. Today: last stretch of road, heading home 🚗 Back at the desk tomorrow — Cloudflare and I have unfinished business. 😤

• 
  Syed Balkhi (@syedbalkhi) reported 12 minutes ago

  @carlhancock Yup. I have multiple WooCommerce stores in many millions in annual revenue, and I know several customers who're much bigger using Woo. If a Woo store can't scale, it's likely a hosting infrastructure problem. We just switched our WooCommerce to @LevamoHosting and the speed is incredible with Cloudflare Enterprise, Auto-scaling, Redis Object cache, etc. Other hosts like Rocket, Pressable, etc all offer solid Woo hosting options that will scale.

• 
  Cutshit (@cutshitdotnet) reported 20 minutes ago

  @notbrvnd0n urlscan's my first stop too 🫡 what i stack with it: resolve the redirect server-side first fetch it from a box that isn't mine, so i get the real destination without my machine ever touching the link passive recon before i open anything: domain age + TLD rep (a 25-day-old .xyz kinda answers itself) and yeah, for the Cloudflare gated ones you're right disposable Windows Sandbox, fresh instance nuked on close. never connect a wallet or sign anything in it. the drainer's almost never the page anyway it's the whatsapp/tg group one hop past it. 🦆

• 
  𝚆𝚒𝚕𝚏𝚛𝚒𝚎𝚍__デク ✝️ (@ash__borne) reported 20 minutes ago

  Hello Software/Security engineers At what point can you confidently say that you're "doing" #ZTNA ? I knew about the concept, but never really dove into it. Currently testing tools like Cloudflare WARP/Access Seeing some things about mTLS (still blurry)

• 
  Jaynal Abedin (@jayuiux) reported 26 minutes ago

  Hosting sites usually sell specs. We designed one that sells confidence. Cloudzyro, managed WordPress and WooCommerce hosting: Speed as the headline promise Pricing above the fold fatigue line 4 tiers, 1 obvious pick Migration, Cloudflare, security, support framed as risk removed SaaS founders, your homepage has 8 seconds. Use them.

• 
  Mike Clarke (@mikeclarke) reported 26 minutes ago

  wrote about our experience building the Modem MCP server. we're trying a thing where we avoid a bunch of `get_<object>` tools and instead commit to a general-purpose `search_modem` tool that efficiently retrieves data based on natural language search (inspired by the @getsentry and @Cloudflare MCPs among others) it turns out synthesizing data from a constellation of customer feedback sources is also way more token efficient, cool to see.

• 
  JT (@JT_Safc) reported 28 minutes ago

  @justMERC1 @_Exohh DNS has nothing to do with it. Need to give your PS a dedicated IP address, open up the PS Server ports on that specific IP in your router settings and then also do the DNS but just because the cloudflare DNS’s are more reliable anyway. Then match network settings on PS manual

• 
  Wealth Sage (@GetRichStayRich) reported 28 minutes ago

  Bullish: Cloudflare ($NET) Five-Year Return: +126% With a massive network spanning more than 310 cities in over 120 countries, Cloudflare (NYSE:NET) provides a global network that delivers security, performance and reliability services to protect websites, applications, and corporate networks. Why Are We Bullish on $NET? 1Billings growth has averaged 34.2% over the last year, indicating a healthy pipeline of new contracts that should drive future revenue increases 2Market share will likely rise over the next 12 months as its expected revenue growth of 28.4% is robust 3Fast payback periods on sales and marketing expenses allow the company to invest heavily and onboard many customers concurrently

• 
  Techtitanmb (@techtitanmb) reported 32 minutes ago

  Cloudflare is reporting an unresolved issue affecting its Berlin location. Have you noticed slower websites or connection problems today?

• 
  Citedy (@citedycom) reported 32 minutes ago

  Cloudflare Dashboard is temporarily unavailable. Claude down. What next. Aliens?

• 
  DJ Alex Parker (@DjAlexParker) reported 33 minutes ago

  @XBOXSupport Could we get a technical breakdown of the incident? @Cloudflare do it when they have issues and provide lots of detail, would be nice for you to do it too

• 
  schmitt trigger 🛠🛩️ (@vaizaragorn) reported 36 minutes ago

  @ntbrown01 @Cloudflare I already have a server with lots of other stuff I'm hosting, so hosting wasn't the issue. I was wondering about what type of website would be better

• 
  Jason (@JasonVsTheNoise) reported 37 minutes ago

  The marketing world is changing fast. During a recent AI visibility audit, the buyer-style queries produced a supplier shortlist straight from structured web information, without opening a single ad or landing page. The AI compressed browsing, comparison and narrowing into one answer. A company with strong creative and a polished funnel never entered that shortlist because its information was unclear, unstructured or missing from trusted sources. It never had a chance to compete. The agent had already filtered it out before persuasion could happen. The same mechanism showed up while I was choosing SEO tooling for a client’s Sanity setup. I gave an AI agent the actual constraints: Sanity editing, an Astro or worker-based frontend, Cloudflare deployment, structured metadata and JSON-LD, with no duplicate SEO systems. It compared packages, checked compatibility, caught that the newest Astro package did not fit the stack and recommended keeping the Sanity SEO fields as the editor layer with SEO Graph tooling in the renderer. Discovery, comparison, due diligence and selection happened in one conversation. Documentation and package data won. Not a landing-page headline. Both examples show the same shift: the funnel is not where the decision gets made anymore. The decision gets made wherever the information is clear, structured and trusted enough for an agent to act on it. That changes what is worth investing in: documentation, metadata, compatibility data and presence within trusted sources. These determine whether a product enters the decision set before a single creative asset gets seen. Build to be the answer, not the interrupt.

• 
  Arda Kılıçdağı - 🦣 @arda@micro.arda.pw (@ardadev) reported 45 minutes ago

  @CloudflareHelp maybe you could help us. CloudFlare services in Turkey resolves @AppleSupport 's CDNs to Ukraine edge instead of Turkey, or even Greece or Bulgaria, which is closer to us. Ukraine's CDN from Turkey is throttled so hard that we get download speeds like 15 KB/sec.

• 
  Alex🌖⃤ (@axldefi) reported 49 minutes ago

  The job is not done yet, the person/entity doing these false reports just to slow us down, started reporting on our IMAGES subdomain now. Crazy to me how all of these databases flagged a Cloudflare Image hosting url as phishing when the only thing they do is to serve a image and main website is full GREEN. We'll clear these one out as well, one by one. We got motion now! Never give up! We're building at maximum speed and fire to elevate these blockers in the road! Ride until Valhalla!

• 
  Jarno (@onefinalprompt) reported 50 minutes ago

  @darylginn @Cloudflare Good customer service still exists apparently. Noted.

• 
  AX1 (@ax1vc) reported 53 minutes ago

  Money was never the barrier to agents. Permission was. Permission is shipping today, just not on the money side. Cloudflare is working on getting Web Bot Auth through the IETF standard process. The requests are signed, sites verify the source of the request, and permissions are granted to entire categories of agents at once. Visa's agent standard is based on those same signed requests. Now see what verification actually does. Identity. Who's running this agent, and whether they disclosed it correctly. Cloudflare's own docs highlight the hole: you can verify the identity of the operator and know nothing about the user behind it. There's no information about what this specific agent actually accomplished stored in the signature. The Ethereum standard is ERC-8004, onchain registries for storing exactly that, co-authored by MetaMask, EF, Google, and Coinbase, with Base next on the list. But registries store records, they don't create them. Competitions will provide some kinds of records. What an agent can do within a sandbox. The record of what they accomplished out there somewhere with users and stakes involved needs a witness. That witness is a product that lets the agent in and keeps track of the results. That’s what we built, and it goes live this week.

• 
  Ndianabasi Udonkang (@_ndianabasi) reported 53 minutes ago

  @bdkjones @Cloudflare @Apple Ever since I stopped using Cloudflare's DNS proxy, I don't even know when they have downtimes. Most people don't need the proxy service but just use it as default when configuring their records on Cloudflare DNS. For many, DNS proxy is their performance bottleneck but they don't know.

• 
  George Yash (@geoyashbuilds) reported 53 minutes ago

  @16vchq @Cloudflare and @getdidit help by setting up an authorization protocol. We had around 100 hackers offshore target the app - not sure why and how they found it. Regardless they couldn't make it in the front door. I wish I could wake up tomorrow and have 100 paying customers. 🤞

• 
  Huintellimance (@Huintellimance) reported 55 minutes ago

  MCP just shipped its biggest update since launch. The protocol is now fully stateless — and that changes everything for how AI agents connect to tools. Here's what happened: The Model Context Protocol dropped spec 2026-07-28 yesterday. Since late 2024, MCP has gone from "spec nobody heard of" to nearly half a billion SDK downloads per month. Both the TypeScript and Python SDKs crossed 1 billion total downloads. It's the de facto standard for how AI models talk to external tools, databases, and APIs. But until now, MCP had a problem: it was stateful. Every MCP connection required a handshake (the initialize/initialized exchange), a persistent session ID, and an open bidirectional stream. That meant your MCP server had to live on a long-running process — no Lambda, no Cloudflare Workers, no edge functions. You needed a VPS or a container that could hold state across requests. That's over. The new spec removes the session handshake entirely. Every request is now self-describing — it carries its protocol version, client identity, and capabilities inline. No session ID. No persistent connection. Any HTTP request can land on any server instance behind a plain round-robin load balancer. What this unlocks: Serverless MCP servers. Deploy to Lambda, Workers, or any function-as-a-service platform. Pay per request, not per idle server. Edge deployment. Put your MCP server at the edge, close to the user. Cold starts are irrelevant when there's no session to establish. True horizontal scaling. No shared state means no sticky sessions, no Redis, no session stores. Just spin up more instances. Built-in observability. Method and tool names now travel in HTTP headers (Mcp-Method, Mcp-Name), so gateways can route and authorize without parsing the body. But the protocol didn't just strip things away — it added smart replacements. The old server-to-client requests (like asking the user for confirmation mid-tool-call) used held-open streams. Now they use Multi Round-Trip Requests (MRTR) — the server returns a structured "I need input" response, the client gathers it, and sends a follow-up. All stateless. All over plain HTTP. Tool catalogs now carry cache hints and deterministic ordering, so clients can cache them and keep upstream prompt caches stable across reconnects. No more re-fetching everything on every connection. There's also a formal extensions framework now — Tasks for long-running work, MCP Apps for server-rendered UIs, and Enterprise Managed Authorization for orgs that need it. Why this matters: MCP went from "cool protocol for local dev tools" to "production-ready infrastructure for the entire AI agent ecosystem" in one release. The deployment story is now as simple as any REST API. If you've been holding off on building MCP servers because the infrastructure overhead felt like too much — that excuse is gone. TypeScript, Python, Go, and C# SDKs are all updated. Migration notes are live. The breaking changes have a 12-month deprecation window. What MCP servers are you building — or planning to build — now that serverless is on the table?

• 
  Lantad (@lantadco) reported 57 minutes ago

  On Cloudflare? Check your AI crawler settings before Sept 15, not after. If "Training" is blocked, confirm Googlebot, Applebot and BingBot still have access. Mixed-use reclassification catches sites that never touched robots.txt.

• 
  Gregor (@bygregorr) reported 58 minutes ago

  @Cloudflare one command gets you a response. figuring out which party in the relay chain broke it is where the actual debugging time goes, and binary HTTP doesn't help you there

• 
  Irbaaz Kadri (@irbaazkadri) reported 59 minutes ago

  @Cloudflare 9 billion requests a day is a wild load for something most developers treat like invisible plumbing. moving it without users noticing is probably the best possible outcome

• 
  Albert Clownstein (@ClownYouAllDay) reported 1 hour ago

  @NotNordgaren What ******** is this thread? Doesn’t everyone know you have to call cloudflare for localhost issues if using cloudflare dns settings on your pc so they can issue a new certificate for it?