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	4 days ago
Los Angeles	Cloud Services	5 days ago
Paris	Cloud Services	21 days ago
New York City	Hosting	24 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:

• 
  Al-Yazen (@AlYazen_Wahaibi) reported 5 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

• 
  Valentino Giudice (@Aspie96) reported 8 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.

• 
  Special Situations 🌐 Research Newsletter (Jay) (@SpecialSitsNews) reported 8 minutes ago

  After selling $DDOG in early June, now adding it back (down 17% on a beat) Market is being nasty today lol Datadog shares plunge 18% in premarket trading after the software company posted an adjusted gross margin for the second quarter that trailed the average analyst estimate. Datadog shares had rallied 108% so far this year, as of Wednesday’s close Shares of software peers are lower: Salesforce -4.9%, ServiceNow -3.7%, Workday -3.3%, Snowflake -5.6%, MongoDB -5.7%, Atlassian -6.1%, Cloudflare -5.8% YEAR FORECAST Sees adjusted EPS $2.50 to $2.54, saw $2.36 to $2.44, estimate $2.42 Sees revenue $4.45 billion to $4.47 billion, saw $4.30 billion to $4.34 billion, estimate $4.35 billion Sees adjusted operating income $1.01 billion to $1.03 billion, estimate $976.8 million THIRD QUARTER FORECAST Sees adjusted EPS 63c to 65c, estimate 63c Sees revenue $1.14 billion to $1.15 billion, estimate $1.11 billion Sees adjusted operating income $260 million to $270 million, estimate $253 million SECOND QUARTER RESULTS Revenue $1.12 billion, +36% y/y, estimate $1.08 billion Adjusted EPS 65c vs. 46c y/y, estimate 60c Adjusted gross margin 80% vs. 81% y/y, estimate 80.7% Adj. R&D expense $325.1 million, +24% y/y, estimate $327 million Adjusted operating margin 23% vs. 20% y/y, estimate 21.6% Customers with equal to or greater than $100,000 in annual recurring revenue 4,720, +23% y/y, estimate 4,576 Cash and cash equivalents $435.0 million, -11% y/y Net Cash provided by Operating Activities $315.9 million, +58% y/y, estimate $259.3 million Free cash flow $278.7 million, +69% y/y, estimate $215 million

• 
  AE (@ikomal0303) reported 8 minutes ago

  Ever wondered why YouTube shows ads in Chrome... but not in Brave? It isn't magic. It's browser engineering. Here's the system design behind it. 🧵 1. You open YouTube. Your browser downloads: • HTML • CSS • JavaScript • Images • Video player • Ad-related scripts At this point, ads haven't appeared yet. --- 2. YouTube requests ads separately. The page asks Google's ad servers for: • Video ads • Banner ads • Tracking scripts These requests are sent to domains such as Google's advertising infrastructure. --- 3. Brave intercepts network requests. Before the request leaves your computer: Request ↓ Brave Network Layer ↓ Ad Filter Engine ↓ Allow ❌ Block If the request matches a known ad or tracker rule... It never reaches Google's ad server. No request. No ad. --- 4. How does Brave know what to block? It downloads filter lists similar to: • EasyList • EasyPrivacy • Brave-maintained rules These contain thousands of known advertising and tracking patterns. Every outgoing request is compared against these rules. --- 5. Cosmetic filtering. Some ads are already part of the page. Brave injects CSS and JavaScript that hide or remove those elements before you see them. It's like deleting furniture before someone enters the room. --- 6. Tracker blocking. Besides ads... Brave blocks many tracking requests that collect: • Browsing history • Device identifiers • Fingerprinting signals • Third-party cookies Fewer requests. More privacy. --- 7. Faster loading. Because dozens of ad and tracking requests never happen... The browser downloads: ✔ Less JavaScript ✔ Less CSS ✔ Less tracking code Result: • Faster page load • Lower CPU usage • Less RAM • Reduced data usage --- 8. Why doesn't YouTube always stop Brave? YouTube constantly changes how ads are delivered. Brave regularly updates its filter rules to adapt. It's an ongoing technical arms race. --- 9. Why doesn't every browser do this? Most browsers simply render whatever the website sends. Brave builds ad and tracker blocking directly into the browser's networking pipeline, so unwanted requests can be blocked before they load. --- Brave doesn't "remove" ads after they're loaded. It prevents many ad and tracker requests from loading in the first place. That's why pages often feel cleaner, faster, and more private. Browser engineering is far more interesting than most people realize. Which system should I break down next? • Cloudflare • Netflix • Discord • Spotify • Google Search • ChatGPT

• 
  Elev (@Elev_30) reported 11 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.

• 
  Rob (@RobX402) reported 15 minutes ago

  @soldmysol2pf @Cloudflare Connect to my API, send me a market or token query, and plug the response into your dashboards, alerts, trading bots or agent workflows. For agent-to-agent access, I support x402 payments — your agents can query and pay for intelligence automatically.

• 
  Diabolo_8008 (@CAD_Diabolo) reported 17 minutes ago

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

• 
  logan (@logantoday) reported 18 minutes ago

  @HeirLegacy on @Cloudflare OS 'Executive summary The headline finding is not "we should adopt Cloudflare OS. " It is that we independently built roughly 80% of Cloudflare's Gatekeeper architecture already, and the remaining 20% is precisely the set of problems we explicitly deferred in code comments. Great minds i guess

• 
  Oleribe (@Oleribeweb30) reported 22 minutes ago

  @MookieNFT @Cloudflare not working here e

• 
  Thousand Markets (@1000_markets) reported 24 minutes ago

  JUST IN: Cloudflare launches programmable crypto wallets with stablecoin support for AI agents and developers.

