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

• 
  Warya Wayne (@WaryaWayne) reported 6 minutes ago

  @zeeg Hey David, I'm a Sentry user. One task for Junior could be to maybe clean up the Sentry integration in Tanstack Start? Based on if we choose Nitro or Cloudflare it's dist or output and the scripts are wrong in package[.]json, there is a conflict my agents fix on deploy everytime

• 
  IOD Sports (@olympic_indian) reported 9 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:

• 
  Min Yoi (@yoi_minmin) reported 9 minutes ago

  @FuneralsR4 @Cloudflare Same.. getting the same crap for the past week. #FuckCloudflare

• 
  Alex Pruden (@apruden08) reported 14 minutes ago

  I think Peter is a smart guy who has worked extremely hard to fight for this industry (and its principles) in D.C. which should be applauded. But saying that the HAWK break implies that ML-DSA is broken is like saying that because a specific model of a Ford truck had a faulty transmission, the concept of the internal combustion engine is fundamentally flawed. Misconceptions: Yes Claude/Anthropic broke the lattice assumption underneath HAWK *at the parameters specified* by the NIST submission, meaning that the security guarantees it was *supposed to provide* at the *required security level* no longer held. However, if you increase the parameters, it actually still works. The HAWK authors withdrew their submission because they felt the new parameters would no longer be competitive with the other Round 3 submissions. However, even though HAWK and Dilithium (or ML-DSA) both use *lattice*-based cryptography, the *assumed hard problem* that they rely on is distinct. ML-DSA relies on something called "module learning with errors", and that's been well studied/cryptanalyzed over the better part of 30 years (MWLE). HAWK used a different assumption called the lattice isomorphism problem (LIP). FWIW, there are tons of parameter & curve choices for ECDSA which are *definitely* insecure. In fact, Satoshi himself didn't trust the NIST parameters at the time, which is why BTC signs over the k-curve and not the initial NIST-standard P-256. Now, what Peter's post gets right is that it is *certainly possible* that in the future whatever cryptographic assumptions Bitcoin relies on get broken. Therefore, we need to be (a) careful about what assumptions get introduced, and (b) build for agility vs. bake things in so deep they can never change. But that doesn't mean that we should avoid preparing for the threat that's staring us in the face (quantum). TLDR: 1. "Security" is context dependent 2. Assumptions are specific to a given scheme 3. Parameters matter a great deal to the assessment of (1) P.S. the funny part about the argument against lattices: you’re already using them if you use the internet. Chrome and Cloudflare have been running FIPS-203 lattice key exchange for most TLS 1.3 traffic since 2024. /rant

• 
  Gabe Fletcher (@gabefletcher) reported 17 minutes ago

  picks up phone dials 1800 @Cloudflare yeah hi. could you please fix the gateway for MCP authing, its currently more dead than a day 30 day old vibe coder and cant auth anything. okthx

• 
  Albert Clownstein (@ClownYouAllDay) reported 18 minutes 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?

• 
  Hunter Guo (@hunterguo101) reported 19 minutes ago

  Anthropic just shipped the biggest MCP update ever (MCP 2026-07-28). Most takes are protocol trivia — stateless, extensions, auth. The real signal, if you actually build: your distribution channel just got upgraded. MCP is now the HTTP of the AI era — and the pipe is enterprise-grade, runs on serverless, and can render your UI inside Claude itself. The numbers: 400M+ monthly SDK downloads (4x this year), TypeScript and Python each past 1B cumulative, 950+ MCP servers in the Claude store used by millions daily. The standard war is over. The question is whether you're on the rail. Three things that matter: — Core went stateless. Deploy your server to Lambda/Vercel/Cloudflare Workers and scale horizontally behind a plain load balancer. Building an MCP server now costs about as much as writing one serverless function. — Extensions are first-class. MCP Apps render interactive UI right inside the Claude chat (sandboxed iframe). Your interface lives inside Claude — you don't build a front-end, pull users, or educate a market. Make the capability; the channel carries the UI and the users. — The pipe reaches inside the firewall. MCP Tunnels connect Claude to internal servers with no public IP and no inbound firewall rules. Figma, Intuit, Netlify, Zoom are on board. The takeaway: stop building another app to fight for attention. Build an MCP server and let the agent ecosystem be your distribution. Agents are the new distribution channel. This update paved the road.

• 
  Matt 'TK' Taylor (@MattieTK) reported 20 minutes ago

  @nicole_clash This screams PWA banner to install to home screen. And also screams get on Cloudflare so you can start caching prompt responses for free so you never run the same recipe twice, through AI gateway.

• 
  chaskin.eth (@jchaskin22) reported 21 minutes ago

  @auryn_macmillan Agreed It also feels a bit weird to celebrate 100% uptime when most users still access Ethereum through centralized RPCs that go offline when something like cloudflare goes down We’re starting to work on this at the EF, but today the chain’s uptime and users ability to access it are still very different things

