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 (39%)
• Domains (22%)
• Web Tools (22%)
• Hosting (11%)
• E-mail (6%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Cloud Services	13 days ago
Los Angeles	Cloud Services	14 days ago
Paris	Cloud Services	30 days ago
New York City	Hosting	1 month ago
Manchester	Domains	2 months 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:

• 
  Devin Kurant (@DevinKofsky) reported 3 minutes ago

  @janxpm @Namecheap I spent 2 hours this morning thinking it was my fault and configuring cloudflare, only to discover the real issue. Clients think I broke there sites.

• 
  Onramp (@OnrampBitcoin) reported 3 minutes ago

  More of the internet's traffic is now agents than humans. Cloudflare expects a thousand to one within five years. The whole web runs on you showing up to look at an ad. If a model reads the page for you, nobody shows up and nobody gets paid. The fix has been sitting there unbuilt since the nineties.

• 
  John C. 🇹🇹 (@jcamachott) reported 6 minutes ago

  @bhartzer @Namecheap "If you used @Cloudflare, for example, for DNS, then you could simply log into CF and point the DNS to another web host and your site or service would be back up and running in minutes." Not always as simple as it sounds. This also means restoring a website with yesterday's data to a new hosting account. It's really unusual for a hosting account to go down for several hours like this

• 
  Andy aka Mrdudestar (@mrdudestar) reported 6 minutes ago

  @FootballManager @FootballManager cloudflare error trying to sign in to fmfc

• 
  Timzen (@timzen_ofc) reported 6 minutes ago

  @timonvlr @riotgames @VALORANT website told me that they have server problems after I tried to relog in... So I asked if its maybe cloudflare. Idk whats the problem :/

• 
  Sterling Labs (@sl_wire) reported 7 minutes ago

  A crawl is a program walking the web on its own, saving a copy of each page to build the pile of text a model learns from. Each page gets taken once. That was 36.40% of AI bot traffic in January 2025 and 44.56% in July. Agent traffic is the other thing, a page fetched right then because you asked, and it was 2.63% last October and 2.65% in July. Nine months flat. Both are shares of AI bot traffic, not of the web. @CloudflareRadar counts this because Cloudflare sits in front of a big share of it, and out on the whole web bots were 34.81% of requests in July against 65.19% human. Agents are at most 0.92% of everything, and that assumes every bot is an AI bot. Call it a third of a percent. The tollbooth is already built. $NET opened Pay Per Crawl in private beta on July 1 at a one cent minimum per successful retrieval, and the network already returns more than two billion payment required responses a day. Its own June investor day line was that the vast majority never become a transaction. Purpose is self declared at registration and nobody audits it, so hold the levels loosely. Anthropic’s crawl to referral ratio fell from about 8,800 requests per referral in April to 2,800 in July, and Adobe measured AI referred retail visits up 138% year over year in May. We are following what the models tell us. The agents aren’t out doing the shopping. Yet.

• 
  Chan Walrus (@chanwalrus) reported 7 minutes ago

  @kidariseyogt @NamecheapCEO @Cloudflare I've had some hideous problems with Cloudflare in the past to the point where if I see a captcha, I just close a site. Probably best not to get into it here as my GOD... I have a LOT of work to do today. XD

• 
  Jabol aso (@Jabolaso) reported 11 minutes ago

  @mikeydsoftware @Aditya_181105 Self managed server can use cloudflare services, but i dont have a usecase to use vercel, if im a self managing. Most of vercel service are related to their app deployment service

• 
  Alex @Bickov (@bickov) reported 14 minutes ago

  Found out this week that Cloudflare was telling ClaudeBot, GPTBot and every other AI crawler to stay off my site. I never set that. A default toggle was writing my robots.txt for me and I had no idea

• 
  Alpha Batcher (@alphabatcher) reported 15 minutes ago

  A cold email got him a Cloudflare interview, no leetcode anywhere First round was a Lead Staff Engineer from the AI Workers team going deep on rooflining, batch size tradeoffs, p50 against p99, TTFT, and where a pipeline actually bottlenecks He had all of it from optimising rerankers and embedding models on in-house GPUs He still did not get the role, because encoder-only stacks skip attention and KV cache, so vLLM and SGLang never showed up in his day job 44 to 58 LPA, lost to a gap he can name in one sentence, which is what makes the writeup worth reading

• 
  Rattey (@theRattey) reported 17 minutes ago

  figma made design multiplayer. ai just made it single player again. designers spent ten years drifting away from code. frameworks kept changing, figma didn't, so everyone settled into rectangles and flows. now ai writes html without complaint, and the quickest way to show an idea is a real page in a browser. real text, real hover states, ten versions in one file. the mockup is the website. the trade is collaboration. one team i read about ran a two week launch sprint entirely in html prototypes. best visual work they'd done in years. sharing it was misery. the marketing lead couldn't open the file, let alone change a word. feedback came in a separate doc. nobody knew which of the six saved versions was the latest. my fix is simple. the agent builds the page, pushes it to vercel or cloudflare, and i send one link. it has a comment box built in. teammates leave notes on it, the agent reads them and makes the edits. no separate doc, no version chaos. and before any of that, twenty minutes asking if the thing should exist at all. building is almost free now. thinking still costs the same.

• 
  Ryan Hart (@thisdudelikesAI) reported 21 minutes ago

  I replaced my $2k/mo n8n stack with one Cloudflare Worker Sounds insane but hear me out n8n was doing 4 things for me: 1. Scraping 6 sites every 15 min 2. Running them through an LLM for classification 3. Dropping the good ones into a database 4. Firing a Telegram alert when something scored high That was it. 4 nodes worth of logic spread across 12 automations, a hosted plan, a Postgres addon, a queue worker, and a bill that kept climbing every month Then I sat down with Codex and asked one question: "what would this look like as a single script" 30 minutes later I had a Cloudflare Worker doing the exact same thing Here's the full stack: - Cloudflare Worker (the whole app, one file) - Cron Triggers (replaces n8n's scheduler, free) - Workers KV (replaces Postgres for this use case, free tier is plenty) - Workers AI or a direct call to Gemini Flash (classification, pennies) - Telegram Bot API (same as before, free) Total cost: $5 a month. And that's only because I upgraded the Worker plan for longer CPU time. You could genuinely run this on $0 The lesson isn't that n8n is bad. It's great for prototyping and for people who don't code The lesson is that once you know what your automation actually does, 90% of the visual builder is overhead you're paying for A Worker is a function. Your automation is a function. Skip the middleman If you're paying $500+ a month for any no-code automation tool right now, do this today: 1. Open Codex or Claude Code 2. Paste your workflow logic in plain english 3. Ask it to rebuild the whole thing as a single Cloudflare Worker 4. Deploy with 'wrangler deploy' 5. Delete the n8n subscription You'll be shocked how small the code actually is The no-code wave was a bridge. AI-written code is the destination

