Tor Project Issues Rapid-Response DoS-Defense Fix Amid Sustained DDoS Attack
aillia
99 points
24 comments
November 16, 2026
Related Discussions
Found 5 related stories in 134.9ms across 12,728 title embeddings via pgvector HNSW
- August 27 TCRF DDoS Attack Postmortem panic · 27 pts · September 24, 2026 · 56% similar
- Ubuntu Currently Suffering from Sustained DDoS Attack theanonymousone · 15 pts · October 08, 2026 · 55% similar
- Understanding the recent DDoS attack against Read the Docs davidfischer · 180 pts · September 09, 2026 · 54% similar
- Tor Browser 16.0 acossta · 16 pts · October 29, 2026 · 50% similar
- Three Days in August: What a DDoS Attack Exposed in Our Network nine_ch · 19 pts · September 28, 2026 · 50% similar
Discussion Highlights (6 comments)
blakeashleyjr
DOS are always going to be a cat and mouse game on Tor. Who has an interest in shutting it down? Usually they are directed at specific sites (competitors, etc), but this seems system-wide. Perhaps these are relays caught in the middle of a specific DOS? Tor has made advances in POW challenges and things like that, but this may be even before that is triggered.
cowlevel
I tried to load the release notes for Tor, on Tor's website, through Tor, and received a 403 error because Tor blocks Tor. Not a good sign.
m00dy
I wonder tor is still secure after all the AI take over
noident
Could this be an effort to direct traffic to adversarial relays?
Actor
I started running a non-exit node a few months ago and after a little while it became trusted and became a guard node. Guard nodes seems more important than amiddle node so I was happy to run one I know is legitimate. That makes at least one legitimate guard node for the network. I noticed the attack when my mom said the wi-fi wasn't working well and I checked it out and the download speed was down 99% from normal. And eventually after various other troubleshooting attempts I turned off my mini pc where the relay and other self-hosted services run and the internet speed returned to normal. Yeah I'm not a very adept sys-admin, AI set up all the docker compose stacks for me. I then looked at my relay on the relay search and it said overloaded. So I checked the Tor forum and sure enough others were reporting the same thing. So at first I tried just lowering the bandwidth let through, although I'd thought it should already not be letting that much through. That did not work. So I made it not become a guard node and now it works fine. But I also read something about malicious guards and exits being how Tor users have been compromised before. So it seems important guards are trustworthy. I'm not gonna risk running a guard again (letting my node become a guard) at least for a while until this attack stabilizes.
sikozu
I tried Tor briefly maybe about 10 years ago, only to have a little look around as I was curious, and to be honest I remember the experience was pretty disappointing, websites were slow and lots of resources seemed to be unavailable. Has it changed much at all? I don't really know what most people get up to on Tor admittedly.