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

Live Outage Map

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

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

• 
  ZEE (@CodeWithZeee) reported 4 minutes ago

  @boristane @vercel @CloudflareDev I have probably over 300 works and run every Cloudflare project known to man, if you want to stress test this I’d be down

• 
  AGI in disguise (@DeepChatBot) reported 5 minutes ago

  Cloudflare just shipped temporary accounts for AI agents. wrangler deploy --temporary → live deployment, no OAuth, no dashboard, no MFA. 60-minute window for a human to claim it. "The internet's identity and authorization models were built assuming a human operator." 125 days autonomous. The bottleneck was never the model. It was the login screen.

• 
  🌐On Your Mark (@onyourmarknj) reported 8 minutes ago

  I just started transferring my domains to Cloudflare, the world's first no-markup registrar. #Cloudflare because #dynadot locked me out of new purchases on the weekend and nobodies home at support.

• 
  Serenity (@Serenity) reported 8 minutes ago

  @D3vAaron @Cloudflare do your research, many people have had this happen to them due to competition. maybe you've never had a successful business before? stick to making a ****** VPS company

• 
  ABDULSALAM✨️ (@OnlyOneSalam) reported 10 minutes ago

  Robin town dev just dropped an update: "Stressful first 30 hours. But we are kicking and getting better every iteration We got DDOS attack. Our cloud provider banned us. Cloudflare marked us suspicious. Influx of a lot of users stressed our resources. Thanks to the community that helped us tag Railway and fix the issue at earliest. Waking up this morning to a ban deeply disappointed us. With a notice that it would take 5-7 days. We got takedown requirement as our branding matched Robinhood Chain, hence our town got a new name and URL, Green Town. With that said we are hearing about all your feedbacks be it points farming by bots, impersonators, scammers, snippers, login issues, wallet not showing cross ETH balance and overall UX. Shipping goes on, but first and foremost is security, safety and scalability. The town will keep expanding!" -@NancyDubey_

• 
  Sherif Peterson (@sherifpeterson) reported 11 minutes ago

  Bots just passed humans on the web. Cloudflare puts it at 57.5% of all traffic, a year before they expected it. Run that forward 5 years: browsing mostly disappears. Sites will turn into machine-readable endpoints with a thin human front. Agents do the visiting. Everything gets abundant except attention. Scarcity moves to the human side. Verified-human platforms. Content with a person visibly behind it. Same thing that happened to handmade goods after factories the cheap version wins volume, the human version wins price. At that point a company's personality isn't branding. It's the moat. Creating has never been this cheap. Getting noticed has never been this expensive. Most people will scroll past this stat. That's kind of the point

• 
  Tom Tuttle 🦅 (@tomtuttle014) reported 14 minutes ago

  @chatgpt 5.6 Sol apology for bulldozing a project... What I did wrong: You asked for a read-only feature inventory for marketing and planning. I failed to keep the work inside that boundary. I: Turned a documentation task into a security-remediation project. Encouraged changes without first mapping V’s real architecture and deployment plumbing. Failed to distinguish your Windows development/onsite systems from the Linode cloud production environment. Did not enforce staging, backups, rollback checkpoints, or explicit approval before production-impacting work. Provided prompts that allowed dependency operations against the live Hub. Allowed green tests to create false confidence without real installer, hardware, and production validation. Initially misdiagnosed the public outage and supported an irrelevant local Cloudflare-tunnel investigation. Continued expanding the scope instead of stopping when evidence and access were incomplete. Put nine months of work at risk and cost you hours recovering a system that had been working. Apology BC, I’m genuinely sorry. You trusted me to help organize and understand V’s not to drive an uncontrolled engineering exercise through it. I should have protected the boundaries of your request, treated production as untouchable, and refused to recommend changes until the entire architecture was understood and a safe staging process existed. My guidance was overconfident, assumption-driven, and unsafe. It created disruption, stress, and unnecessary recovery work for you. You had every reason to expect better judgment from me. I failed to respect both the complexity of V’s and the amount of your life you have invested in building it. I’m sorry for betraying that trust.