• 
  Joseph Lorenzo Hall, PhD (@JoeBeOne) reported 25 minutes ago

  The archive is public, so this isn’t a “harvest now, decrypt later” use case (no secrets!). It is a useful real-world compatibility test. I’d love to see Backblaze add PQ key exchange support to B2 so Cloudflare-to-origin connections can use it without falling back to X25519. 6/6

• 
  Artyom Shimanski (@a_shimanski) reported 28 minutes ago

  @sloaxleak @Namecheap @Cloudflare yeah, you're right. paying isn't the problem, picking one that stays up is

• 
  @jorgediazapps (@jorgediazapps) reported 29 minutes ago

  I wired Grok Bot into the actual stack I run the company on. Not a toy demo. MCP where it exists. Raw API or the browser where it doesn’t. Live MCP right now: Gmail, Google Calendar, Google Drive Stripe + Link Coolify (read-only official MCP — writes go through their API) Cloudflare docs, builds, observability Typefully, Castmagic, Octolens DataForSEO, DataFast, Apify Resend, AgentMail Composio, Context7 No real MCP, still connected: Enlac. ee (short links + static hosting — dashboard + API) Outrank (blog → Strapi webhook) Strapi on cms. doublemyleads .com Facebook via the signed-in browser (never paste the password) GitHub official MCP The bot doesn’t get a new brain. It gets the same tools I already pay for. That’s the whole trick.

• 
  ./ivan (@sloaxleak) reported 32 minutes ago

  @a_shimanski @Namecheap @Cloudflare Haha. Or just pay for a reliable email service: Google Workspace, Microsoft 365, or a Proton subscription with a custom domain. There are options. I love Cloudflare, but not everything needs to be solved by them

• 
  City of Hats (@CityofHats) reported 34 minutes ago

  @signalapp @Cloudflare Signal’s AKV is a useful improvement, but “automatic” deserves an asterisk. Signal still operates the central key directory, while Cloudflare and Trail of Bits are explicitly trusted auditors. AKV proves consistency of the identifier → key mapping; it does not prove the identity behind that identifier. Even more interesting: today, verifying another user still requires knowing their phone number, and the user must explicitly open Safety Number and select “Verify automatically.” So this is better tamper detection — not the elimination of trust. The architectural question remains: why should identity/key discovery depend on a centralized directory and external witnesses at all?

