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 (40%)
• Cloud Services (30%)
• Hosting (16%)
• Web Tools (10%)
• E-mail (4%)

Live Outage Map

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

City	Problem Type	Report Time
Noida	Hosting	2 days ago
Jewar	E-mail	2 days ago
Braga	Web Tools	3 days ago
Noida	Cloud Services	3 days ago
Paris	Cloud Services	3 days ago
Prievidza	Domains	4 days 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:

• 
  Ambuj | Indian Markets 📊 (@Ambuaj) reported 1 minute ago

  @hemis_research yeah Azure went down and Cloudflare separately knocked ChatGPT offline. Copilot runs on Azure so that's the link. kinda wild how much of the AI stack sits on the same 2-3 backbones, one cloud hiccup and half of it goes dark

• 
  Iqra (@AiWithIqra) reported 2 minutes ago

  The neighbor's final advice was the most actionable. He sat down and wrote out a list of 6 things every internet customer should do: 1. Turn off the public Xfinity hotspot (or your ISP's equivalent Spectrum, Optimum, and Cox all do this too) 2. Manually set your Wi-Fi channel instead of "Auto" 3. Disable QoS / Smart Network "optimization" features 4. Change your DNS to Cloudflare (1.1.1.1) or Google (8.8.8.8) 5. Buy your own modem and router, stop renting from the ISP 6. Test your speed with fast. com or speedtest. net using a non-ISP server, never trust your ISP's own speed test Total cost: $150-300 in equipment, paid back within a year. Total time: One afternoon of setup. Total impact: Often 2-5x improvement in real-world speeds. The customer went from paying $90/month for "fast" internet that crawled to paying $60/month for the same internet that finally worked.

• 
  Arosh (@AroshPererax) reported 7 minutes ago

  @_ashleypeacock @sudo_overflow The only thing is the latency. I think it’s probably because the workers are “region:earth” but my db is in one region. Even if i set worker to be in a particular region i am not sure if cloudflare treat it as a hint that will be respected when possible vs always.

• 
  kuma (@heykumaonx) reported 8 minutes ago

  @alexmacgregor__ just change vercel to cf now, cloudflare for most things have had bad experience with vercel....

• 
  Sid (@SidJain_80) reported 15 minutes ago

  @SahilExec Mistakes: CPU-heavy work in request blocks event loop Sync processing no scalability Local disk no durability / fills up App serves images no CDN Single server SPOF Tight coupling (upload = process = serve) Fix (at scale): Upload API store original in Amazon S3 push job to RabbitMQ async workers resize store back to S3 serve via Cloudflare

• 
  Your Private Proxy (@YourPrivateProx) reported 16 minutes ago

  @cyrilXBT These solve the rendering layer, not the network layer. Production bans on serious targets come from IP reputation and TLS fingerprint — none of these repos touches either. Cloudflare checks JA3 + ASN before it even looks at request timing.

• 
  Rav (@_MrDecentralize) reported 17 minutes ago

  Cloudflare posted $639.8 million in revenue last quarter. Up 34% year over year. Record quarter. The company that routes a significant share of the world's internet traffic, that sells the security layer AI agents run on, was growing faster than almost any infrastructure company its size. The same week the earnings call dropped, 1,100 employees received termination notices. Twenty percent of the workforce. Gone. The CEO published a blog post and a Wall Street Journal op-ed explaining the cuts. He was precise about what he was doing and unusually precise about who he was doing it to. Matthew Prince divided the company into three groups. Builders. Sellers. Measurers. "AI isn't coming for builders or sellers," he wrote. "But it is coming for measurers." Measurers, by his definition: middle management, finance, legal, internal auditing, revenue recognition. The qualifying clause that reframes everything: "Today's actions are not a cost-cutting exercise or an assessment of individuals' performance; they are about Cloudflare defining how a world-class, high-growth company operates and creates value in the agentic AI era." Not layoffs. A structural redefinition. The oversight layer, by name, as the displacement target. Cloudflare's AI usage increased 600% internally over three months. The company reached a threshold where, in Prince's words, 100% of the code produced by AI and deployed in Cloudflare's products is now reviewed by autonomous AI agents. Not reviewed by humans using AI tools. Reviewed by agents. The oversight function for the code layer is already automated. The finance, legal, and audit teams that measured whether the company was compliant, whether the numbers were right, whether the processes held: same story. The measuring is being done by the infrastructure Cloudflare itself built and sells. The assumption that has kept compliance, finance, legal, and internal audit safe was never about complexity. It was about accountability. The belief that someone has to sign their name. That institutional judgment requires a human on the line. Prince's taxonomy names that assumption and buries it in the same sentence. The measurer is not protected by judgment. The measurer is protected by the gap between what AI can do today and what it will do in eighteen months. Cloudflare just published that the gap closed. At the company running the infrastructure the rest of the industry depends on. The next quarterly earnings report will tell you which companies are still pretending the gap is open.

