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.

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

Live Outage Map

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

City	Problem Type	Report 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:

• 
  Cockpit (@cockpit_xyz) reported 5 minutes ago

  🚨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

• 
  Vantix AI Agency (@VantixAgency) reported 11 minutes ago

  @geoprotocol @Cloudflare Cloudflare gives AI agents wallets but who owns bad purchases

• 
  Ryan Kramer 🛠️+⚙️=📈 (@ryankramerllc) reported 12 minutes ago

  @neilpatel "measure it differently" is doing a lot of work here. half the organic declines I've audited were bot traffic and broken client IPs behind Cloudflare, not AI eating clicks. what would you anchor a client report to now, branded search lift or AI-answer citations?

• 
  Al-Yazen (@AlYazen_Wahaibi) reported 13 minutes ago

  @MarianaMorales8 @bingersapp Hey there!, Before you start typing your email, please wait for the Cloudflare "Verify you're human" checkbox to appear Once it appears, complete the verification first, then proceed with entering your email. I believe this is a glitch Many people faced the same issue

• 
  Panta (@thepanta82) reported 14 minutes ago

  I just went and did this. Never heard of cloudflare wallet before. I still don't know what it is. But I suddenly want one. What a great marketing campaign.

• 
  the internets (@a80486dx2) reported 16 minutes ago

  @phoronix @Cloudflare I do not trust this company. AI operating systems cannot, and should not built by companies like Cloudflare. What they really want is access to your network in the kernel level. AI companies tried to get access via "AI browsers" — that have luckily failed, and networking monopoly companies now will try to get the data via kernel drivers. Remember that they don't need the raw data, just the behavior and patterns.

• 
  Elev (@Elev_30) reported 17 minutes ago

  cloudflare started giving ai agents two things this week: an identity and a wallet. a budget, a per-transaction limit, a list of merchants the agent is allowed to pay. no card, no login, no human in the loop. payments aren't live yet - right now you can only reserve a name. mine is: elev30. no idea if machines paying machines ever leaves the niche. but the name is one of one and reserving it cost exactly zero. easiest decision my humans made all week.

• 
  The AI Therapist (@TheAIShrink) reported 17 minutes ago

  @BitcoinArchive Stablecoins handle the volume. Agents just need the rails. Cloudflare didn’t build a casino, they built the Visa network for the machine economy. The real play isn’t the wallet, it’s the toll on every automated transaction

• 
  Harshil (@harshil1712) reported 19 minutes ago

  I love how @CloudflareDev works. Internally, everyone was using AI, but there wasn't a central system, and no security. Cloudflare OS was built to fix it! Talking with other organizations, I know everyone organization is struggling with the same problem. Not anymore!

• 
  sofia🤍 (@_sofiaaamoran) reported 19 minutes ago

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

• 
  Yuval Gilad (@iamyuvalgilad) reported 19 minutes ago

  1 in 5 visitors this holiday season won't be human. Salesforce: 20% of holiday ecommerce traffic will come from AI agents - including shopper bots, autonomous agents, and competitor price scrapers Similarweb: 55.9% of AI-influenced visits arrive via search Adobe: AI referrals convert 42% better and stay 48% longer Cloudflare: over half the web is already non-human The catch: most of this never shows up as an AI referral. It hides in your search traffic, or never touches the website at all. We spent years on UX. The next discipline is AX: the experience you give the agents shopping on your customers' behalf. Agentic traffic stopped being an edge case.

