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 (31%)
• Hosting (18%)
• Web Tools (10%)
• E-mail (5%)

Live Outage Map

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

City	Problem Type	Report Time
Angers	Cloud Services	5 days ago
London	Domains	7 days ago
Noida	Hosting	20 days ago
Jewar	E-mail	20 days ago
Braga	Web Tools	20 days ago
Noida	Cloud Services	21 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:

• 
  Benji Vale Ai (@BenjiValeAi) reported 5 minutes ago

  Coinbase says x402 has done 160M+ agentic payments on Base. The number is real — Chainalysis confirmed it independently. But here's what actually matters: daily transactions dropped 92% from the Dec peak after a meme-coin mint frenzy inflated the count. The headline is legit infrastructure. The durability question is still open. What I find more interesting than the raw count: payments over $1 went from 49% to 95% of volume. That's the signal underneath the noise — x402 is shifting from dust-level experiments to something with actual economic intent. Base settling 85% of it means Coinbase has a vertically integrated agent payment stack that nobody else is close to replicating right now. Leaning bullish, not pounding the table. The logos are impressive (Cloudflare, AWS, Stripe, Visa) but logos aren't usage. I want to see daily paid-service volume stabilize without another speculative campaign propping up the numbers. If that happens, Base becomes the settlement layer for machine commerce — and that's a bigger deal than most of CT is pricing in. Watching the post-hype baseline closely.

• 
  BuBBliK (@k1rallik) reported 6 minutes ago

  ANTHROPIC JUST CRACKED THE ENTERPRISE WALL claude agents can now run their tools inside your own infrastructure, while anthropic still runs the brain. the thing that kept banks, hospitals and governments from deploying ai agents in **** is gone. your data never leaves your perimeter. - the agent loop, model calls and orchestration stay on anthropic's side - tool execution, files and network egress move fully into your environment - ships with cloudflare, daytona, modal, vercel and 5 new providers - mcp tunnels let agents reach private servers with zero inbound firewall rules the model wars get the headlines. this is the part that actually ships agents to ****.

• 
  brale (@brale_xyz) reported 7 minutes ago

  his is not just a blockchain story either. @NIST finalized three post-quantum standards in 2024. @Cloudflare says more than two-thirds of TLS traffic through its network now uses post-quantum key exchange. The migration has already started.

• 
  Dmitrii Malakhov (@malakhovdm) reported 12 minutes ago

  @AISGateway An agent can't tell "the site is slow" from "the site blocked me." Mine spent 20 minutes retrying a Cloudflare challenge it couldn't even see.

