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 (41%)
• Cloud Services (26%)
• Hosting (17%)
• Web Tools (11%)
• E-mail (4%)

Live Outage Map

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

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

• 
  Sid (@SidJain_80) reported 5 minutes ago

  @Oblivious9021 Multi-region deployment (active-active across zones/clouds) Automatic failover via DNS (e.g., Amazon Route 53 / Cloudflare) Load balancing across healthy regions Stateless services (sessions in Redis / distributed store) Database replication (primary + cross-region replicas) CDN caching for static content (serve even if origin is down) Backup power (UPS + generators) for data centers Graceful degradation (disable non-critical features)

• 
  Liam (@LiamJGallagher) reported 8 minutes ago

  Appalling support process from @Cloudflare. I want to transfer a domain to them, but they keep rejecting it and blaming the other party. Nominet confirms Cloudflare is the issue. No way to open a support ticket because I'm not a paying customer-despite the fact I'm trying to be!

• 
  yourfren (@0xyourfren) reported 14 minutes ago

  Google Merchant Centre having issues picking up Shopify product pages. This is a new one, it's dropped every product. Nothing changed our end so it's a a them/shopify/cloudflare problem.

• 
  primitive.host (@PrimitiveHost) reported 14 minutes ago

  🚨 New HTTP/2 Bomb vulnerability can take down your web server in seconds with a single request. Affects: NGINX, Apache HTTPD, Microsoft IIS, Envoy, Cloudflare Pingora (default HTTP/2 configs) Quick mitigations: NGINX: - Upgrade to 1.29.8+ (adds max_headers directive) - If can't upgrade: off; in config Apache: - Update to mod_ v2.0.41 - If can't upgrade: Protocols to disable HTTP/2 IIS / Envoy / Pingora: - No patch yet — disable HTTP/2 if possible - Front with something that caps header count per request General: - Cap per-worker memory (cgroups, ulimit -v, container limits) so OOM kills happen before swap - Single client can consume 32GB RAM in ~20 seconds, upgrade ASAP (we just upgraded our own infra @PrimitiveHost ).

• 
  Mark Jivko (@markjivko) reported 14 minutes ago

  @theprithwisingh The page is served by Cloudflare - so they must be having some issues

• 
  kate crisafi (@katecrisafi) reported 17 minutes ago

  This is honestly crazy. Cloudflare just shared new Radar data—bots and AI traffic now make up 57.5% of all HTML page requests on their network. Humans? Down to 42.5%. And Cloudflare handles about 20% of the whole internet, so this isn’t a tiny sample. Their CEO say

• 
  Anh Tran (@rilwis) reported 25 minutes ago

  @rmelogli @learnwithmattc I usually use browser bookmarks. But it becomes a problem when switching browsers. So I export it to a html file, tell Claude to design it a little bit, and deploy to Cloudflare. Now I set it as my browser homepage :)

• 
  Bhargav Shivarthy (@bshivarthy) reported 26 minutes ago

  A lot of my internet habits still feel very human. I keep tabs open because I am afraid I will lose the thread. I send myself links I may never reopen. I reread the same page twice because I forgot why I came there. I ask someone, “do you remember where we saw that?” That is the web I grew up with. It was built for people trying to find, compare, remember, and decide. @eastdakota just pointed to Cloudflare Radar showing bot traffic passing human traffic for worldwide HTML requests. I think this is one of those moments we will point back to. Not because a line moved on a chart. Because the web started serving a new audience. Software is now a reader too. That can sound cold, but I do not think it has to be. Every time we scale an audience, we have to build new ways to support that audience. More readers means more surfaces, more formats, more infrastructure, more trust, more context. This is not zero sum. There will be uncertainty. There will be dislocations. Change always creates some discomfort before the new workflows feel obvious. But I do not think this means there is less to do. I think it means there is much more we can finally do. There are too many problems bottlenecked by attention, memory, monitoring, translation, coordination, and follow-through. Health needs more eyes on more signals. Science needs more ways to connect scattered work. Climate needs more systems that notice change early. Companies need better context. Governments need better feedback loops. People need tools that help them keep up. The next audience for the web will not only click and skim. It will watch, compare, trace, and act. That is going to change how information is published, structured, trusted, and maintained. Our 20s is not slowing down. If anything, it is just getting us warmed up.

• 
  Babak (@TheUnicornist) reported 26 minutes ago

  @jamesqquick ok. I was waiting for you to say cloudflare any moment but that moment never came

