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 (50%)
• Domains (25%)
• Hosting (25%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Hosting	6 days ago
New York City	Cloud Services	24 days ago
Los Angeles	Cloud Services	26 days ago
Paris	Cloud Services	1 month ago
New York City	Hosting	1 month ago
Manchester	Domains	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:

• 
  Nicu Chiciuc ▣ (@nicu_tsx) reported 4 minutes ago

  Already have apps? Import any repo. Connect/create Convex projects and Cloudflare Workers. The "new app" flow is just a simple version of all the flows that we support. Every PR gets preview deploy Every local worktree gets local deploys you can use dozens of agents in parallel

• 
  ✨️ Reina Cruz ✨️ 🥼🧤 ☭⃠ (@realReynaCruz) reported 4 minutes ago

  @ritakozlov @Cloudflare Fix human verification

• 
  Bash (@bashirbuilds) reported 5 minutes ago

  @jpschroeder Finding an $8.8k Cloudflare Durable Object loop from the invoice instead of an alert is the worst possible detection method. Glad they adjusted it still a monitoring gap.

• 
  ardhy samjaya (@samjayaardhy) reported 5 minutes ago

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

• 
  Web3.0 (@Web3_0_AMATW) reported 7 minutes ago

  @smartholdem P2P hosting without Cloudflare? Say less, I'm building my dApp on this tomorrow. I'm so tired of AWS bills and sudden account freezes. Does it support React/Next.js?

• 
  Current Events, Sports & Christian Content (@PartesanJournal) reported 10 minutes ago

  Goodnight @X, I might login tomorrow, if @Cloudflare allows me. Here is an idea, I logged in to my other account using the hand gestures/face recognition on the App, make this available on PC/Laptop Web browsers

• 
  )) (@truthofkosova) reported 12 minutes ago

  @adityadotdev @rauchg You need custom rules for Cloudflare in order to make the AntiDDoS really work, I'll be happy to help!

• 
  ☉rthonormalist🧭✡️ (@orthonormalist) reported 16 minutes ago

  @MorlockP @travis4nh I am in the process of talking to my clanker about getting a one click deploy for a free tier cloudflare of mcp managed todotxt so I can keep track of the infinite little tasks that are too annoying to write down ('mom wants me to email her this link') etc. and get a morning digest

• 
  Nana (@nmanu__) reported 18 minutes ago

  Hi @dillon_mulroy I’ve applied to the cloudflare startups program for a product I’m working on for days and I’ve still not heard anything back. Could you help with anyone I could speak with?

• 
  skubopis (@skubopis) reported 21 minutes ago

  @klausbyskov @Cloudflare Have you tried the CLI instead? Usually I’ll go for CLI over MCP when possible. Especially if it is a remote MCP server = slow and expensive

• 
  Yoonsun Lee (@everdenepublic) reported 23 minutes ago

  Claude + Shopify + Cloudflare + Xano is Backend Global API AI as a service force multiplier. Claude + Shopify for Theme is a waste of tokens. We don't need to solve the theme setup. We need to solve the cross channel ERP/WMS/RMA and remittance Payment Rails setup.

• 
  pystar (@pystar) reported 23 minutes ago

  OpenAI has joined the WebMCP hype train, same month as @Cloudflare. Hunch has been on it since Feb'26. "Never wrong, just early."

• 
  kevops (@kevvOH_) reported 24 minutes ago

  i am unable to login successfully into cloudflare

• 
  Ben Haupt (@benchaupt) reported 30 minutes ago

  I'm noticing a pattern of new(er) engineers (and vibe-developers) over-designing their tech stacks for simpler projects (e.g, mobile app backend on AWS)... It should be a pretty simple decision: buy the things where being wrong is a compliance event or an outage. Database = Postgres (just raw postgres) Auth = Auth0, Cognito or Clerk (compliance event) Email = Resend or SES (deliverability is pain) Payments = Stripe Cache = Redis Queue = Rabbit or Bull CDN + edge = Cloudflare Analytics = PostHog Observability = Prometheus + Loki + Sentry + Better Stack SMS = Twilio Compute = VPS (Synteq (biased), digital ocean, etc)