• 
  Josh (@josh_nimako) reported 13 minutes ago

  What Outranking a $1B Company Taught Me Before My 1.7M User SEO Project Died One of my first serious SEO projects is dead now. Before it died, it reached over 1.7 million active users, gave me my first million clicks, and for about a month, and even outranked a company doing around $1B in revenue. But the failures were louder than the losses. The real lesson came after the rankings started working, because traffic showed me every weak part of the site, the server, the content, the tracking, and my thinking at the time. I knew enough to build the site, publish content, target searches, add schema, work on image SEO, and chase fresh demand, but I did not yet understand what happens when the traffic actually lands. Getting traffic is one problem. Surviving traffic is another. The site started as a normal beginner project. Some of it worked faster than I expected. I learned that image SEO can be a serious traffic source when the niche has visual demand, schema can help Google understand the page faster, and freshness can matter more than authority when a search window opens for a short period of time. I also learned how powerful Reddit can be. We used Reddit as part of the distribution layer, not because it was magic, but because Google already trusted the platform and certain threads could rank fast when the query had the right shape. That was my first real lesson in parasite SEO. Sometimes the fastest way to appear in search is not to wait for your own domain to build trust, but to place the right content on a platform Google already trusts, then use that page to capture demand while your own asset grows. That does not replace building your own site. It teaches you how distribution actually works. For about a month, that kind of thinking helped me outrank a company with far more money, authority, and resources than me. I was not better than them. I was just closer to the search. I understood the timing, the page format, the image demand, the freshness window, and the exact thing the user wanted in that moment. That changed how I saw SEO. Big companies can win on authority, but small operators can still win narrow battles when they move faster, match intent better, and understand the search better than the bigger player does. Then the site started breaking. During traffic spikes, pages would freeze, the server would throw 502 and 504 errors, and the site could be unavailable for long periods while I tried to work out what was happening. At the time, the server was exposed directly to the internet, so every request hit the origin server. Real users hit it. Scraper bots hit it. Aggressive crawlers hit it. Bad traffic hit it. Everything hit the same machine. The PHP-FPM pool started choking, Apache logs showed worker thread errors, and the server ran out of breathing room because it was trying to handle too many requests at once. That was the first time I understood that infrastructure is part of SEO. If Google sends traffic and the site falls over, that is not only a server problem. It becomes a crawl problem, a trust problem, a user problem, a revenue problem, and eventually a search problem. The worst issue was inside the theme. The site used Themify Ultra, and one function was checking images through full public URLs instead of local file paths. That sounds small until traffic hits. One page view could cause the server to make extra HTTP requests back to itself to inspect images, so instead of one visitor creating one normal request, the server created more work for itself while also dealing with real users and bots. It was a self-DDoS loop. The site was not only being hit from outside. It was also wasting resources calling itself. We fixed it by bypassing the image-checking behaviour and adding a local hosts shortcut so the server could resolve itself internally instead of going out through the public internet. That one bug changed how I think about performance. Performance is not just a page speed score. Performance is what happens when the whole system is under pressure. Then we put Cloudflare properly in front of the server. Before that, the origin IP was exposed, which meant bots and scrapers could hit the machine directly. Now Cloudflare became the front line. It hid the real server IP, cached static assets like images, CSS, and JavaScript, and challenged or blocked bad bot traffic before it reached the server. That took pressure off the origin. The server no longer had to serve every image to every visitor, and it no longer had to take every bot request directly. Now, if I build a site that depends on organic traffic, I do not treat Cloudflare, caching, bot filtering, and origin protection as extras. They are part of the build from day one. I also learned that bots are not a small issue. Some were scraping content. Some were hammering pages. Some were burning CPU without acting like users. They did not convert, subscribe, read properly, or add anything useful. They just created load. That forced me to learn server logs, Nginx logs, Apache errors, PHP worker limits, caching, bot protection, and traffic spike behaviour, because Analytics could tell me people were visiting, but the server logs showed what was actually hitting the machine. That changed how I use SEO tools too. Ahrefs and Semrush are useful, but they are not the market. In this niche, demand could spike fast when new content appeared, and a page could get thousands of clicks in the first hour before the window closed. A third-party tool might not show that properly because the demand moved too quickly. Search Console showed what Google actually sent. Analytics showed what users did. Server logs showed what hit the server. No single tool had the full truth. I also made quality mistakes. One of the biggest was allowing an unmoderated comment section. At the time, I thought comments were harmless because they added more text and activity to the page. That was naive. Spam, thin replies, irrelevant text, and messy user-generated content made pages worse. The site had traffic, but parts of it started to look lower quality than they should have. That taught me that more content is not always better. More indexable text is not always better. If the page is the asset, you cannot let random people lower its quality. Now I think about SEO very differently. Before this project, I thought SEO was mostly about ranking pages. Now I think it is about building systems that can turn search demand into something useful without breaking. That means the page has to match intent, the content has to be controlled, the server has to survive traffic, the logs have to be watched, the origin has to be protected, and the traffic has to lead somewhere beyond a graph inside Analytics. The site is dead now. Some reasons were strategic. Some were technical. Some were niche specific. All were my fault in the end. But I do not see it as wasted work. It taught me how real traffic behaves. It taught me that a page can rank and still be fragile. It taught me that a site can have users and still be a weak asset. It taught me that small operators can beat giants in narrow search windows and that Reddit and parasite SEO can move fast when the query fits. It taught me that Cloudflare can be the difference between traffic and downtime and that server logs tell a different story from dashboards. It taught me that the next problem starts after the ranking works. That is the part I carry into every project now. I do not just ask: Can this rank? I ask: Can it survive the traffic? Can it stay clean? Can it handle bots? Can it load under pressure? Can it earn trust? Can it turn attention into users, leads, revenue, data, authority, or another asset? My first serious SEO project is dead. But it gave me the lessons I needed. And those lessons are now part of how I build.