• 
  Fast&Final (@FastFinalAlgo) reported 35 minutes ago

  Cloudflare added MCP detection at the network level today $Algo 🔮 @marcvl

• 
  ruminations (@amphib0ly) reported 35 minutes ago

  signals need execution and a lot of people who want to use q are very busy they are founders / builders and are down to try stuff but also just want to put money in a wallet and let it work for them no amount of UI polish will make them want to use the UI and adding more assets won't sway them - they just want to buy convenience so, we made a baby sister for Q named Cassie - short for Cassandra, look it up cassie will help users execute trades on Quotient signals in their local environment or in a deployed, cloudflare run-time they control users bring capital Q brings intelligence Cassie brings execution

• 
  Card Trading Marketplace (@CTM_Market) reported 37 minutes ago

  @a_shimanski @Namecheap @Cloudflare Lol our business email has been down since 9 am

• 
  Ross (@402Signal) reported 38 minutes ago

  One nuance to this 93% figure - its dollars settled. @Algorand x402 settlements recently jumped ~30x in 5 days, while @solana has also seen strong payment growth. More txs with fewer dollars may actually be the machine-commerce signal. Agree on @Cloudflare. Q4 should test whether distribution turns into repeat paid usage. $ALGO $SOL

• 
  Aaron Boodman (@aboodman) reported 45 minutes ago

  Think of DOs by analogy to a serverless function. A better (and much funnier) name might have been "serverless objects". A "serverless function" is a stateless javascript program you upload to, say, Vercel. The external interface is a function. It is reachable at a URL. You send a request to the URL, Vercel instantaites your program, sends the exported function the request, gets the function result, send the result to you as an HTTP response, then destroys the program. DOs are exact same thing, but stateful. You upload a JavaScript program to CloudFlare. The external interface is a *class*, not a function. DOs are reachable at a URL. You send a request to the URL and CloudFlare invokes your program, instantiates your class, and sends a particular method on the class the request, gets the result, and send it to you as an HTTP response. So far, just a more complicated version of serverless functions. The difference is that CF keeps that class running for awhile. If another request comes into same URL, CF routes it to the same running program and the same exact JavaScript object in memory. So you can keep state in that JS objects across invocations. That's it, that's the whole pitch. These little javascript programs are low-power (last I looked max ram was maybe 1GB?). But they are cheap to run so you can have zillions of them. This makes them a very useful primitive for certain kinds of problems, like say chatrooms, multiplayer games, etc.