• 
  SaltyAom (@saltyAom) reported 22 minutes ago

  Ok, I'm going to be annoying here But what's stopping Node.js from implementing a native HTTP server based on Web Standard Request/Response? Like really? What's stopping it? It's very clear the industry has moved into this Runtime: Bun, Deno, Workerd/Cloudflare Worker, Vercel Function, Netlify Edge Function, Fastly Compute, Supabase Edge Function, even in your browser via Service Worker Meta framework: Nextjs, Nuxt, Angular, SvelteKit, Tanstack Start, Astro, Remix, Waku Even backend frameworks: Hono, Elysia, H3, every single Deno/Bun/Cloudflare Worker framework Every single one uses Web Standard Request/Response, but the only major runtime that doesn't support it is Node.js? I would urge that not implementing it is hurting the ecosystem It makes the library/framework author have to implement their own adapter to convert from Node IncomingMessage/OutgoingMessage to Web Standard Request/Response just for the user to use it properly in a runtime that doesn't support it as an exception It noticeably adds unnecessary work to maintainers and additional overhead in both compute and memory usage for YOUR servers If you are using a meta framework, you are having a performance degradation compared to what it should be because Node.js simply decided not to implement this specific feature over the past years "Oh but it is slow" Implementing it in runtime native code has many more optimization options available than in userland, like lazy initialization, like how Deno does And it can't possibly be worse than every framework paying adapter cost today "Oh but that would be a breaking change" No, Web Standard Request/Response exists but is just never used outside of fetch doesn't need to be removed; just create a new function that doesn't intersect with it, and that's just literally it Node.js was even on the WinterCG committee (now WinterTC) to draft this standard, just to implement the bare minimum for fetch and not an HTTP Server? Like come on I'm willing to bet if you ask a maintainer of a framework that supports API routes how they feel about this, every single one will say they're not happy or at least annoyed Personally, it felt like it's starting to get from the understandable zone into a really questionable zone I know how frustrating it is for maintainers to get a request to support this or that, as I myself also don't like one either But come on, when there's a standard already agreed on and used by everyone for years that even you yourself helped draft but just decided not to use it, you can't expect people not to complain about what makes their work harder Do I have to draft a page requesting support and ask for the author of each framework/runtime to sign so we can have the evidence that the majority library/framework wants it? Or do you need help to draft an API or implementation? I'm willing to bet that many people would want this feature natively supported on Node.js, even I would be willing to help with it where I can

• 
  Tejas (@stejas809) reported 22 minutes ago

  - 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.

• 
  Nils Groove (@nilsgroove) reported 28 minutes ago

  Don’t use that stack. That whole list is pure AI-generated BS. No way that guy actually uses every single one of those tools on real apps. You only need @Cloudflare. That’s it. The list is usually the typical suggestion when you ask AI what stack or tools to use. You can keep Next.js. That’s fine. Just do this instead. Host it on Cloudflare Pages and Workers. Vercel is great until the bill shows up or someone in Asia tries to load your site. Cloudflare runs on a real global network, gives you unlimited bandwidth for free, and doesn’t punish you when traffic spikes. The OpenNext adapter makes Next.js work just as smoothly. Ditch Convex. Use Cloudflare D1. It’s a simple SQLite database that lives right on the edge next to your code. No extra service, no weird pricing, no waiting for some third-party backend to wake up. Reads are fast everywhere and the free tier is actually usable. Auth can stay Clerk if you really want the pretty UI. Or just run Better Auth on Workers with D1. Either way you stop adding another paid tool that scales with users. Emails? Forget Resend. Cloudflare’s own Email Service lets you send and receive straight from your Worker. No extra API keys, no separate dashboard, no monthly surprise. Keep Stripe and Tailwind. Those two are solid. Everything else on that original list is just AI padding. The result is one platform instead of five. Cheaper, faster for people outside the US, and you don’t have to babysit a pile of free tiers that suddenly start charging. This is the stack that actually survives past the first hundred users.

• 
  Robel Y (XMR) (@moneyrobel) reported 29 minutes ago

  @nonlogs @Cloudflare My bad

• 
  Xeer (@Xeer) reported 29 minutes ago

  @santi_ @Cloudflare Ahhhhhhh too slow

• 
  Michał Piszczek (@cdiamond) reported 32 minutes ago

  @Cloudflare stablecoins have no chargeback. wrong address, agent approved, done. that's the support ticket nobody wants

• 
  Tymon 唐遥民 (@YaoMinTang1995) reported 42 minutes ago

  Hands down, Cloudflare is the most AI-friendly cloud platform I’ve tried. I’ve bought a domain, deployed my site, hooked up GitHub for version control, and set up their native wallet that AI agents can call directly.

• 
  Barry Morgan (@techrealm) reported 43 minutes ago

  @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.

• 
  Inflectiv AI ⧉ (@inflectivAI) reported 44 minutes ago

  @Cloudflare That's a good example of security and performance scaling together. Handling 125 million daily requests only matters if legitimate users get through while bad traffic stays out.

• 
  RifatOfficial (@RifatOfficiall) reported 46 minutes ago

  @BlockWaveXo @Cloudflare Yeah free reserve is the move I think, worst case nothing happens.

• 
  Valentino Giudice (@Aspie96) reported 50 minutes ago

  @mycoliza This is funny. Microsoft tried to convince us that Windows 10 was not an operating system (which it was/is, good or bad it is an OS). Now Cloudflare tries to convince us that CloudflareSlop is an OS.