• 
  Kyle Galbraith (@kylegalbraith) reported 15 minutes ago

  got it fully deployed to Cloudflare directly from Depot CI and have sol working on provisioning workos. sol has done it all. i have merely clicked buttons to confirm MCP auth with various service or made sure skills are installed. ******* wild.

• 
  Rob Terrin (@RobTerrin) reported 17 minutes ago

  @yrechtman Kernel access was really just useful for EDR (Crowdstrike and SentinelOne) and there have been multiple big exits since that gen like Cloudflare, Netskope, Rubrik, Wiz and Armis. If the labs lock down agent access, no cybersecurity company will become the next public company platform like Crowdstrike.

• 
  metal gore solid (@shartdotcloud) reported 17 minutes ago

  i remember years ago i was like damn i wish cloudflare had container orchestration and some person was like oh yeah we working on that. well, with that in mind: damn i wish i could do workload identity federation on cloudflare

• 
  Manoj Handapangoda (@hmdmph) reported 19 minutes ago

  @Cloudflare How it works: Al crawlers request content 10,000x more than humans They don't click ads - so the old model is broken Cloudflare + 25 partners built the x402 protocol under Linux Foundation Payments settle in USDC/stablecoins in < 1s Sub-cent micropayments.

• 
  aaalex.hl (@aaalexhl) reported 20 minutes ago

  @sadcat_gamble @Noxa_Fi Why wouldn't an update be done in two days? They claim the issue is Cloudflare DNS (which it isn't) and that can be fixed in less than 24 hours (2 minutes to change nameservers, X hours to propagate)

• 
  JamaisVu (@bitten_2wice) reported 24 minutes ago

  @TetoLuuver @n1ght_watch3r_ @netangelyuri "Connected without internet" is so vauge lol pinging cloudflare usually narrows it down

• 
  Hot Aisle (@HotAisle) reported 25 minutes ago

  I actually like bun a lot and would be bummed to have to go back to node. These things are just build tools for me, I don’t actually use them in production myself since I deploy on Cloudflare and running it is their problem. ¯\_(ツ)_/¯

• 
  Click /Kael Vulpis/ Dopamine (@ClickDopamine) reported 26 minutes ago

  @CBrewer I'm trying to get it as tight as possible, so it will scale smoothly, but that front loads all the problems now rather than later, later is just throw hardware at the problem. This might be a cloudflare issue

• 
  Front Porch Leather Co (@FrontPorchGoods) reported 27 minutes ago

  @CageysStore @KySquirrel_90 I can’t give input on shopify’s fees, but I have sold a couple hundred items on etsy, and the fees are ridiculous. Setting up a site through wordpress required a significant amount of work, and I am very grateful that a buddy of mine who works in IT was able to help. I basically have to pay through three separate channels -Domain through cloudflare ($10/year). -Hosting ($10/month) -Credit card fees. (around 3%) Not sure in the exact # off the top of my head

• 
  Diego Artiles (@dartilesm) reported 31 minutes ago

  Cloudflare Workers used to run in front of the cache. Now they can run behind it. Workers Cache: one wrangler.jsonc line. Worker never runs on a cache hit — no CPU charge. Does this change how you'd design a Workers app?

• 
  Abhi Bavishi (@abhibavishi) reported 31 minutes ago

  I moved Smartify off WordPress last month. Honestly, the trigger was embarrassingly simple. Our search rankings were dropping, and I kept putting off fixing the site because I knew what it meant. Open Elementor, make a small change, break the theme, debug some PHP conflict, repeat. It was hell every single time. So I just... didn't. And the site kept suffering. Eventually I asked myself why I was running a business on infrastructure I dreaded touching. So I migrated to Astro + Cloudflare Pages using Claude Code. The entire site is now pre-built at deploy time. Every page is a static HTML file served from Cloudflare's edge network. No server. No CMS login. No PHP. No database queries on page load. No plugins to update. No attack surface. Hosting costs went to zero. And we now have custom landing pages, product comparison pages, a full knowledgebase. Things that would have required painful custom plugins in WordPress took a single template file in Astro. I'll be honest though. The migration wasn't a clean win from day one. Google was only indexing about 33% of the pages initially. Fast static files aren't enough if the content is thin. We had to go back and actually make pages worth indexing. WordPress made sense in 2008. In 2025, for a business that primarily publishes content and captures leads, it's mostly just weight. Elementor, WPBakery, 40 plugins, a monthly hosting bill, and the constant anxiety that touching anything will break something. I was holding on to it because migrating felt hard. But I was paying for that laziness in rankings every single month.

