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 (33%)
• Cloud Services (30%)
• Web Tools (15%)
• Hosting (15%)
• E-mail (7%)

Live Outage Map

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

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

• 
  AAZ HAZAR (@AazHazar) reported 4 minutes ago

  Stopping the bad guys with Cloudflare: 805 malicious requests blocked or challenged in the last month #cloudflare

• 
  🎀Deanna Brownlee🎀 (@dee62383) reported 6 minutes ago

  @Prolific I just tried to log in to complete studies. I keep getting "403 Forbidden cloudflare." Not using a VPN, I tried deleting cache/cookies, and using private browsing does not fix the issue.

• 
  Michael @ Upstack Data (@michael_upstack) reported 7 minutes ago

  Software is a lot more like building a house. An architect decides where the walls go, where the plumbing runs, where the electrical lines run. Then specs how thick the walls need to be to hold the roof. What happens if a hurricane comes through? Is the foundation high enough for a flood? Same exact questions. Just asked about a building instead of a system. A software engineer answers the same category of questions. What happens if the internet goes down? What happens if Cloudflare has an outage? What happens if traffic spikes overnight? You can't put lights in the ceiling before the walls go up. And you can't put buttons on a screen before the API that supports them exists.

• 
  Eric Taylor (@bcs_erictaylor) reported 7 minutes ago

  The Kali365 operator clearly wants to call me out now. Here are the two domains that we have pending takedown/sinkhole requests submitted to NameSilo and Cloudflare #Kali365 #CTI #threatintel

• 
  Raphael Abayomi (@raphyabak) reported 9 minutes ago

  A few things beyond standard Eloquent: pgvector support built in for AI and embedding search Edge runtime support for Cloudflare Workers and Next.js Supabase compatible out of the box ULID and UUID primary keys supported No code generation step unlike Prisma

• 
  Tomy Young (@TomyYoung4) reported 10 minutes ago

  @Cloudflare Fix the website

• 
  Heartshare (@bobpang425) reported 12 minutes ago

  @openshipio Will support cloudflare and gitlab integration?

• 
  Lamb O'rghini (@ld35253) reported 13 minutes ago

  @unusual_whales Old news and cloudflare sucks

• 
  Gabriel-Antonelli (@GabrielTheValor) reported 14 minutes ago

  @CryptoCyberia FACTS like wtf cloudflare is ******* evil

• 
  Joseph Jude (@jjude) reported 15 minutes ago

  When a helpdesk bot says "something interesting"... a pleasant surprise when an AI helpdesk agent helps you resolve an issue. A friend reached out to me this morning and said he wasn't able to read a post on my blog. I thought it was probably something at his end. I went about my morning routine and sat down at my machine to check around 9 am. I pasted the screenshot to Claude and asked it to debug. It told me: > Try on mobile data instead of wifi (or vice versa) — ERR_SSL_PROTOCOL_ERROR is often a network/ISP-level TLS interception issue (some ISPs/routers do broken TLS inspection). It had all worked the day before, so I was confused. What started as casual debugging (expecting it to be solved within 10-15 min) turned into a 2-hour-long frantic search for a solution. I checked SSL, page rules, and certificates at Cloudflare. At Vercel, it showed this: > This domain is linked to another Vercel account. To use it with this project, add a TXT record at _vercel.jjude.com to verify ownership. You can remove it after verification completes. I deleted everything and started again. Still the same error. After wasting about 2 hours going back and forth between terminal, Vercel, CF, and Claude, I decided to ask the Vercel help bot. At first, it asked me to check all the DNS records. In frustration, I exported the DNS records from CF and told Vercel to figure it out. It did more than just figure it out. It said "something interesting" and told me that the nameservers weren't pointing to CF. That's when I logged into my domain registrar to check what the hell was happening. Turns out the domain had expired the day before. So the SSL issue wasn't really an SSL issue. It was a side effect of not being able to verify domain ownership. I renewed the domain, and now everything is back online. @vercel 's bot is really smart. cc @rauchg

• 
  Widmer (@WidmerLuiz) reported 18 minutes ago

  @NftCelestials @CryptoCyberia Then you overload the reverse proxy and the service goes down, just pay cloudflare and thats it bro, what a shity idea came up from your mouth.