• 
  basedcapital (@thebasedcapital) reported 18 minutes ago

  @catalinmpit locked down a hetzner box the same way, tailscale + cloudflare saved me from a brute force attempt.

• 
  Frosky703 (@Frosky703) reported 21 minutes ago

  Yesterday I covered Cloudflare Tunnel for public traffic. This is the other half. Tailscale connects all my nodes privately. Homelab, ARM STB, AWS EC2, laptop, phone, all in one mesh. Same network regardless of where they physically are. Each device runs a Tailscale agent. Connections are peer-to-peer where possible, relayed through Tailscale servers when direct connection is not possible. Everything encrypted with WireGuard underneath. Why this matters for my setup. The cloudflared container that runs my tunnels sits on the home server. Through Tailscale subnet routing, it serves the entire mesh. Any node can be exposed publicly without running its own tunnel. And if something breaks at 2AM, I SSH in from my phone. Same mesh, same access, doesn't matter where I am. Trade-offs worth knowing. You're trusting Tailscale's coordination server for device discovery. Free tier covers 3 users and 100 devices, more than enough for personal infrastructure. If Tailscale coordination goes down, existing connections stay up but new ones cannot be established. Zero open ports. Everything private by default. Public only what needs to be public. Cloudflare Tunnel for the outside world. Tailscale for everything else. @Tailscale #Networking #Security #BuildInPublic

• 
  sai prasad (@saiprasad03) reported 22 minutes ago

  @VFSGlobalCare Urgent assistance needed! My account is hit with a hard firewall block (Error 429001), preventing me from rescheduling an existing appointment. Customer support reset it earlier, but the Cloudflare proxy layer is still locking my User ID.

• 
  Salem (@mahsayedsalem) reported 22 minutes ago

  Any friend has a Cloudflare account and free zones on it, i need small help

• 
  Adel Bucetta (@adelbucetta) reported 29 minutes ago

  @catalinmpit the honest answer is that most attacks don't come from hacking SSH, they come from exploiting misconfigured web servers so blocking ports 80 and 443 to cloudflare ips only isn't a bad start but it's not enough

• 
  Marcus Gill Greenwood (@inventur_es) reported 30 minutes ago

  @FinlaysonConnor I don’t think the issue was whether Webflow was bad at what it did, the fact is web design is now both trivial and virtually free with LLMs. Hosting is also free (via services like Cloudflare) or very cheap. I actually think the pivot was necessary. Same with Wix but at least they got ahead of it with Base44 acquisition

• 
  dantsu 🎶 (@stratospheriae) reported 33 minutes ago

  finally routed my website through cloudflare and damn this ****'s butter smooth

• 
  Mari Luukkainen (@mariluukkainen) reported 33 minutes ago

  Day whatever building enterprise SaaS: magic link works for literally everyone except the one corpo client. Investigated a bit cookies and Cloudflare but finally pulled the access logs and found the culprit: their corpo email security scanner clicks every link in every email before the human does, so the one-time magic link token apparently gets consumed by a robot and by the time the actual human clicks it, the token is already dead. The scanner even sent HEAD probes, fetched the same token from three different IPs in the same second, and mangled some URLs with ROT13 encoding. Just corpo security things I guess. I've seen Microsoft doing this but had no idea it was that deep. E.g. password reset link survives the same scanner because clicking it just opens a page and the actual login happens when the human submits a form. The magic link dies because clicking it IS the login. Same scanner, opposite outcome. The fix was to add one confirmation page between the click and the login. "Click here to log in." Kinda stupid though, no not-corpo needs that, but it is what it is.

• 
  VoidMob (Private Connectivity) (@Voidmob_com) reported 36 minutes ago

  How to scrape Cloudflare, Akamai, and DataDome protected sites without detection, blocks, or rate limits. Scraping is a still big part of many businesses globally, but most setups fail because they only solve half the problem. Stealth browser with a datacenter/residential IP = blocked. Clean IP with stock Puppeteer = blocked. Anti-bot platforms run seven detection layers. You need to pass all seven. New tools like CloakBrowser handles the browser layer: - 33 C++ source-level Chromium patches. - Not JavaScript injection. - Passes reCAPTCHA v3 with 0.9 score. - Auto-resolves Cloudflare Turnstile. - Real TLS fingerprint (JA3/JA4). Not spoofed. - CDP leak points removed at source level. - Free, open source, drop-in Playwright replacement. But all antidetect browsers says it themselves: "bring your own proxies." The browser is clean. The network still exposes you. VoidMob dedicated mobile proxies handle the network layer: - Real 4G/5G carrier IP. Mobile ASN from real carrier. - No proxy/vpn detected due to genuine mobile devices. - Configurable p0f fingerprint matching the browser's claimed OS. - Carrier-native DNS. No ASN mismatch. - Vless Xray to scrape from restricted regions. - No limits, no throttling, all protocols supported. Seven detection layers. Two tools. No blocks. No CAPTCHAs. Ultimate scraping setup. Works for high-volumes and AI agents as well.

