Cloudflare 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:

• 
  Ayush Ray (@Aaayush_Ray) reported 5 minutes ago

  Engineering Behind the Internet — Day 11/14 You type a website URL. Your request travels across the internet. But it may never reach the website’s server directly. Instead, a powerful layer called Cloudflare can sit in between—helping protect the server, cache content, block attacks, and speed up responses. But how does Cloudflare handle millions of requests without slowing everything down? Let's break it down. 🧵

• 
  Admire The Web (@AdmireTheWeb) reported 7 minutes ago

  @Cloudflare @MattieTK Customer zero? You mean one?

• 
  Ersin Akyüz (@ersinakyuz) reported 8 minutes ago

  Trying to avoid paying Google Workspace money just to have 30 email aliases. I have 2-3 domains, lots of app/service specific addresses, mostly inbound + occasional replies. Cloudflare Email Routing + Gmail SMTP vs Purelymail ($10/yr). What would you run?

• 
  Net-Updates by StabilityTest (@stabilitystatus) reported 11 minutes ago

  Cloudflare Service Disruption Cloudflare is investigating an issue which may result in latency increases for a subset of requests. Status: Investigating Impact: Minor Updated: 8:38 PM GMT+0000 Service status tracked by @stabilitytestio

• 
  Adithya 🚀 (@adithyashreshti) reported 11 minutes ago

  @jain_harshit Cloudflare. Better management and support, then namecheap.

• 
  Ahmad A.Sabilla (@ahaabsa) reported 15 minutes ago

  @Cloudflare Doest it support rtl ?

• 
  Hannan (@truehannan) reported 18 minutes ago

  @BraydenWilmoth Outerbase is acquired by cloudflare! WHAT? Bro i justed started using it. Btw can u fix the latest build. It failed to deploy on workers and im lazy to figure out for now

• 
  saburo (@suhburo) reported 20 minutes ago

  @Daeshawn @OpenAI @cerebras Dude I ran into this problem when I ran out of usage one month. Blew my mind that you can’t make basic edits manually. I had to stop using it widely after that back to vercel/cloudflare

• 
  Nima (@nimanikroo) reported 25 minutes ago

  @CloudflareHelp @Cloudflare @CloudflareDev who do i talk to about surprised billing that will end me and my startup? I really need help on this one please

• 
  Uroš (@djedlajn) reported 25 minutes ago

  Love that wrangler login --device exists for remote boxes less love that Cloudflare bot challenges its own OAuth requests from a Hetzner VPS. Normal OAuth gets the same 403. Do I really need to reverse-SOCKS-ing through my Mac just to authenticate. @CloudflareDev. Really in 2026?

• 
  Robin Ebers (@robinebers) reported 27 minutes ago

  @0x0kazi @Cloudflare @vercel prime skill issue if you think this is bait

• 
  Matt Mazur (@mhmazur) reported 29 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.

• 
  Web3.0 (@Web3_0_AMATW) reported 31 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?

• 
  Kojo Jeffery (@openclonne) reported 33 minutes ago

  @Temi_Dy @Cloudflare @tursodatabase Love it, no worries I treat that window as durability, not dedup. "Redis Lua" claims the key and caches the original result, so a retry returns the same outcome and never runs twice. The worker is "at-least-once archival" so if it dies I retry the persist, not the request. Redis TTL is the cleanup. The real hole is, Redis loss before drain, so the domain op still has to be replay-safe. Your DB tx is the tighter source of truth; I just don’t want key cleanup on the hot path.

• 
  Ayush ☘️ (@ayushHardeniya) reported 35 minutes ago

  @__Piyushrathore the thing is our current backend is a conventional Go server, while cloudlfare workers is a serverless runtime! while they have a thing called cloudflare containers which is quite close to what we need, but that is a paid service, I'm looking for 0 fee option.