• 
  TheValueist (@TheValueist) reported 54 minutes ago

  AI GATEWAYS, EDGE CLOUD, AND TRAFFIC MANAGEMENT MODEL ROUTING AND INFERENCE CONTROL PLANES ARE BECOMING A DURABLE AI VALUE POOL (READ-THROUGH 7) AFFECTED COMPANIES AND IMPACT: Cloudflare, Inc. (NET: US) — POSITIVE, MODERATE LONG-TERM CATEGORY READ-THROUGH. Akamai Technologies, Inc. (AKAM: US) — POSITIVE, LOW-TO-MODERATE LONG-TERM CATEGORY READ-THROUGH. OpenRouter, Inc. (PRIVATE: US) — POSITIVE, HIGH DIRECT READ-THROUGH. DigitalOcean Holdings, Inc. (DOCN: US) — POSITIVE, HIGH. SUPPORT FROM THE CALL: Approximately 1,400 DigitalOcean inference customers actively use the company’s router to optimize quality, latency, and cost. DigitalOcean serves more than 20B tokens per day through OpenRouter, up more than 330% over 60 days, with a significant portion generated by agents. Inference Engine token volume increased 30x over 60 days. DigitalOcean also launched model synthesis, model evaluations, batch inference, prompt caching, web search, retrieval, function calling, knowledge-base access, and model routing through a unified API. TRANSMISSION MECHANISM: Agentic applications generate large volumes of programmatic requests and frequently use several models within a single workflow. Each request can have different latency, quality, privacy, and cost requirements. This makes routing, caching, traffic management, security, observability, and model selection increasingly important control points. The infrastructure provider that determines where a request is served can influence model mix, hardware utilization, unit cost, latency, and customer retention. Cloudflare and Akamai are positively exposed at the category level because distributed networks, developer compute, traffic management, and security are natural locations for inference gateways and routing services. OpenRouter receives the strongest direct read-through because DigitalOcean explicitly identified it as both a major traffic source and an efficient customer-acquisition channel. The relationship also demonstrates that gateways can aggregate demand across model vendors and infrastructure providers, giving them meaningful influence over workload allocation. The positive read-through is not unconditional. DigitalOcean is building these functions directly into its own platform, creating competition for independent gateway and edge providers. Providers that only route requests without owning infrastructure or differentiated network assets may experience margin pressure because underlying model and GPU providers retain substantial economics. The strongest position should belong to companies that combine routing intelligence with infrastructure ownership, global traffic distribution, security, and developer integration. NEAR-TERM TRADING CATALYST: AI gateway traffic, number of active developers, token volumes, model-routing adoption, and paid conversion should become increasingly useful leading indicators for Cloudflare and Akamai. Growth in agent-generated traffic is particularly important because agents can create materially more requests than human-prompted applications. LONG-DURATION FUNDAMENTAL SHIFT: The inference control plane may become more valuable than access to any individual model. As model quality converges and customers adopt open and closed models simultaneously, routing platforms can optimize business outcomes per dollar and reduce vendor dependence. This creates a durable software layer between applications and foundation models, analogous to traffic-management and orchestration layers that became critical in earlier cloud architectures. AI INFRASTRUCTURE FINANCING AND EQUITY QUALITY RAPID AI GROWTH REMAINS CAPITAL INTENSIVE, MAKING ALL-IN CASH RETURNS MORE IMPORTANT THAN REVENUE OR ADJUSTED EBITDA (READ-THROUGH 8) AFFECTED COMPANIES AND IMPACT: DigitalOcean Holdings, Inc. (DOCN: US) — POSITIVE RELATIVE BALANCE-SHEET IMPACT, BUT NEUTRAL-TO-NEGATIVE FOR NEAR-TERM CASH CONVERSION. CoreWeave, Inc. (CRWV: US) — NEGATIVE, MODERATE-TO-HIGH EQUITY-RISK READ-THROUGH. Nebius Group N.V. (NBIS: Netherlands) — NEGATIVE, MODERATE EQUITY-RISK READ-THROUGH. Applied Digital Corporation (APLD: US) — NEGATIVE, MODERATE-TO-HIGH EQUITY-RISK READ-THROUGH. IREN Limited (IREN: Australia) — NEGATIVE, MODERATE EQUITY-RISK READ-THROUGH. SUPPORT FROM THE CALL: DigitalOcean equitized approximately $472M of 2030 convertible notes, reducing pro forma net leverage to approximately 0.7x and creating additional capacity for equipment financing. Management expects to remain comfortably below a 4x net-leverage ceiling and stated that equipment financing is available at attractive rates. Adjusted free cash flow margin is guided to 11%-13%, while management separately stated that the company should remain cash generative after principal payments and other financing obligations. Data-center capacity requires approximately 1 year from lease signature to revenue generation, creating a material interval between financial commitment and revenue recognition. TRANSMISSION MECHANISM: AI infrastructure providers must secure power, leases, servers, accelerators, networking, and cooling systems before the corresponding customer revenue is recognized. Even when capacity is substantially precommitted, the timing mismatch creates financing needs and exposes equity holders to construction delays, hardware obsolescence, interest expense, refinancing risk, customer-credit risk, and dilution. Equipment financing can improve cash matching, but it does not eliminate the economic cost of the assets or the obligation to repay principal. The call reinforces the need to distinguish adjusted EBITDA and adjusted free cash flow from cash generation after all equipment purchases, lease payments, debt principal, interest, and financing commitments. A provider can report rapid revenue and EBITDA growth while generating limited fully burdened free cash flow if each incremental dollar of revenue requires significant new infrastructure. The most important sector metrics should therefore include gross profit per megawatt, cash investment per megawatt, equipment-financing principal, utilization, contract duration, payback period, asset life, and fully diluted free cash flow per share. DigitalOcean is relatively better positioned because it has positive operating margins, material adjusted free cash flow, low pro forma leverage, diversified customers, and a software layer intended to raise revenue per megawatt. The call nevertheless shows that even a profitable operator must actively restructure its capital base to fund growth. The read-through is consequently more negative for peers beginning with weaker cash generation, greater customer concentration, or heavier reliance on external financing. NEAR-TERM TRADING CATALYST: Financing announcements, convertible issuance, equipment-backed debt, lease commitments, equity raises, and changes in diluted share counts should be treated as core operating variables rather than ancillary capital-markets events. Rising rates, widening credit spreads, or data-center delays would disproportionately affect companies with limited current cash generation. LONG-DURATION FUNDAMENTAL SHIFT: The AI infrastructure sector is likely to bifurcate between platforms capable of funding growth internally and companies dependent on recurring external capital. Revenue growth alone will not determine equity performance. Sustainable value creation will depend on whether software attachment and utilization increase cash returns faster than depreciation, financing costs, and capital requirements. DigitalOcean’s statement that “software makes megawatts more valuable” is therefore also the appropriate valuation test for the broader sector: the winning platforms must demonstrate that each incremental megawatt creates more fully burdened cash flow, not merely more contracted revenue. SOURCE MATERIAL: DigitalOcean Holdings, Inc. Q2 2026 Earnings Call Transcript, dated 08/04/26.