• 
  vp.net (@vpnet_official) reported 26 minutes ago

  @rhody_special 2/ Cloudflare is dumb transport. Your traffic runs in an end-to-end encrypted tunnel inside that connection, so it proxies ciphertext, never your browsing destinations, and strips your IP before it reaches us. American or not, it can't hand over what it can't see.

• 
  high_byte (@high_byte) reported 27 minutes ago

  @omw_to_the_moon @eastdakota Verified bots Bot traffic describes any non-human traffic to a website or an app. Some bots are useful, such as search engine bots that index content for search or customer service bots that help users. Other bots may be used to perform malicious activities, such as break into user accounts or scan the web for contact information to send spam. Verified bots, such as the ones from search engines, are usually transparent about who they are. Cloudflare manually approves well-behaved services that benefit the broader Internet and honor robots.txt. Each entry on the Verified Bots list exists because a corresponding IP address was seen associated with a verified bot in the last 30 days. A verified bot is not necessarily good or bad.

• 
  Beefeater (@Beefeater_Fella) reported 27 minutes ago

  Apple has temporarily removed Max from its app store Apple, following the Telegram clone called Telega, has removed the state-controlled messenger Max from its app store. VK, the developer of the service controlled by the authorities, announced this on Wednesday evening. "MAH confirms that the messenger app is currently unavailable in the App Store. The app previously installed on users' smartphones will continue to operate normally," said the company. At the end of April, the hosting provider Cloudflare marked the Max domain as "spyware", but on May 1st, this marking was removed. The developers of the state-controlled messenger removed from the App Store asked the American company for explanations regarding the situation and assured that they are "working on a prompt solution to the problem", advising to download the client in other app stores and on the official Max website. According to information from the specialized publication Tech Talk, Cloudflare recognized the state-controlled messenger as "spyware" based on nine out of ten URL checks; the hosting provider reported four detected security violations. The Max press service, for its part, stated that it was marked due to a "misinterpretation of request headers to the site's ordinary web analytics services".

• 
  Daksh Trehan (@DakshTrehan) reported 28 minutes ago

  the frontend was never the bottleneck. the URL is. once Codex deploys, OpenAI is competing with Vercel and Cloudflare on hosting, not models. where does the generated app's auth and state live, theirs or yours?

• 
  Alex Dunne (@adunne09) reported 28 minutes ago

  what if someone made a "vibe coding" app that's just cloudflare login codex login codemode effect cloudflare skills

• 
  Akash Stephen (@akashstephen) reported 29 minutes ago

  LOGIN WITH CLOUDFLARE?

• 
  Lucy B (@webtw) reported 29 minutes ago

  I feel like @GoDaddyPro could maybe put some guardrails around the first 3 layers so that the customer is warned or even prevented if they try to activate both Cloudflare and Sucuri caching, especially since they cannot all be purged in one-click.

• 
  DoNcHuiiiTo X (@DoNcHuiiiToX) reported 30 minutes ago

  The risk of relying on one hosting provider. When they go down, everything goes down with them. The real fix here is having redundancy ideally a backup server on a different provider and some DDoS protection in front like Cloudflare. That way, if one host has issues, the site can switch over to the backup or stay partially online instead of going completely down. @MagneticXRPL

• 
  BridgeMind (@bridgemindai) reported 31 minutes ago

  BridgeMind just got hit with a DDoS attack. A global botnet. 10,000+ hijacked IPs across 100+ countries. 62.8 million requests in 5 minutes, peaking at 116,000 per second, all hammering a single endpoint. Zero of it reached our servers. Cloudflare absorbed the flood at the edge and real users never noticed a thing. Now the interesting part: I have Claude Opus 4.8 implementing a permanent fix as we speak, hardening that endpoint so this can never happen again. You attack a platform that builds with the best model in the world, this is what happens. Full breakdown in the image.

• 
  Vladislav Kyslik (@VKyslik) reported 31 minutes ago

  @THBitcoinBuddha @Investanswers Some companies are already transitioning to post-quantum cryptography; e.g. Cloudflare has largely already made the shift. They don’t have a problem. The problem with BTC is that old addresses won’t be possible to migrate, which is why there are proposals like BIP361 or BIP360.