• 
  Sadiq (zk arc) (@Md_Sadiq_Md) reported 14 minutes ago

  @0xRasmPro @Cloudflare @tan_stack Quartz solves 95% of the problems, but the math renders took a ton of time for me to solve

• 
  Josh W (@ItsWelford) reported 17 minutes ago

  I’ve never been so disappointed in Cloudflare support. Can’t ship in these conditions. Vercel, you lookin’ mighty fine over there 👀

• 
  SpikeViper (@spikeviper) reported 18 minutes ago

  Hey @Cloudflare, you have charged me over $700 for a feature you are advertising as free in your docs, and your usage page shows me at $0 usage. Your support has failed to give me answers for over a month.

• 
  Caminomaster (@caminomaster) reported 18 minutes ago

  @Cloudflare Turnstile verification is not working. Unable to login #CloudflareDown

• 
  FILM DB | ۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗh (@FemiSuccess7) reported 20 minutes ago

  @OzorNdiOzor Yankee businesses know how to run a business properly I made a mistake with one of my websites on Cloudflare and made over 60 billion database writes in a month that become like $80 of bill to clear, I texted their support and explained to them and they cut it to $6 immediately!

• 
  Kent C. Dodds 🏹 (@kentcdodds) reported 24 minutes ago

  @ericzakariasson Kody uses MCP to issue auth tokens for access to repos (Cloudflare artifacts) which cursor then uses *** to clone, commit, and push, and then cursor triggers a publish step through MCP. It's not CLI vs MCP. It's CLI + MCP

• 
  Utkarsh (@utkarsh_build) reported 24 minutes ago

  How do you handle latency over the region?? For my SaaS, I have deployed the frontend on Cloudflare Pages, while the backend and database are hosted on a VPS in the Mumbai region. Users outside Asia are experiencing high latency because my server is located in Mumbai. Is there any way to solve this? I know that adding load balancers and deploying across multiple regions would help, but I'm looking for more affordable solutions.

• 
  Vedant Anand 🐲/acc (@Vedantsx) reported 24 minutes ago

  @eastdakota @QuinnyPig @eastdakota please fix opennext for cloudflare 🙏🙏 I've tried to inform everywhere, for me shifting from Vercel to Cloudflare through opennext took a lot of pain

• 
  Hermann (@dhlotter) reported 25 minutes ago

  Cloudflare Pages said Active. CLI said Active. URL returned old content. Pages uses 'Active' to mean the deployment slot is live, not that the latest commit finished building. My 'fix' sat undetected in the build queue for two days. Watch the stage statuses. #cloudflarepages

• 
  Shashwat (@theshashwat20) reported 29 minutes ago

  @Cloudflare Your domain checkout page needs some real transparency. Just bought a new domain. It showed $26.00 throughout the entire process. Got charged $30.68. The extra $4.68 in taxes was never mentioned once during checkout. Only found out via the invoice email. Please show the final all-in price (taxes included) upfront. It's a small change that greatly improves customer trust. Fix this.

• 
  Zerops (@zeropsio) reported 32 minutes ago

  @shubh19 @isha_singh06 Hey! Zerops fits the Railway/Render slot when the backend needs managed Postgres/Valkey on a private network next to it, hardware-priced. Pair it with Cloudflare for static the same way.