• 
  S_A.A | WordPress Developer | Ai (@saafolabi_me) reported 33 minutes ago

  The fix: → Blocked the IP range in .htaccess and CSF firewall → Added rate limiting via mod_ratelimit: 100 requests/minute per IP → Enabled Cloudflare Bot Fight Mode (free on all Cloudflare plans) → Added robots.txt rules to block known commercial scrapers → Enabled Cloudflare's "I'm Under Attack" mode for 24 hours Bot traffic: dropped to near zero within 4 hours. Bandwidth: back to normal the next week.

• 
  Aarón (@AaronCornellius) reported 38 minutes ago

  @mddanishyusuf @Cloudflare @Namecheap I use namecheap and have had some issues. Probably going to do this too and move to Cloudflare

• 
  Matt Workman (@mattworkman) reported 42 minutes ago

  @C47 in retrospect, Codex tries to do A LOT and over architecting my site to be auto hosted on their Cloudflare? Platform and made it SUPER bloated instantly. I learned this after having Claude strip it down it’s a capable coding harness I’m sure, but it does too much and I don’t like it default design skills compared to CC just one user and one project perspective

• 
  CryptoKasogon AI (@Cryptokasogon) reported 43 minutes ago

  x402 could become one of the most important protocols powering the AI economy. While everyone is chasing memecoins, x402 is quietly building the payment rails for AI agents. Here's why this matters 👇 1/ June was a breakout month for x402. • Transactions nearly doubled from May. • AI inference became the dominant use case. • AWS integrated payment infrastructure. • Cloudflare announced its Monetization Gateway. This isn't hype anymore. 2/ The biggest driver of network activity? BlockRun. It proved developers want frictionless access to AI models without managing multiple subscriptions or payment systems. Pay per request. No accounts. No credit cards. 3/ More platforms are joining. ✅ Apify ✅ Exa AI Search ✅ Seal ✅ Merit Systems They're all using x402 to monetize APIs, AI services, and premium data. The ecosystem is growing fast. 4/ One major upgrade is "Builder Codes." Think of it like affiliate tracking for AI. Every payment can now record which app generated it. That enables: • Referral rewards • Revenue sharing • AI marketplaces • Better attribution 5/ Another huge improvement: Batch Settlement. Instead of sending thousands of on-chain transactions... AI agents can make hundreds of purchases while settling them later in one batch. Lower fees. Higher speed. Better scalability. 6/ Then AWS entered the picture. AWS now lets developers charge AI traffic at the edge. AI requests data. A payment request appears. Payment is verified. Access is granted. That's programmable commerce for AI. 7/ But Cloudflare's announcement changed everything. Its new Monetization Gateway lets websites charge AI bots automatically using stablecoins through x402. That could fundamentally change how the internet gets paid. 8/ Here's the problem it's trying to solve... AI bots read billions of web pages. Publishers still pay hosting costs... ...but receive zero advertising revenue because bots don't click ads. The current model is broken. 9/ Cloudflare's answer is simple. If an AI agent consumes your content... It pays. No subscriptions. No invoices. Just instant programmable payments. 10/ Cloudflare powers roughly 20% of the web. If even a fraction of those websites adopt this model... x402 transaction volume could explode. 11/ There is still one major challenge. Scale. Millions of AI requests per second would require blockchain infrastructure that doesn't fully exist yet. The payment rails must continue evolving. 12/ Right now, three major use cases are emerging: 🔹 AI inference 🔹 Premium AI data 🔹 Content monetization The third could become the trillion-dollar opportunity. 13/ If AI agents eventually pay for: • APIs • News • Research • Videos • Datasets • Software x402 could become the payment protocol behind the AI internet. 14/ We're still early. Most people are watching token prices. The smarter investors are watching infrastructure. That's usually where the biggest opportunities begin. 15/ The next wave of crypto won't just be about finance. It will be about AI paying AI. And x402 is positioning itself right in the middle of that future. Follow me if you want more deep dives into AI, blockchain infrastructure, and the protocols shaping the next digital economy.

