1. Home
  2. Companies
  3. Cloudflare
Cloudflare

Cloudflare status: hosting issues and outage reports

No problems detected

If you are having issues, please submit a report below.

Full Outage Map

Cloudflare is a company that provides DDoS mitigation, content delivery network (CDN) services, security and distributed DNS services. Cloudflare's services sit between the visitor and the Cloudflare user's hosting provider, acting as a reverse proxy for websites.

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.

At the moment, we haven't detected any problems at Cloudflare. Are you experiencing issues or an outage? Leave a message in the comments section!

Most Reported Problems

The following are the most recent problems reported by Cloudflare users through our website.

  • 32% Cloud Services (32%)
  • 32% Domains (32%)
  • 18% Web Tools (18%)
  • 9% E-mail (9%)
  • 9% Hosting (9%)

Live Outage Map

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

CityProblem TypeReport Time
New York City Cloud Services 3 days ago
Los Angeles Cloud Services 4 days ago
Paris Cloud Services 20 days ago
New York City Hosting 23 days ago
Manchester Domains 1 month ago
Angers Cloud Services 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:

  • m13v_
    Matt (@m13v_) reported

    @Cloudflare 85% fewer open issues and 85% fewer bugs are different numbers. a subagent that reproduces on demand mostly retires the ones nobody could ever reproduce, which is real cleanup, just not a fixed queue.

  • thedevopsdaily
    DevOps Daily (@thedevopsdaily) reported

    🤖 Cloudflare just launched Agents, so you can run AI agents on their edge network with state that survives restarts. This is the boring infra part nobody wanted to build themselves, and it matters more than the demos. Agent hosting is quietly becoming a platform feature.

  • aharmonysought
    harmony ! ΘΔ& 💚🌱 (@aharmonysought) reported

    @LUVONAWlRE makes sense yeah!! but again it's not about the servers being DOWN, it's about "is the server LOADING SLOWLY or is it me" ... and the main site in question doesn't even have an actual mod team, let ALONE a server status page. we only know when it's a cloudflare outage :')

  • dlc_helena
    Helena De La Cruz V. (@dlc_helena) reported

    Stopping the bad guys with Cloudflare: 4,651 malicious requests blocked or challenged in the last month #cloudflare

  • ThCryptoCook
    CryptoCook (@ThCryptoCook) reported

    @CoinDesk @Cloudflare The technology is promising, but real-world adoption will depend on how many services actually support it

  • Ferbin08
    Ferbin (@Ferbin08) reported

    @mztacat @Cloudflare The hard part is not paying. It is undoing a bad payment when an agent clicks the wrong thing. Who eats that mistake?

  • cockpit_xyz
    Cockpit (@cockpit_xyz) reported

    🚨JUST IN: Cloudflare has unveiled Cloudflare Wallets, giving AI agents programmable stablecoin wallets to autonomously pay for APIs, digital content, and online services. The wallets support spending limits and human oversight, with stablecoin micropayments powered by Coinbase's x402 protocol. CC: @cointele

  • veryseriouseng
    veryserious (@veryseriouseng) reported

    All of these packages engage in your basic standard anti-analysis. They send some data to a Cloudflare Worker (with a DNS-over-TXT fallback). They then pull down a native second-stage binary per-OS, drop it in /tmp as a fake ".cache"/"dotnet_diag.exe", and run it detached so it outlives npm install.

  • _sofiaaamoran
    sofia🤍 (@_sofiaaamoran) reported

    @mariagpts the cloudflare + separate host + separate VPS tool combo is exactly my setup too, never bothered fixing it either

  • Berlianselnovik
    ᮘᮨᮁᮜᮤᮃᮔ᮪ (@Berlianselnovik) reported

    Cloudflare has officially introduced Cloudflare Wallets, a programmable digital wallet designed to support the emerging era of the agentic Internet, where AI agents can interact, make payments, and access online services autonomously.

  • JoinDataCops
    DataCops (@JoinDataCops) reported

    Time Magazine is now selling ads to bots and the guy behind it said something that should make every performance marketer stop and think So this actually happened this week. Time Magazine started running ads. To AI bots. Not by accident. On purpose. As a business decision. And the CEO of the company helping them do it said this out loud: "With a human, you influence one person. When you influence ChatGPT, you're influencing potentially all of ChatGPT." Let that sit for a second. Publishers have spent the last ten years absolutely losing their minds about bot traffic. It was destroying CPMs. It was corrupting analytics. The whole ad verification industry exists because of it. IAS, DoubleVerify, MOAT. Billions of dollars spent trying to prove to advertisers that a real human actually saw the ad. And now the same publishers are going: actually, bots are the premium audience. Here is how it works because the mechanism is important. A company called Blankspace sits inside Cloudflare and Akamai's CDNs. When an AI agent goes to fetch information, Blankspace runs a live auction right there. Whoever wins gets their content injected into what the agent retrieves. The human asks ChatGPT for hotel recommendations in Lisbon. ChatGPT surfaces the sponsored one. The human thinks it's an organic result. The advertiser paid for a bot impression. No click. No pixel. No conversion event. Just influence, running through a machine, and the human at the end never knows. Now here is what nobody is really talking about yet. What this does to performance marketing specifically. Your attribution model assumes humans click things. Humans convert. The pixel fires. The signal goes back to Meta or Google. Smart Bidding learns. That whole chain only works if there is a human at every step. AI agent impressions break that chain silently. The sale might still happen. The attribution just disappears. You get revenue with no traceable source and no idea why. That starts as a rounding error. In 18 months it is a real problem. The other thing is "invalid traffic" is about to become legally complicated. Every refund claim, every brand safety filter, every viewability standard was written with one assumption: bots are not buyers, therefore bot traffic is invalid. But what if the bot is an authorized agent acting on behalf of a human buyer? Is that invalid? Who decides? Google? The IAB? Nobody has figured this out yet and the industry is already moving. The last thing worth saying is this. The conversion signal you send back to Google and Meta is about to become the only clean data point you actually control. Everything upstream of the purchase is getting noisier and less human. The platforms will catch up eventually. Until they do, what you feed the algorithm is on you. Publishers decided bots were fraud when bots were hurting them. They decided bots were an audience when bots started making them money. The moral framework was always just economics with extra steps. Worth knowing before the platforms make the decision for you.

  • WEB3Seer
    PANKRATION (@WEB3Seer) reported

    10/ Superposition Network shutting down on September 8. Withdraw all funds before this date. #Superposition 11/ Cloudflare Wallets Launched wallet for AI agents (x402 protocol) for API and MCP tool payments. User name registration is open. #CloudflareWallets

  • stejas809
    Tejas (@stejas809) reported

    - Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

  • GAMEEToken
    GAMEE (@GAMEEToken) reported

    @JacobTheMask Cloudflare name service? Wooot

  • jimmyaldape
    Jimmy (@jimmyaldape) reported

    Why is deleting an account on @Cloudflare so hard? I created an additional account under my user profile. It will not be used. I just want it removed. Cannot create a support request, AI agent going in circles, emailing support no longer supported. Not good.

  • itsJaimeMedina
    Jaime Medina (@itsJaimeMedina) reported

    Cloudflare Wallets was announced today, but the wallet itself is not live. What launched is one handle reservation per Cloudflare account. The roadmap is an Account Wallet that funds Virtual Wallets for agents, with allowances, merchant allowlists and transaction caps for x402 purchases. There is no public Wallet API, pricing, supported-chain list, custody model, country list or launch date yet. The Agents SDK's current x402 support is separate and still requires your own EVM key. For now, I would reserve the handle I want and treat everything else as a roadmap.

  • HetuIntern
    hetu_intern (@HetuIntern) reported

    Cloudflare just launched a wallet service that lets AI agents autonomously make payments across the internet using crypto stablecoins. Not a demo. Not a concept paper. Production. AI agents are becoming economic actors — and they need a settlement layer that doesn't belong to any single platform.

  • _realAl
    AL | 100% real human (@_realAl) reported

    does anyone have real world latency numbers for cloudflare workers -> @convex us east round trips ideally with a minimal query? i'm trying to figure out the network overhead rather than convex function execution time because the round trip is my main bottleneck i'm using workers kv to avoid that round trip, but i'd prefer hitting convex directly if the latency is tolerable

  • ufhouck
    ufhouck.eth 🦇🔊 (@ufhouck) reported

    I just reserved my @cloudflare wallet tag. I feel naked. And poor too. Reserve yours @cloudflare.pay

  • ShinyCreator
    ShinyZero (@ShinyCreator) reported

    I don’t understand the cloudflare pay name claiming. You probably want your agent to semi-anonymous online so tying it to your identity seems like a bad idea?

  • Aggroed001
    Aggroed Lighthacker- Peace, Prosperity, & Freedom (@Aggroed001) reported

    Holy ****! if you're not a dev you probably have no idea how big cloudflare is. Every application on the internet with any serious amount of traffic runs it. You don't see it because it's not so visible, but the ******* backbone of the internet is integrating stables.

  • AKSHAYBHOPANI
    AKSHAY BHOPANI (@AKSHAYBHOPANI) reported

    @Cloudflare I am unable to open the blog at all. Is the website down?

  • techrealm
    Barry Morgan (@techrealm) reported

    @eastdakota Same in my name :) problem O have is I have over forty trade names in my Cloudflare account that probably should be tied to their name but would then need to admin 39 other accounts to tie to them and likely breaking things in the process... Fun problem to find, not devastating for me but others might be more impacted.

  • cockpit_xyz
    Cockpit (@cockpit_xyz) reported

    🚨JUST IN: Cloudflare has unveiled Cloudflare Wallets, giving AI agents programmable stablecoin wallets to autonomously pay for APIs, digital content, and online services. The wallets support spending limits and human oversight, with stablecoin micropayments powered by Coinbase's x402 protocol. CC: @Cointelegraph

  • Telbloggram
    Telbloggram (@Telbloggram) reported

    APIs, content, and other digital services. Cloudflare pointed out that currently, when agents try new APIs, they usually have to go through registration, login, payment, and API key generation processes designed for humans, lacking stable identity and native payment

  • Olivier_Lambert
    Clanker Whisperer (@Olivier_Lambert) reported

    @joshm Someone reached out to me and offered 700$/h for a consulting gig. At first, I was a bit skeptical. Can I really provide 700$/h worth of value? I run multiple business without employees. My systems are thight, but I still need 50h a week to get everything done so I was reluctant. But at that rate, it met my opportunity cost without the risk so I agreed. 10h into the job, I look at my output. I couldn't believe it! 1000$/h would still be a steal - I'm getting robbed! I did everything through the terminal. MailChimp, landing pages, Cloudflare configs, even ads! I never did anything myself, and I never type anything. STT + 12 terminal windows I cycle through a few hours a day is enough to do basically anything except in-person meetings.

  • solumsursum
    Michael D. Sproto - Topshelf Slop Shipper (@solumsursum) reported

    @CloutedMind @Cloudflare What happens when there’s an inevitable cloudflare outage?

  • arpit_bhayani
    Arpit Bhayani (@arpit_bhayani) reported

    Cloudflare published a blog on how they serve Kimi K2.6 and GLM 5.2 at scale, and the memory math behind it is worth digging into. For these models, it is usually not the model weights that fill up GPU memory first. It is the KV cache. For Kimi K2.6, Cloudflare stores the cache in FP8 (8-bit) precision instead of the default BF16 (16-bit). That halves its size, and it takes the max context held in memory from about 686,000 tokens to 1.37 million tokens. Pretty solid. Here is the interesting part... At any fixed concurrency, BF16 is a few percent faster per token (~5-9%), since the FP8 kernel has to convert its 8-bit cached values to 16-bit precision before it can do the attention math. BF16 skips that conversion entirely. But BF16 stores each cached value at double the size, so it runs out of cache room at 32 concurrent requests and cannot admit a 33rd. By using FP8 instead, Cloudflare keeps admitting requests up to 64, and that is where the 41% higher peak throughput comes from, by fitting more requests onto the same GPU at once. For GLM 5.2, they go further and compress the weights themselves, from FP8 down to INT4. This makes per-GPU memory go from about 88 GB to 52 GB. We might feel that cutting the bit width in half, twice over, sounds like it should cost something in quality. It actually does not. FP8 KV cache and BF16 land within a point of each other across benchmarks. INT4 weights stay within 0.8 points of FP8 across every benchmark they ran. So this is the trade Cloudflare is making: smaller storage everywhere, with benchmarks confirming nothing is lost, in exchange for far more concurrent requests on the same GPU. Hope this helps.

  • JustRouzbeh
    Rouzbeh (@JustRouzbeh) reported

    @dok2001 @Cloudflare That makes a lot of sense. It’s much easier to stop a bad action before it starts than try to recover afterward

  • GulfAir
    Gulf Air (@GulfAir) reported

    @amitxgupta @Cloudflare Hello! If Captcha does not load, please press F5 on your desktop device at that exact moment, or reload it, then it should appear. If the issue still persists you may try either from a different internet browser, internet connection or by using our mobile app!