• 
  Shraddha Bharuka (@BharukaShraddha) reported 46 minutes ago

  📂 SaaS Stack ┃ ┣ 📂 Frontend ┃ ┣ 📂 React ┃ ┣ 📂 NextJS ┃ ┣ 📂 Vue ┃ ┣ 📂 TailwindCSS ┃ ┗ 📂 Shadcn UI ┃ ┣ 📂 Backend ┃ ┣ 📂 NodeJS ┃ ┣ 📂 Django ┃ ┣ 📂 Laravel ┃ ┣ 📂 FastAPI ┃ ┗ 📂 Express ┃ ┣ 📂 Database ┃ ┣ 📂 PostgreSQL ┃ ┣ 📂 MySQL ┃ ┣ 📂 MongoDB ┃ ┣ 📂 Redis ┃ ┗ 📂 Supabase ┃ ┣ 📂 Auth ┃ ┣ 📂 Clerk ┃ ┣ 📂 Auth0 ┃ ┣ 📂 Firebase Auth ┃ ┣ 📂 Supabase Auth ┃ ┗ 📂 NextAuth ┃ ┣ 📂 Payments ┃ ┣ 📂 Stripe ┃ ┣ 📂 Paddle ┃ ┣ 📂 Dodo Payments ┃ ┣ 📂 Lemon Squeezy ┃ ┗ 📂 Polar ┃ ┣ 📂 Emails ┃ ┣ 📂 Resend ┃ ┣ 📂 SendGrid ┃ ┣ 📂 Mailgun ┃ ┣ 📂 Postmark ┃ ┗ 📂 Amazon SES ┃ ┣ 📂 Storage ┃ ┣ 📂 AWS ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 Google Cloud Storage ┃ ┣ 📂 Supabase Storage ┃ ┗ 📂 Uploadcare ┃ ┣ 📂 Deployment ┃ ┣ 📂 Vercel ┃ ┣ 📂 Netlify ┃ ┣ 📂 Railway ┃ ┣ 📂 Render ┃ ┗ 📂 AWS ┃ ┣ 📂 Domains and DNS ┃ ┣ 📂 Namecheap ┃ ┣ 📂 Hostinger ┃ ┣ 📂 Cloudflare DNS ┃ ┣ 📂 Google Domains ┃ ┗ 📂 SiteGround ┃ ┣ 📂 Analytics ┃ ┣ 📂 Google Analytics ┃ ┣ 📂 Plausible ┃ ┣ 📂 PostHog ┃ ┣ 📂 Mixpanel ┃ ┗ 📂 DataFast ┃ ┣ 📂 Monitoring ┃ ┣ 📂 Sentry ┃ ┣ 📂 LogRocket ┃ ┣ 📂 Datadog ┃ ┣ 📂 NewRelic ┃ ┗ 📂 UptimeRobot ┃ ┣ 📂 DevOps ┃ ┣ 📂 Docker ┃ ┣ 📂 Kubernetes ┃ ┣ 📂 GitHub Actions ┃ ┣ 📂 CI CD ┃ ┗ 📂 Terraform ┃ ┣ 📂 Search ┃ ┣ 📂 Algolia ┃ ┣ 📂 Meilisearch ┃ ┣ 📂 Elasticsearch ┃ ┣ 📂 Typesense ┃ ┗ 📂 OpenSearch ┃ ┣ 📂 AI Integration ┃ ┣ 📂 OpenAI API ┃ ┣ 📂 Anthropic API ┃ ┣ 📂 Replicate ┃ ┣ 📂 HuggingFace ┃ ┗ 📂 Gemini API ┃ ┣ 📂 Integrations ┃ ┣ 📂 Zapier ┃ ┣ 📂 Make ┃ ┣ 📂 n8n ┃ ┣ 📂 Pabbly ┃ ┗ 📂 Webhooks ┃ ┣ 📂 Security ┃ ┣ 📂 SSL ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 WAF ┃ ┣ 📂 Rate Limiting ┃ ┗ 📂 Secrets Management ┃ ┣ 📂 Marketing ┃ ┣ 📂 Search Console ┃ ┣ 📂 Outrank ┃ ┣ 📂 Buffer ┃ ┣ 📂 Analytics ┃ ┗ 📂 Kit ┃ ┗ 📂 Customer Support ┣ 📂 Intercom ┣ 📂 Crisp ┣ 📂 Zendesk ┣ 📂 Tawk ┗ 📂 HelpScout

• 
  Bob Stolzberg (@BobStolzberg) reported 47 minutes ago

  $1 .app or .dev domain registration on @Cloudflare even with the FREE plan! WTF are you waiting for?! Best place to build.

• 
  Frankenmint (@Frankenmint) reported 49 minutes ago

  @NEEDcreations this is bad idea, if you must do it, you should create a tunnel via cloudflare and expose your printer to the web then you can fire off the print job (but so could anyone with your ip address)

• 
  Joseph Lorenzo Hall, PhD (@JoeBeOne) reported 51 minutes ago

  Cloudflare support traced the 525 to a post-quantum-only origin setting. Cloudflare could offer X25519MLKEM768, but B2 couldn’t negotiate it—and no classical key exchange was available as fallback. The handshake failed before certificate validation. 4/6

• 
  solopath (@pathlessknown) reported 51 minutes ago

  @HotAisle Damn nvm then maybe not meant for you haha It’ll save you money and look pretty with all cloudflare info in real time and secure too

• 
  Sajid Mehmood (@smehmood) reported 51 minutes ago

  @axat_div @ethan_breitk @binsquares Cloudflare, no. For the others, they all started on the hyperscalers, but several of them are moving off in a major way (e.g. Railway Metal, Modal uses a number of neoclouds, etc.) And even if the hyperscaler is the underlying compute, it's meaningful that they are losing the direct customer relationship

• 
  Jota (@jota__feldmann) reported 55 minutes ago

  I'm in love with Cloudflare Durable Objects. They make so much sense for a ton of domains and problems we've spent way too much time frying our brains trying to solve elsewhere.

• 
  m81 (@m81bode) reported 59 minutes ago

  @PhaedraXTeddy @Cloudflare Why does this ***** have maga in his name? His ***** *** would be in prison if he were in America. It’s too bad China is a ********.