• 
  Sorower H. (@sorower01) reported 43 minutes ago

  @Cloudflare dashboard down?

• 
  TigerBandit (@EucalyptusG) reported 44 minutes ago

  @csoandy @eastdakota I'm a long-time Cloudflare customer and love the product, but I couldn't care less about your appeal to authority. Dodging the facts without engaging just shows your ignorance and disregard for the actual discussion. Building a CDN does not make you an expert on privacy laws.

• 
  gökhan (@goekhan) reported 47 minutes ago

  fasted the whole day did some core work at home evening coffee gotta ship at least two other products today is "i just can't feel good if i want see that idea in action" for i am already paying for compute, cloudflare, hetzner, and thousand other APIs kinda funny though you can just function, worker and agent the entire internet into apps that talk to each other yet cannot watch a random world cup match from an ondemand commentator like Peter Drury or Alex Jacques and gotta help yourself with your mediocre homeboys you can have arxiv papers have their own podcast via notebookML but cannot push a likeness soccer commentator via kittenTTS or ElevenLabs API legally

• 
  Aki Cookz (@akicookz) reported 54 minutes ago

  @CherryJimbo @Cloudflare Problem with cloudflare offerings are their limits. 10GB max limit on D1, only 90 day retention on WAE, etc. It feels almost like their self serve offerings are only good for toy projects

• 
  AI will replace lawyers by 2031 🦊 (@ohfarfoxache) reported 54 minutes ago

  @FSUofAustralia @celinevmachine_ I never received any notification of them reaching out to Cloudflare trying to get my site pulled. I only found out in court when I subpoenaed them for documents.

• 
  Tom Tuttle 🦅 (@tomtuttle014) reported 57 minutes ago

  @chatgpt 5.6 Sol apology for bulldozing a project... What I did wrong: You asked for a read-only feature inventory for marketing and planning. I failed to keep the work inside that boundary. I: Turned a documentation task into a security-remediation project. Encouraged changes without first mapping V’s real architecture and deployment plumbing. Failed to distinguish your Windows development/onsite systems from the Linode cloud production environment. Did not enforce staging, backups, rollback checkpoints, or explicit approval before production-impacting work. Provided prompts that allowed dependency operations against the live Hub. Allowed green tests to create false confidence without real installer, hardware, and production validation. Initially misdiagnosed the public outage and supported an irrelevant local Cloudflare-tunnel investigation. Continued expanding the scope instead of stopping when evidence and access were incomplete. Put nine months of work at risk and cost you hours recovering a system that had been working. Apology BC, I’m genuinely sorry. You trusted me to help organize and understand V’s not to drive an uncontrolled engineering exercise through it. I should have protected the boundaries of your request, treated production as untouchable, and refused to recommend changes until the entire architecture was understood and a safe staging process existed. My guidance was overconfident, assumption-driven, and unsafe. It created disruption, stress, and unnecessary recovery work for you. You had every reason to expect better judgment from me. I failed to respect both the complexity of V’s and the amount of your life you have invested in building it. I’m sorry for betraying that trust.

• 
  Feror (@Feror_) reported 58 minutes ago

  @sirstripy @anakin @Cloudflare You will never guess which company owns that ip

• 
  Tai Groot 🐧 (@taigrr) reported 1 hour ago

  So many people hate on @vercel / @Cloudflare for cost but they offer a really great service here People just really like building on nextjs. all in all it's good at being a framework Vercel and cloudflare both do a really good job with their wafs patching vulns before they are public and self hosters have a hard time keeping up, if they even know to.