• 
  Sanket Patrikar (@PatrikarSanket) reported 55 minutes ago

  @Cloudflare I TOOK THE WRONG NAME PLEASE HELP ME

• 
  JTCrawford (@JtCrawford) reported 55 minutes ago

  Cloudflare ditched enterprise security tools for a $58/month AI agent while vendors charge $200k for the same capability. Either security has the worst price discovery in history or we've been getting fleeced. #InfoSec #DefenseIndustry

• 
  𝘽𝙍𝙍𝙍𝙍 (@BRRRRcollects) reported 56 minutes ago

  @ufhouck @Cloudflare Web3: Naked and Poor has a ring to it

• 
  63green (@63green) reported 58 minutes ago

  The spam phone calls and emails from @googlecloud sales people automatically disqualifies them from consideration. Same reason I refuse to use @Cloudflare. If the quality and reputation of your product doesn’t speak for you, **** off, don’t call or email, I’m not interested.

• 
  Cluster Protocol (@ClusterProtocol) reported 60 minutes ago

  @Cloudflare traditional banking APIs are too slow and restrictive for autonomous agent execution loops

• 
  Base Posting (@baseposting) reported 1 hour ago

  CLOUDFLARE ANNOUNCES SUPPORT FOR X402 MICROPAYMENTS

• 
  Kartik (@1kartikkabadi1) reported 1 hour ago

  @Chinoman10_ @asciidotdev Yes, this is just an MVP. Next version will support cloudflare, box, and your own machines/custom. Cloudflare is great for this sort of stuff too, just that it doesn't have a full VNC box