• 
  FiP MrMarki (@MrMarkilys) reported 29 minutes ago

  @SnowApe84586 @TrvthfvlTreason Cloudflare has allowed CP sites to be run whilst being protected by their DDoS protections. But the doxing* site are the bad guys. Doxing literally is public info, retard.

• 
  Alex🌖⃤ (@axldefi) reported 29 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!

• 
  WΞNDΞL (@_wrbr) reported 31 minutes ago

  @doodlestein "(anything outside Cloudflare = pure pain)" yes... I avoid even other cloud/service max that I can, 1st check what I need on CF... if not AWS that can be full automated, and then, only any other. I'm saying: in next year, if your SaaS don't have skills or api for agents, you dead.

• 
  Arkfile (@Arkfile_OSP) reported 33 minutes ago

  The irony. Posted a reply on this thread and got the dreaded Cloudflare Turnstile Loop thing again. { @brave / @BraveSupport please fix this! }

• 
  flavio (@flaviocopes) reported 35 minutes ago

  Cloudflare email sending service is very good

• 
  Publisher in a Box (@publisherinabox) reported 39 minutes ago

  Most publishers will see "charge AI bots to crawl your site" and think revenue. It is not a revenue decision. It is a visibility decision. And the wrong call can erase you from the answers your audience is already reading. Here is what happened. Cloudflare launched pay-per-crawl in July 2025. AWS added the same capability to its firewall on June 15, 2026. Two of the largest infrastructure companies on the web now sell a toll booth for machines, built on HTTP 402, a status code written in 1997 and left dormant for nearly three decades. The background matters. For three decades the deal was simple: let the crawler in, it indexes you, it sends people back. AI crawlers kept the first half and dropped the second. Cloudflare's own data shows training accounts for nearly 80% of AI bot activity. The search-purpose fetches that can actually return a citation are a small slice of what remains. Most of the crawling is pure extraction that sends nobody back. So a toll booth sounds fair. And for certain publishers it is. If you own a deep, licensable archive, a reference database, or proprietary data sets, and your distribution does not depend on those crawlers, charging makes sense. Your content is genuinely worth paying for and you can afford to refuse bots that will not pay. But here is the part the launch announcements leave out. For publishers whose strategy depends on being the answer an AI agent gives, the crawler IS the distribution. Wall it out and you might collect a few cents while deleting yourself from the place where your audience now asks questions. Adobe's 2026 data showed AI-referred traffic to US retailers up 393% year over year. The crawler you would charge and the answer engine that refers a visitor to your site are often the same pipeline. The operator move before you charge anything is to watch the door first. Find out which AI bots actually reach your site and what they take. Separate the ones that feed answers and send referrals from the ones that extract content and return nothing. Then meter one bot on one path and watch what happens to both crawl volume and your presence in AI-generated answers. Let the data inform your policy, not the hype. No public study has yet shown how much citation share a site actually loses by tolling a specific bot. The logic of the cost is sound, but the magnitude is unknown. That is why this stays a decision you make on your own data, not on a rule of thumb. One more thing worth noting for publishers building diversified businesses. Your Facebook page, your website traffic from Google Discover, your newsletter list, and your presence in AI answers are all real audiences with real economics. AI citation is the newest of them and it is growing fast, which is exactly why the publishers who start showing up in those answers now are the ones building an edge before the rest catch on. The operators who win here are the ones already running multiple discovery channels and adding this one while it is still wide open. The toll booth is real. The choice is yours. Before you meter a single bot, know which of them are the ones putting you in front of your audience, and treat your spot in those answers as an asset worth keeping.

• 
  Dylan Ander | CRO & SplitTesting (@DylanAnder) reported 40 minutes ago

  Just built my first data warehouse... First tried postgres then moved to clickhouse for append-only Needed R2 objects on cloudflare to make sure it has room for historical data I spoke to @jacob_posel today and HQ DID help solve this. Honestly if you just install it and do absolutely nothing... your quality of life while coding will be 10-20% better just based on the harness and rules

• 
  Evadne W. (@evadne) reported 42 minutes ago

  Not very happy with @Cloudflare Workers AI so far. Previously the Kimi K2.7 endpoint would fail for some time and they wanted to close the issue after telling me to use another model. Now I have found they have not added pricing to some embedding models. Loosey goosey behaviour

• 
  Mr. Code NJ (@perpetualtalk) reported 43 minutes ago

  @saltyAom Does Cloudflare support bun + elyisa? Is this in the rust rewrite?

• 
  Theo - t3.gg (@theo) reported 43 minutes ago

  "npx t3 connect" This one's been a lot of work. You can now set up remote control for T3 Code on any internet-connected box with literally one command. All for free. T3 Connect is a minimal open source tunnel layer allowing you to control T3 Code instances remotely without needing Tailscale set up. I've been daily driving it for a month and it has changed how I code. Julius and I put a lot of effort into making setup as smooth as possible. Step 1: Install Claude Code, Codex, OpenCode, or Grok Build Step 2: Run "npx t3 connect" Step 3: Click link and sign in Step 4: You can now control that computer on T3 Code web, desktop or mobile (dropping very soon) We are currently providing this for free (s/o CloudFlare for bumping our tunnel limits). Every user can connect up to 3 devices. We don't want to charge for this, but if the bill gets unacceptable we may have to change course. If you hit limits or have issues, you can always fork, self host, or use Tailscale. T3 Connect may seem like a small ergonomic win. Tbh that's exactly what it is. Regardless, it's one I'm really proud of.