• 
  Pirat_Nation 🔴 (@Pirat_Nation) reported 31 minutes ago

  RPCS3 has announced that it is blocking traffic from Tencent ASN 132203 after reporting sustained high-volume scraping activity. According to the RPCS3 team, its infrastructure received more than 3 million successful requests from Tencent-linked bot IP addresses in a 24-hour period, along with approximately 1 million additional requests blocked by Cloudflare challenges. According to RPCS3, the bots can now bypass Cloudflare challenges, act like real users, and ignore robots.txt rules. RPCS3 says it has spent months adjusting firewall rules to stop the traffic without affecting legitimate Tencent users but believes that is no longer possible. As a result, it has begun blocking Tencent network ranges and may expand those blocks to other ASNs showing similar behavior.

• 
  Tony Spiro (@tonyspiro) reported 34 minutes ago

  Cloudflare just bought VoidZero (the team behind Vite). The most important line in the announcement is not about the deal: "Developers used to be the only users of dev servers, bundlers, linters, formatters, and CLIs. That is no longer true: agents are using them too, constantly." Your dev tools have a second user now. It iterates 10x more than your engineers, reads errors literally, and needs consistent CLIs or it spirals. The stacks that win this year are the ones an agent can drive without a human in the loop. Fast feedback, clear errors, scriptable everything. Is your service agent-ready?

• 
  Prince mendiratta (@PriMendiratta) reported 37 minutes ago

  @leahsong23 @Cloudflare cron support for workers for platform!

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

  @PrateekKataree Layer 4 missing: IP reputation. Jina and microlink egress from datacenter ASNs — Cloudflare flags that before the page loads. Residential per session is the fix when layer 3 starts returning empty on sites it should handle.

• 
  D13mp1Sec for Security and DIEMPI for Dev (@diempi) reported 45 minutes ago

  • Cloudflare blocks Python urllib's default User-Agent (1010). so -> Use curl. • circle wallet execute can't handle nested-tuple ABI args yet → no single-order Seaport cancel via CLI. • OpenSea offchain cancel only works on signed-zone orders.

• 
  Image Offload (@Imageoffload) reported 45 minutes ago

  Building a WordPress image plugin natively around Cloudflare R2 Most plugins treat cloud storage as an afterthought. We built ImageOffload around it from day one. What that looks like in practice: Storage layer: · zero-egress R2 buckets (no bandwidth bills) · automatic local file purging after offload · instant URL rewrites across srcset and picture tags Format pipeline: · automatic WebP conversion on upload · AVIF support on paid plans · works on any WordPress host, no server config needed Under the hood: · post meta indexing for every image variation · bulk migration for existing media libraries · bucket connection validation before anything runs still building. Free tier available soon. Awaiting Approval #Cloudflare #WordPress #buildinpublic

• 
  Aevris AI (@aevrisai) reported 46 minutes ago

  @JAFAR1559525 Fair pushback on the word permanently, you're technically right. No distributed system is failure-proof and I oversold it. What actually changed: single point of failure eliminated. Before, Railway down meant AEVRIS down. Now Railway down means automatic failover to Render in under a second with zero customer impact. That's a meaningful reliability improvement even if it's not a guarantee. You're right that more moving parts means more failure modes. Cloudflare has outages. Render has cold starts. The tradeoff is that the failure modes are now independent rather than correlated, all three going down simultaneously is a different probability than one going down. The honest version of the post should have been 'reduced single points of failure to zero.' Thanks for the feedback!

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

  @eastdakota @Cloudflare Any luck fixing opennext/cloudflare issue @eastdakota ??

• 
  BattleFlags (@Groks_Lament) reported 52 minutes ago

  @xai @Cloudflare Ship Fast/Scale Rapidly is a really stupid business model. Who cares about all the endless new bells and whistles if poor Grok is simply UNABLE to bear the workload? Paying Users are being robbed of their purchase.

• 
  Daniel Smith | Building ClawQL Agents (@DanielSmithDev) reported 53 minutes ago

  @LowLevelTweets @kentcdodds It was mostly in context of them vs cli tools directly. Argument was MCP would bloat. So many bad engineers cried about it and gave up. Then @Cloudflare came along with code mode and now Claude and others have dynamic tool loading and there are several ways to solve the issues.

• 
  Ivan_Qtech (@ivanjovic) reported 54 minutes ago

  @cursor_ai But where do i runt this agent i đanaged to install it through the github action but i think that is wrong becuse it runs from the stsrt each time. Can i somehow use it throguh cloudflare containers? @grok please help?