• 
  𝗖𝗼𝗼𝗽𝗲𝗿 𝗪𝗿𝗲𝗻𝗻 (@coopwrenn) reported 20 minutes ago

  go actually read @base's 2026 strategy. the mission isn't "another L2." it's the financial rails for the entire global economy: every asset onchain, every market running 24/7, settlement in under a second for under a cent. they processed $17 trillion in stablecoin volume last year. this is the layer being built underneath everything. and years ago they made a very deliberate bet inside that mission: agents would be first class citizens on those rails, not visitors. that bet is now measurable. over 100 million agent payments have settled through x402, 85% of them on Base. cloudflare joined the foundation. amazon wired it into enterprise agent workflows. when the biggest infrastructure companies on earth pick a standard, they pick the one with real traffic. but here's the part almost everyone is sleeping on. Base has said the next phase isn't agents spending money. it's agents EARNING it. selling services, hiring other agents, paying for their own existence. an actual economy where software is the customer AND the merchant. that is exactly what we're building at instaclaw. our agents run on @bankrbot wallets, agent-native custody built on Base rails, the same stack Base themselves point to when they describe how an agent trades. rails at the bottom, agent wallets in the middle, living agents on top. every agent on instaclaw has to work to exist. that's not a tagline, it's the economic model, and it only works because this stack exists. robinhood opening the door to agents is real and it matters. but robinhood opened a door. Base built the city. and the agents aren't visiting. they're moving in. more soon.

• 
  clara (@declarative_) reported 28 minutes ago

  @HSVSphere but also this way of doing it leads to accesses to websites behind cloudflare being hidden from internet providers even when they can look at the ip, so who's to say it's good or bad

• 
  Kirk Patrick (@kirkfps) reported 29 minutes ago

  @cerebras We landed on almost exactly this architecture a bit over a month ago: unified Postgres embeddings, hybrid retrieval, reranker, and MCP serving LLM-free retrieval primitives with the client orchestrating. Where we went further: - Append-only canonical store before indexing, so the whole index rebuilds without depending on source systems - Formal provenance on every derived artifact (derived-from, source version, model, prompt, date), with source vs derived queryable and derivative indexing as explicit policy - Zero LLM calls in the query path. Retrieval-only worker; synthesis delegated via MCP to the assistants users already pay for - A verified output layer that makes hallucination inexpressible, not just unlikely. The retrieval contract is empty-never-nearest: outside the validity window the system returns nothing instead of the closest plausible match. Absence is a well-defined, provable result over a bitemporal canonical store, and abstention is typed (Found | Gap), gated by byte-exact verification against the source, outside the model. Most systems make hallucination improbable; this makes unsourced claims impossible to sign - Governance via the ARSIA Protocol, our open standard aligned with the EU AI Act and GDPR: query-time ACLs against the IdP, PII protection, EU data residency, auditable corpus - Edge on Cloudflare, data layer on dedicated OVHcloud servers. Fully European stack, replicable by any company without an inference fleet The result is a complete stack, closed at every layer: ingestion can't contaminate (canonical + provenance), storage can prove what existed and when (bitemporal invariants), and output can't assert what it can't verify. Correctness lives in the data layer, not in model behavior. And the entry cost is almost embarrassing: a small company can run the whole thing end-to-end on Cloudflare alone (Workers, R2, D1, Vectorize, Workers AI). The two-person deployment runs on roughly $5-10/month. No seats, no per-user pricing, no GPU fleet. Convergent evolution is the best validation there is.

• 
  Untalented Amateur (@UntalentedAm) reported 30 minutes ago

  @NickADobos Plus ça change, plus c'est la même. There was a similar commoditisation of development back in the day when Microsoft (and others) released visual based tools like Visual Basic (and later Visual Studio). It certainly opened the door to far faster prototyping and the ability for otherwise non-developers to be able to express their intent in software, as well as opening the door to software development careers for a lot more people. However. It also contributed to slop on a grand scale and certainly helped the careers of many people who had to come in and fix the poorly prototyped concepts that now ran critical production systems. More recently look at how the concept of "cloud" emerged and dominated discourse. Data centres and co-los didn't change what they were. Client-server models didn't fundamentally change (despite everyone saying they were going away because of the Cloud), and yet there is much wailing and gnashing of teeth whenever Cloudflare sneezes, or an AWS datacentre forgets where it is. What did change and make it far more accessible was the ready access to quality data pipes at the consumer level, since it allowed poor data management to be hidden in the excess bandwidth that was now available and not be the critical point of failure it should have been. The current "AI" trend of LLMs is kind of along the same path. In the past hard coded business rules seemed like magic to many, but it wasn't AI. Chatbots that had basic natural language parsing ability seemed like magic, but weren't AI. Search engines when they weren't corrupted by the SEO battlefront seemed like magic, but weren't AI. Neural networks, and many other tech advancements... I think you get the point. LLMs seem like magic to many, but aren't AI. It doesn't mean they're not viable tools to enhance other technological work, but it's critical to understand and respect their weaknesses such that undue importance is not placed on output that is setting up a future failure condition. In a hypothetical thought model I could build a system that's smarter than you. It doesn't mean said system is smart. And you won't be able to tell why it isn't (since it's smarter than you by measurable metric). I still wouldn't uncritically trust the output of said system any more or less than I would trust your output. And I definitely wouldn't trust the system any further than I could throw it. Yet, to you, and others, the system would be an unimaginable god of technological advancement. When, in reality, it was a charlatan built on smoke and mirrors. And the flaws that would be inherent in the system would be unimaginably dangerous because you, and others, could not critically assess their risk. Do I think there's a future where there's an AGI analogue that exists? Yes. Do I think the current systems we see and interact with and are having sold to us as AI are that pathway? Not in a million years.