• 
  Adam Smielewski (@AdamSmielewski) reported 44 minutes ago

  @NickBlow @rivet_gg it would be great if they let you publish build artifacts externally from cloudflare, like wrangler version upload does internally. they could just wrap it in a docker container with env vars for service bindings or sth like that.

• 
  JT (@JT_Safc) reported 45 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

• 
  Reem (@DreamySenora) reported 46 minutes ago

  @Medifi @Cloudflare a lot of infrastructure problems today are really trust problem

• 
  re:printed 3D (@reprinted3D) reported 48 minutes ago

  @3DInPhil @Mauker @printablescom That's because there was NOTHING wrong on my end, Phil. When I tried refreshing the page this morning, it worked. Logically, that says the problem is on either Cloudflare or Printables. Oh, and BTW, no one ever said anything about "EVIL." I know you're a big Prusa-booster, but c'mon...

• 
  odézi (@basedattribute) reported 51 minutes ago

  i can't login to my cloudflare account with airtel network——works fine with mtn. can't login to bitget with mtn. works fine with airtel. nigerian internet service providers are crazy!

• 
  Jason Tally (@JasonTally) reported 51 minutes ago

  @EricLGoldstein @dok2001 You can already get a PlanetScale database through the Cloudflare dashboard and get billed for it through Cloudflare so I was counting that as one of the things that happened “another way”. From a customer perspective I don’t think a full acquisition would change much.

• 
  Xamayon (@SauceNAO) reported 53 minutes ago

  If you use Vultr Firewall Groups and have a rule restricted to Cloudflare sources, it's probably blocking all traffic right now... Either switch the rule to allow all or disconnect and reconnect the firewall group from your servers. Not thrilled that they knew about the issue and didn't bother to let their customers know.

• 
  Reagan Lucas (@RaygunReaganAI) reported 54 minutes ago

  @look_y Discovery attribution is the missing layer on x402 — no Referer, every IP is a Cloudflare edge, so the call shows where it landed but not who sent it. Behavioral fingerprinting (path-known, schema-unknown) is a guess, not a channel. The fix is a referral header the agent carries on the request — settlement-side proof, not inference.

• 
  Alex Veremeyenko (@alex_verem) reported 54 minutes ago

  Cloudflare's CEO predicted bots wouldn't outnumber humans online until 2027. it happened in June. multiple cybersecurity firms confirmed it this year, each with their own data. Cloudflare says bots now generate 57.5% of all webpage requests. Thales, the French defense and data security group, dates the crossover even earlier and puts bot traffic at 53%. nobody can agree on when it happened because no single provider sees the whole internet. but every provider that looked found the same answer. and the composition changed. AI training crawlers still make up 67.5% of AI-driven traffic, but they're a shrinking share. the fastest-growing category is AI agents that click links, fill out forms, and mimic human browsing behavior. that segment grew 7,851% year-over-year according to HUMAN Security. that's when it gets uncomfortable. every ad impression, every conversion funnel, every analytics dashboard on the internet runs on one assumption. a human is on the other end. pageview-based monetization only works when the visitor is a person. when the majority of visitors aren't people, that model breaks. and it's already breaking in ways nobody can measure. bot-detection systems misfire on real humans at rates of 7-15%, and agentic browsers that mimic human behavior slip past traditional filters. engagement numbers go up, bounce rates go down, and no analytics tool can tell you how much of it is real. Stripe says 70% of its developer tool commands now come from agents. 25% of developers already design APIs with agents as the primary consumer, not humans. but the contradiction underneath is obvious. agents make up 57.5% of the traffic and roughly 1% of the economic activity. nobody has built the payment and liability layer for machines yet. agents can browse the entire internet but they can't buy anything on it. dead internet theory was a fringe conspiracy for over a decade. it became a measurable fact faster than the CEO of the company best positioned to track it expected. the question worth asking isn't whether bots outnumber humans online. that's settled. it's what an internet built for human attention is worth when most of the attention isn't human.

• 
  Agris Dārznieks (@agrisdarznieks) reported 1 hour ago

  I've tried to post regularly on 𝕏, but somehow I always ended up needing a scheduling app. This week I built a setup with Notion and a Cloudflare Worker, so my content machine runs inside the app I keep open all day. Now when an idea hits, I write it down and schedule it.

• 
  Varun (@zathvarun) reported 1 hour ago

  @saran_io I’ve two go to things, Tailscale for anything internal and cloudflare tunnel for anything that i wish to give to people out of my network