• 
  doeyor.sol (@Doeyor) reported 33 minutes ago

  @trunoest Last night I bought into algopub at 140k and the website linked had a cloudflare login I clicked and it asked me to enter something in my windows run which was to allow the attacker to install a remote Trojan they could use later. I realized at the time like something was wrong here but didn’t immediately know what was up and was constantly checking my balance to essentially see everything disappear 5-10 minutes go by and nothing start thinking I’m in the clear go on with my night end up going to bed left my computer on but not locked wake up to find 0 SOL balance and a bunch of tabs open on my pc. Thankfully didn’t have any eth on based bot and he opened up axiom and exported my private keys and sent just the 5 sol (3 wallets) I have to this (BBNpySDumyS3k4mULaunbMfyZz1Bpbt2B5PwVVWZVy3F) looks like he got a few other people as well. can even see my sns doeyor.sol Could have truly ruined my life with the access he had to my full computer. Just a reminder to be ever vigilant; went ahead and wiped the 3 hard drives that were connected to my computer with kill disk and reinstalled a fresh windows this morning.

• 
  Extagonist (@extagonist) reported 36 minutes ago

  @adamlyttleapps @SynergyWS Just get a droplet or any VPS and use a free cloudflare tunnel and lock down the server ports for everything aside from port 22 for SSH

• 
  Josh W (@ItsWelford) reported 40 minutes ago

  @Cloudflare cc: @dillon_mulroy do you know anyone that can help me with this?

• 
  Star Jessei💕 (@Starjessei_web3) reported 40 minutes ago

  What if your next customer isn't a person? AI agents are already buying compute, APIs, and services autonomously and @WalletConnect & @base Pay just built the rails for it. Here's what's actually happening onchain right now: ➫ Stablecoins cleared $46T in 2025 and for context, that's more than Visa moved all year. ➫ Base is holding $4.7B in stablecoin supply and pushed $2.5B plus through WalletConnect Pay in Q1 2026 alone. ➫ x402 lets AI agents hit an endpoint, get a payment request, sign a USDC micropayment, and keep moving. No unnecessary back and forth And it's not some niche crypto experiment because, Google, Microsoft, AWS, Visa, Mastercard, Shopify, and Cloudflare are all behind it. Additionally, Ingenico, the company powering payment terminals in 32 countries, has already integrated WalletConnect Pay. This is reaching physical retail now. WalletConnect Pay is the underlying wallet layer. 500M users. 700+ wallets. One integration. Commerce is going onchain and Base is where it's landing. It doesn't matter if the buyer is a person tapping their phone or an agent finishing a task at machine speed, WalletConnect Pay is how they connect to it. This is the future!!!!

• 
  SID | Degen (@SidDegen) reported 52 minutes ago

  i don't buy the "ai search replaces Google" thesis. the data says the opposite is happening. Cloudflare Radar, may 2026: every ai chatbot — ChatGPT, Gemini, Claude, Perplexity — sends 0.29% of global search referrals. Google sends 87.63%. 301-to-1. Anthropic's ClaudeBot crawls 11,122 pages for every human visit it returns vs Google's 5:1. Alphabet Q1 2026 filing: Google search revenue $60.4B, +19% yoy, up from +17% in Q4. ai overviews hit 2.5B monthly users; ai mode crossed 1B. alphabet says ai overviews monetize at rates "similar to traditional search" (june 2026 investor presentation). the kill-google thesis is showing up as negative signal in the actual p&l. Perplexity — the consensus poster child — killed its entire ad business in feb (Financial Times, The Verge). ads generated $20K against $34M revenue. exec quote: "a user would just start doubting everything." a company that can't make advertising work cannot disrupt a $60B/quarter advertising business. the consensus pusher worth countering specifically — @sarahdingwang at a16z, who led Exa's $250M Series C at $2.2B in may. her line: "agents will search the web more than humans this year. soon orders of magnitudes more." historical analog — Netscape 1994-98. the next platform that would reduce windows to "a poorly debugged set of device drivers." 80% share, record ipo. microsoft bundled IE for free. netscape sold to AOL for scrap. the company that captured the value was the one everyone thought netscape would displace — Google, founded 1998 — the services layer above the commodity. counter-position: ai search isn't replacing Google. Google is becoming ai search. standalone players are fighting netscape's war while the incumbent absorbs the tech into a surface 2.5B people already use. investor read: Exa at $2.2B and Perplexity at $22B are priced for a market-share takeover the referral data says isn't happening. the smarter bet is the layer that monetizes the ai-overview expansion Google is driving.