• 
  notmyname (@beyondfinites) reported 31 minutes ago

  So a comment on these startup programs 1. computer use bot to automate this as I tell each client to do this step for all their digital businesses (cloudflare, Microsoft, etc.) AWS is instant to get $1k after form filing 2. All other forms are slow to respond (if ever)

• 
  ✨️ Reina Cruz ✨️ 🥼🧤 ☭⃠ (@realReynaCruz) reported 32 minutes ago

  @ritakozlov @Cloudflare Fix human verification

• 
  Matt Mazur (@mhmazur) reported 32 minutes ago

  My SaaS's support docs are something I've always updated and served through my support desk service. I decided to move them into the app. I tasked Claude with "migrate all of my support docs over to the rails app. put the content in individual markdown files. copy the existing images into the app and serve them behind a cdn." It searched the codebase and found the URL of the support docs, then scraped the docs homepage. That included links to some docs, but more importantly, links to individual doc categories, which it followed to compile a list of 83 articles. Except there were 87. Help Scout paginates categories at 20 per page, so two articles were sitting on a page two nobody links to, and two more were published but filed under no category at all. Claude probed every article ID from 1 to 170 and found all four. It parsed the HTML of those pages to figure out where the content lived, and extracted the content of each page. One interesting thing: the support docs were served by Cloudflare, which automatically obfuscates email addresses so naive scrapers can't scrape emails. I asked Claude afterwards how it figured out what emails to use. It replied: > The real address is right there in the markup, in a data-cfemail hex blob: 0f676a637f4f7f7d… The first byte is an XOR key. Here it's 0x0f = 0000 1111, so XOR just flips the low nibble of each byte that follows: 0x67→0x68 "h", 0x6a→0x65 "e", 0x63→0x6c "l", 0x7f→0x70 "p", then 0x4f→0x40 "@". Once "help@" fell out I knew the guess held and let code finish the rest. Clever. At one point Cloudflare throttled it, so it added backoff and retries and kept going. It built a parser but ran into issues (<img> and <p> sitting directly inside <ol>, between the <li>s) but worked through them, eventually converting every support doc from HTML into markdown. Then it checked its own work by diffing the rendered markdown against the live pages. 22,178 words in, 22,178 words out. Every image and every link accounted for. That's how it caught the malformed HTML in the first place: an article that came out empty. It downloaded 190 images and confirmed they'd be served behind the CDN. I told it I wanted to change the URLs from like /article/127-add-event-to-timeline to like /support/add-event-to-timeline. It did that and set up redirects so all the old URLs pointed to the new pages. The redirects resolve on the ID, not the slug, which turned out to matter: my own docs linked to four articles by slugs that had changed years ago. I asked it to look through the docs and recategorize anything as it saw fit. It recategorized 11 articles. I then said "add search functionality", so it built a new endpoint as well as the front-end so users could search the docs. It searched the codebase and found 33 links across 25 files still pointing at the old docs, and updated them all. I then told it "look through all the docs you created and verify the information is still accurate. some of it may be outdated and needs updating." It checked all 87 articles against how the product currently works. Not by reading them. It pulled every bolded UI label out of the docs and grepped the views for each one, then checked the numbers against the constants and the plan claims against the plan table. Two articles promised restrictions that don't exist anymore, including one telling free users to upgrade for a feature they already have. Nine articles named buttons that had been renamed. It fixed all of it. It also used its read-only access to the production database to look for content referencing the old doc URLs. It found one, and gave me the command to fix it. It then walked me through the changes I needed to make in Cloudflare to point the old docs subdomain at the new site. It deployed the code, waited for it to go live, then ran a bunch of cURL requests to make sure everything worked. I plan to update the deployment skill to review pushed changes and make sure the public docs reflect any key changes. Put another way: Claude will maintain the docs going forward, ensuring they're always accurate and up to date. This entire docs migration consumed maybe 30 minutes of my time. It would have probably taken me a week to do this manually in the past, and I wouldn't have done nearly as good of a job as Claude did. Pretty amazing.