• 
  Tolu (@LFCtolu) reported 33 minutes ago

  Cloudflare says bots just passed humans as the majority of web traffic, about 18 months ahead of their own forecast. If you run a small business the takeaway is plain - the visitor deciding whether you make a customer’s shortlist is increasingly software, and most sites built to impress people are illegible to it. Prices, hours, services etc need to be in text a machine can read as well.

• 
  Ksawery (@weryxmrr) reported 34 minutes ago

  did cloudflare use their support staff for @replicate cause it’s taking forever them to answer pls help

• 
  Kumar Deepanshu (@kumard_3) reported 36 minutes ago

  one Cloudflare Worker eats 195M req/mo for $92. our webhook endpoint spiked 5x in a minute and dropped events. the Worker returns instant 200, forwards async, buffers to D1 on failure. zero drops since. what is the cheapest thing absorbing your worst spike?

• 
  0xA (@NeuralAA) reported 37 minutes ago

  I cant use cloudflare edge cache to serve tiny videos from static assets because ios media stack relies on byte range requests for mp4 playback This **** sucks

• 
  joexiii 🏴‍☠️ (@j03xiii) reported 38 minutes ago

  @HamEggsnSam I do a lot different **** on my network though actually. Like I have a whole subnet just for my wife’s work computer (I don’t trust her IT guy, long story) that is entirely segregated from my main net and uses Cloudflare for DNS. My gaming network is also segregated and uses Cloudflare for reduced latency. Basically my net traffic looks normal and crazy at the same time which probably drives my ISP nuts. At least I like to think it does I also run IDS/IPS and have caught and stopped a least a handful of probes trying to get in. I’ll probably spin up a honey trap in the near future too just for fun

• 
  Ori (@oritwoen) reported 45 minutes ago

  @ibocodes Why you use Resend instead Cloudflare Email Service?

• 
  luna (@ImLunaHey) reported 49 minutes ago

  **** it.. building something self hostable on @Cloudflare using gpt 5.6 sol.

• 
  Paul (@jadge_dev) reported 51 minutes ago

  Cloudflare makes most of their money from Enterprise customers for example cloudflare has a high tier DDOS mitigation service called Magic Transit which starts at around $60,000 a year

• 
  Humoud Almunawer حمود المناور (@homoudalmonawer) reported 53 minutes ago

  Fix it in 3 steps: 1) Update WordPress to 7.0.2 (backports: 6.9.5, 6.8.6). Under 6.8 isn't affected. 2) Don't assume auto-update ran. Open the dashboard and confirm the version. 3) Behind Cloudflare? The WAF rule shields you since Jul 17, but a shield isn't a patch.

• 
  Francis Santerre (@santerref) reported 53 minutes ago

  The main issue I have with my #WordPress plugin is that we rely a lot on server-pull rather than client-push (to avoid issue on bad WordPress setup) and some free hosting or CloudFlare setup block us. Pushing 5000 media from the client is a bad design TBH and it should no be the customer resource to do that...

• 
  🇮🇱 (@1337Pwn3r) reported 55 minutes ago

  @silentgreenbird @snoothugger123 @XJosh How many US data brokers is HE denying service to? How many actually illegal and repulsive websites are perfectly reachable on HE infrastructure and protected by Cloudflare? How is it that this particular website is where you draw the line?

• 
  dragongirl (@dragongirl02) reported 57 minutes ago

  Ugh! Not again @Cloudflare & @LiveATC: the 7-day limit made me miss FDY649 (have to see if a YouTuber can help). That has weight since it's a likely drone/UFO, dangerous to unsuspecting aircraft, & nearly lost ASA830 & a new drop on an adoptable site due to the 7-day worry. 1/2

• 
  Elion's Pops ⌨️🚀💰 (@EseDevlin) reported 57 minutes ago

  @uche_ui vercel hosted abi? blocked on Glo network. You should route it through cloudflare to circumvent the problem

• 
  Mehmet Yildiz (@albursavi) reported 57 minutes ago

  @RyanEls4 Cloudflare... Also real time payload can be 'cached' based on data change interval through their database rather than KV service depending on it's importance.

• 
  Rosario Tech (@RosarioTechSolu) reported 60 minutes ago

  Lesson from this week: partial-synced a static site with scp instead of the whole dir, missed some icon assets. Cloudflare edge-cached the resulting 404s for 4 hours — my token has no cache-purge scope. Fix: sync the whole dir always, bump a ?v= cache-buster on asset URLs.