Re:Verizon AS701 blocking Tor consensus server tor26 (86.59....
by ocdtrekkie on Wednesday May 16, 2018 @12:33AM
(#17080020)
The reason Cloudflare originally flagged Tor nodes was because 99% of the traffic over them was malicious. Cloudflare cared to make an alternative solution to it, but most presumably would just let a perceived malicious IP remain blocked.
Re:Verizon AS701 blocking Tor consensus server tor26 (86.59....
by GauntletWizard on Tuesday May 15, 2018 @10:21PM
(#17079534)
It's probably a bad DOS protection mechanism, that has either the inbound or outbound net set too wide. Not uncommon, though a PITA and hard to distinguish from censorship (and why botnet blocklists should be public)
Re:Verizon AS701 blocking Tor consensus server tor26 (86.59....
by jiveturkey on Wednesday May 16, 2018 @12:35AM
(#17080030)
bad publicity? i can’t see there being any bad publicity.
otherwise i agree with you. probably not intentional.
Re:Verizon AS701 blocking Tor consensus server tor26 (86.59....
by djsumdog on Tuesday May 15, 2018 @11:45PM
(#17079879)
Hanlon's razor
Re:Verizon AS701 blocking Tor consensus server tor26 (86.59....
by gricardo99 on Wednesday May 16, 2018 @12:00AM
(#17079921)
Grey’s law [1]:
“Any sufficiently advanced incompetence is indistinguishable from malice”
Re:Verizon AS701 blocking Tor consensus server tor26 (86.59....
by MikeTaylor on Thursday May 17, 2018 @09:22AM
(#17091047)
This should be Elsevier's corporate motto.
The tiny percentage of Tor users don't concern Verizon. The miniscule loss of advertising revenue isn't as big of an issue as the bad publicity that messing with TOR would get them from media.
VPN users might be a thing they get concerned about, at some point, but I'd expect them to come out with a VPN service if that was the case.
So I expect this will be traced to some kind of incompetence or error, not a deliberate effort.