• 
  Naelo — 🇪🇺 eu/acc (@naelodev) reported 34 minutes ago

  @mannupaaji @Cloudflare @cognition Never received an answer from Cloudflare after 2 months.. any tips?

• 
  🥔🥔🥔 (@argofowl) reported 35 minutes ago

  @robinebers @Cloudflare twitter drama this never happens to me been using cloudflare for a year, never run into a single issue lol

• 
  Joey (@joeyjurjens) reported 38 minutes ago

  @fuolpit @Cloudflare Maybe make a Github issue? :)

• 
  ✨️ Reina Cruz ✨️ 🥼🧤 ☭⃠ (@realReynaCruz) reported 40 minutes ago

  @Cloudflare @eastdakota @zatlyn Fix human verification

• 
  Luke Berry (@LukeberryPi) reported 41 minutes ago

  btw i moved this website behind cloudflare with waf and it solved this issue entirely actually codex computer use did it in 25 minutes - moved dns to cloudflare - moved dkim + spf railway records - added ssl and www apex redirect - blocked php word press probes and now my network logs look clean, only 200s from my own production testing

• 
  vibebuilder (@vibebuild) reported 42 minutes ago

  @thekitze Tried getting Grok Bot to authenticate Shopify and it couldn’t do it in the cloud browser, Cloudflare blocking their ***. Tried doing it locally, couldn’t do it. Eventually said **** it try it cli locally, eventually did it. Took like a ******* hour.

• 
  Troy Tessalone | Automation Ace ⚡️ (@AutomationAce_) reported 43 minutes ago

  Pro-coders forget how big of a gap there is between them and low-coders/no-coders. The avg user trying to accomplish something technical has never heard of these apps (e.g. AWS, Cloudflare, etc.) or concepts (e.g. SDK, CLI, etc.), let alone know where to even begin.

• 
  Frantisek (Frank) Borsik (@FBorsik) reported 45 minutes ago

  @eastdakota @Cloudflare Matthew, how can I turn off that stupid AI in @CloudflareRadar - it's not helping me at all, quite the contrary, I'm not able to find ISPs I'm looking for, since you guys rolled it out. Just horrible customer experience :( in product I used to love.

• 
  Ryan Djurovich 😎 (@ryan0x44) reported 45 minutes ago

  @Cloudflare How much would it cost a customer to run this, assuming exact same content and traffic?

• 
  BLOCKCAST.CC NEWS (@Blockcastcc) reported 46 minutes ago

  Socket Security has discovered 40 malicious Firefox extensions that impersonate crypto wallets like OKX, Rabby, and TronLink to steal recovery phrases and credentials. The campaign, active since March 2026, involved 77 total linked extensions, some initially posing as sports score apps before updating to include wallet-stealing code that exfiltrates data via Cloudflare Workers or remote switches. Firefox users should install extensions only from verified official developer sites, check reviews carefully, and remove any suspicious add-ons, as Mozilla acted on Socket’s report to take down identified threats.

• 
  Full Stack Patriot (@fullStackRebel) reported 46 minutes ago

  If you're all really want to cack your britches... Cloudflare moved a lot of its internal and external IT insecurity s*** to india. If they have even a moderately bad day , a quarter of the internet goes down for hours

• 
  Reza Karegaran (@rezacentral) reported 54 minutes ago

  network solutions is a garbage company: because a domain wasn’t locked they just decided to swap out dns settings and reset it from cloudflare— breaking my FIL’s company website— @netsolcares you guys are literally the worst with the worst website and worst customer hostile service

• 
  miel (@mielchevre67) reported 58 minutes ago

  @kagemaru_dono @real_hotaru The problem is the lazy developers that just uses the default cloudflare protection, not cloudflare