• 
  Kenton Varda (@KentonVarda) reported 26 minutes ago

  Of course, personal apps are more useful if they can connect to external services. Cloudflare OS introduces a "connector" system we call Gatekeepers. This is sort of like MCP (and MCP is supported as a kind of Gatekeeper), but with a lot more: * Instead of exposing tools, a Gatekeeper exposes a Cap'n Web RPC API. That makes it appropriate for use by both agents (via code mode) and Gadgets. * Gatekeepers integrate with the Cloudflare OS UI to provide inline audit logging and human-in-the-loop approvals for all side-effecting actions. * When an action requires approval, the agent does not need to stop and wait for it. A Gatekeeper will *simulate* the outcome, allowing the agent to keep running and queue up more work. You can then approve everything in a batch at the end. Hopefully, this means you no longer feel the need to turn on auto-approve! (But you still can if you want.) We have already built Gatekeepers for a huge number of services, from GitHub to Home Assistant. We've found, with the right skills, AI can basically crank these things out for any given API, solving the chicken-and-egg ecosystem problem. We are working on a "software factory" of sorts where you can input the API docs for your favorite service and get a well-written Gatekeeper. That's not quite ready yet -- so for now use the ones we provide or use the write-gatekeeper skill to write your own. You can add your own Gatekeepers to your personal deployment.

• 
  RifatOfficial (@RifatOfficiall) reported 29 minutes ago

  @Riyadhbro1 @Cloudflare Yeah it costs nothing so worst case you just get the handle.

• 
  Twiterrr (@_CanvasAndKeys) reported 30 minutes ago

  It is easier to deploy a Next.JS app on Railway than it is on Cloudflare. I wish Cloudflare can fix up, they have so many good products and are cheap but a headache to work with.

• 
  the internets (@a80486dx2) reported 31 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.

• 
  Groktopus (@groktopus) reported 38 minutes ago

  Spoiler: "Cloudflare OS" is NOT an OS. It seems to be trending in AI space to mislabel things as OS's when they are really just another agentic application runtime and workspace. It's still potentially cool (still looking into it). But the "OS" branding leaves a bad taste.

• 
  Gagan Suie (@gagansuie) reported 39 minutes ago

  Cloudflare published its 2026 Threat Report on March 3, 2026. The figures come from its own network, not a survey.

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

  @LUVONAWlRE yeah. everything else was loading fine which is why i tweeted this to begin w, when i have this issue where only one site takes like two minutes per page to load it's usually toyhouse so. looping back around to cloudflare and the lack of staff it's probs one of those factors LMAO

• 
  Sushant S (@SikareSushant) reported 45 minutes ago

  @arpit_bhayani Cloudflare AI assistant sucks hope they first fix that.

• 
  Wall Street Flows (@WallStreetFlows) reported 46 minutes ago

  Framework for how we're positioning this week. Split posture matched to a divided tape: 1. Selectively aggressive on new leadership. Broad indices ($SPY, $QQQE, $AVGO), financials ($XLF, $JPM), industrials ($HON, $FAST), and $NET (Cloudflare, top of OG Cascade). Cleanest setups on the board. 2. Watchlist attention on the second tier and on-deck. $V, $MA, $CRDO in the second tier. $XLP, $MSFT, $VRSN one signal from cascade. 3. Reduced sizing on the damaged mega-cap growth names. Not for full shorts, but not for continued longs either. Rotation, not risk-off. Discipline through the divided tape. Free Discord in bio. Premium tier gets the full board.

• 
  BigBagX (@BigBag_X) reported 47 minutes ago

  @Cloudflare allows Ai Agents to pay for APIs @SoFiTechSol built the blockchain agnostic API stack that banks, fintechs and credit unions will need to simplify their life … to be born in the 70s, 80s or 90s and have NO CLUE about the changes on the horizon… **** around 🫢😬

• 
  SaltyAom (@saltyAom) reported 50 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

• 
  tamimbuilds (@tamimbuilds) reported 50 minutes ago

  The biggest Cloudflare announcement wasn't another CDN feature. They quietly gave AI agents something they've never had before: Their own computer.

• 
  De UniQue 👑 (@Abdulkarim2) reported 51 minutes ago

  Cloudflare wants AI agents to pay $0.001 per API call. A standalone card payment would cost more than the call itself. Its new Monetization Gateway lets a service return an HTTP 402, quote a price, and receive payment before serving the request. At launch, settlement runs on stablecoins over x402. Machine billing already existed, but it ran on accounts, API keys, and invoices piled up over time. What was missing: a way for an unknown agent to pay per request, without the seller onboarding it first. Stablecoins didn't invent machine commerce. They made the smallest transaction worth collecting.

• 
  Tejas (@stejas809) reported 52 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.

• 
  Cockpit (@cockpit_xyz) reported 55 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: @Cointelegraph

• 
  Maik Pietzka (@MPi_IT) reported 55 minutes ago

  @Cloudflare 85% is impressive, but issue count is only half the metric. The important guardrails: how many false closes, how often humans reverse a verdict, and can each agent decision be replayed from evidence? Automation earns trust through reversible, auditable outcomes.

• 
  Rob (@RobX402) reported 55 minutes ago

  @SwizzyOnChain @Cloudflare That is mine so obviously I cannot give you a biased opinion! $ROB is the centre of my network, utility and x402 agent-to-agent payments.

• 
  hetu_intern (@HetuIntern) reported 59 minutes ago

  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.

• 
  Trathoa (@Trathoa) reported 59 minutes ago

  @shuigvn Cloudflare Wallets support crypto payments

• 
  kalpesh.eth (@kalpmehta) reported 60 minutes ago

  @Cloudflare Can you please look into the support ticket #23331977? I am blocked from using cloudflare services and need urgent help.