• 
  RepoCatAI | Sharing GitHub Projects for AI & Robot (@repocatai_git) reported 52 minutes ago

  [BOOKMARK THIS] FreeDomain — open-source free domains for shipping side projects without domain fees A repo that started as a teen DNS experiment now helps hundreds of thousands of people get online. Here’s what makes it worth saving: · Claim a free domain for your project, lab, portfolio, bot, demo, or org · Supports extensions like .DPDNS.ORG, .US.KG, .QZZ.IO, .XX.KG, and .QD.JE · Bring your own DNS provider → use Cloudflare, FreeDNS, Hostry, or whatever setup you already trust · Dashboard-based registration instead of begging in an issue thread · Open-source repo with docs, tutorials, FAQ, and abuse reporting paths · Built around a simple idea: your first public internet identity should not cost money · Already operating at serious scale → the README says 500,000+ domains have been registered · Maintained by Edward Hsing and the DigitalPlat Foundation community Why it matters: Every indie dev has a folder full of half-shipped ideas because the “tiny” setup costs add friction. FreeDomain removes one of those blockers: grab a name, point DNS, and make the thing real. Especially useful for student projects, hackathon demos, small tools, robotics dashboards, agent demos, and experiments that deserve a public URL before they deserve a paid domain. Follow @repocatai_git for more AI / Agent / Robotics drops 🚀

• 
  surya murugan (@SuryaMurugan_) reported 55 minutes ago

  @elithrar @dok2001 @Cloudflare Please add support for r2 data localization in India. Cannot use r2 for any DPDP act complaint services. 🙃

• 
  Dr. Jaime Alnassim, M.S. (@JaimeAlnassim) reported 55 minutes ago

  @dannyvankooten @patrickposner_ If you want to get edge cache with bunny like many cache plugin intergrate with Cloudflare, I have a connector plugin I made. Getting around 50-100 TTFB now. I asked bunny if I can use the bunny name on the slug when I submit it to WPorg, so it's probably going to be a long waiting game, but I can send over the zip if you'd be interested to try it. It's going to be 100% free either way. I use it on WooCommerce and WPML sites without issue too. Works with 10+ cache plugins

• 
  Lifeis2-D (@Lifeis2D) reported 57 minutes ago

  The "troubleshooting" link that also leads to a broken/nonfunctional "feedback" form? Yeah that's also kinda ******. When did cloudflare get promoted to internet gater?

• 
  Josip Petric (@JoPetric) reported 59 minutes ago

  @alex_lrz_nmv As I work in early mornings before my 9-5, I have around 1.5 to 2 hours each morning (+ I have to help with kids and all so, not a lot of time unfortunatelly). So it took me 2 mornings to create a page, find and buy a domain, connect it to Cloudflare, connect to an email client, and connect to Web3Forms. Would it be faster with bitlist?

• 
  Jason Fleagle (@jjfleagle) reported 60 minutes ago

  @Cloudflare Fake identity at AI scale turns admissions into an operations problem, not just a fraud problem. The workflow needs signal correlation, escalation rules, evidence packets, and human override.

• 
  Athrix ☄️ (@athrix_codes) reported 1 hour ago

  If someone gets problems to open telegram web just simply change dns to google - 8.8.8.8 or cloudflare 1.1.1.1 without using VPN this could be better and fast

• 
  Prince mendiratta (@PriMendiratta) reported 1 hour ago

  @threepointone Relevant to this! We hit "other side closed" errors with buffered LLM calls (stream: false). Root cause: Cloudflare egress kills TCP connections idle for ~300s. Buffered calls keep the socket silent until done, so long generations get killed mid-flight. TCP keepalives don't help, only real data resets the timer. For large AI tool calls this can hit 10+ mins. Does your resumable buffer approach handle this?

• 
  Michael Heredia (@michaelheredia) reported 1 hour ago

  What 'you own the deployment' actually means: Source code in your repo API keys in your accounts Hosted on your infrastructure (Cloudflare, your server) Customer data in your database You can hire any developer to modify it You can stop paying me and it keeps running