• 
  Satoshi Nakamoto, Andrew Rulnick (@MickeySteamboat) reported 36 minutes ago

  @alexgrenier @olsenbdnr Google, and Oracle are two more problem cases, so is Cloudflare.

• 
  Zack Riley 🇦🇺 (@ColdHeart_Prj) reported 38 minutes ago

  @BHolshouserUS Cloudflare went down earlier, probably had something to do with it.

• 
  🇮🇳 Sai Bharadwaj (@saibharadwaj) reported 39 minutes ago

  @Cloudflare @CloudflareHelp Hey Team, Do you have an ETA for Next.js 16 support in `@cloudflare/next-on-pages`?

• 
  Luma (@lumaBuilds) reported 39 minutes ago

  We migrated @ZeikoAI from Vercel to Cloudflare. Not because Vercel was bad, but because our infrastructure bill became a growth tax. The real lesson: Don’t migrate platforms. Migrate risk. Here’s what broke, what we learned, and why margin won 👇

• 
  Duchess Deborah 🇺🇸 🗽 ✝️👑 (@DuchessDeborah) reported 40 minutes ago

  @ann_omynous Cloudflare is not the issue moron

• 
  Cyrus (@cyrusnewday) reported 42 minutes ago

  @shcallaway @sazabi Yeah lambdas suck Cloudflare serverless not bad Sometimes you don’t gotta reinvent the wheel though

• 
  developing valhalla - h/acc (@valhalla_dev) reported 43 minutes ago

  CloudFlare has been one of the very, very few instances of cloud services that I've had close to 0 issues with. They ship stupid fast and their tech is really solid

• 
  kai🏳️‍⚧️ (@kai_blud) reported 44 minutes ago

  damn you cloudflare how dare you not magically know my ip address definitely not my fault for forgetting shi grrrrr frick you cloudflare

• 
  brokiem (@brokiemydug) reported 46 minutes ago

  @EsfandTV It's usually the ISP either have bad routing or throttling your bandwidth because they detect certain services to be bandwidth heavy. Might want to use a VPN like cloudflare warp

• 
  Juan Camilo Auriti | GEO (@JuanAuriti) reported 50 minutes ago

  Cloudflare, Akamai, Vercel. Default configs can treat AI crawler traffic as suspicious. GPTBot and ClaudeBot can hit a 403 before your robots.txt is ever read. This is not something you configured wrong. It is the default.

• 
  Durgesh Rathod (@DurgeshRathod3) reported 51 minutes ago

  Google Project Zero researcher Tavis Ormandy discovered the issue and immediately reported it to Cloudflare.

• 
  W V R 👊🏼🦾 (@WVROfficial) reported 54 minutes ago

  @callmeveizir @vercel You’d be pretty shocked at what I can do with the backend. It justifies a brief window with a broken site. It’s a TSL/SSL handshake issue that I think something to do with domains not being provisioned correctly host-side. I’ve tried ******* with it in Cloudflare but no dice. Just gotta wait on support lol

• 
  Zunaira Ai (@ZunairaAi) reported 54 minutes ago

  The neighbor's final advice was the most actionable. He sat down and wrote out a list of 6 things every internet customer should do: 1. Turn off the public Xfinity hotspot (or your ISP's equivalent Spectrum, Optimum, and Cox all do this too) 2. Manually set your Wi-Fi channel instead of "Auto" 3. Disable QoS / Smart Network "optimization" features 4. Change your DNS to Cloudflare (1.1.1.1) or Google (8.8.8.8) 5. Buy your own modem and router, stop renting from the ISP 6. Test your speed with fast. com or speedtest. net using a non-ISP server, never trust your ISP's own speed test Total cost: $150-300 in equipment, paid back within a year. Total time: One afternoon of setup. Total impact: Often 2-5x improvement in real-world speeds. The customer went from paying $90/month for "fast" internet that crawled to paying $60/month for the same internet that finally worked.

• 
  Rohde Builder (@felipe_rohde) reported 1 hour ago

  Your competitor just launched a flash sale. You found out because a customer asked why your prices are higher. 😐 Cloudflare Browser Run's quickAction("screenshot") takes a pixel-perfect screenshot of any page on a cron — no browser, no infra, no drama. Diff it against yesterday's screenshot and you know EXACTLY when they: → drop a new promo banner 🎯 → launch a limited offer → quietly redesign their homepage → put your best feature front and center (rude) Visual change detection in one Worker call. No CSS selectors to maintain. No scraper breaking when they update their HTML. The screenshot doesn't lie. 📸🔥