I think it doesn't exactly reflect how paths are chosen based on relay bandwidth scores, if we compare to the actual path selection algorithm: http://tor.stackexchange.com/a/114
I might be missing something, but it seems that relay same-family and same-/16-subnet exclusions are ignored. This might bias the visualization to increase the apparent traffic between popular nodes, while in reality, the traffic should be slightly more evened out with less popular nodes. Hard to tell if this effect makes any visible difference without analyzing the data, though. Either way, because of the way the code is structured, it shouldn't be too hard to fix: just simulate full paths instead of single connections between nodes.
Brightest spots in capitals are probably caused by IP geolocation. Whois for many IPs returns main ISP HQ address which usually is based in the capital city. Also, geolocation tools will return capital city if no specific information other than country is available.
I think they could improve they ip2address tool, because I would expect some bright spot at hetzner datacenter and it's not there (while whois for IPs of my servers there returns proper location of the datacenter).
No idea how good the data is, I assume it's good, but in my mind this is impressive just on the visual representation of it alone. What a fantastically beautiful display of information, the UI is great all around!
One suggestion for the UI: when you click a + on an option, the minus should be at the bottom of the expanded option, so that you don't have to move the mouse to close the expansion.
A disproportionate amount of traffic seems to be passing through Monrovia, Liberia compared to the rest of African continent and even more developed places like Australia. Can anybody shed some light on this ?
There are less than 50 relays in Australia and none of them come close to IPredator. Every AU relay combined has a middle probability of 0.0246% and an exit probability of 0.0060%.
IPredator alone has an exit probability of 2.1961%.
IPredator is a Swedish VPN service that appeared when the "Ipred" law was passed in Sweden, a law that was passed to allow rights holders to find and prosecute people who torrent stuff. So most likely, it's used for piracy.
Kansas has some big data centers in it (there's a reason google fiber launched there). Lots of dedicated server and colocation providers are located in Kansas City. In order for these providers to receive IP addresses from ARIN, they must register with ARIN as an "autonomous system" (AS). One of the items on the form they must complete is the geolocation of the IP address block they are being assigned. That geolocation is often the location of the provider company, not necessarily the location of the server(s) the IP(s) point to.
Server providers register as autonomous systems, and purchase IP space in large blocks. They often have servers at multiple data centers, with VLAN routing configured to switch packets at the ingress IP to whichever server that IP is assigned to. When a client rents a server from a provider, the provider assigns the client some number of IP addresses from its available pool. Many times, the provider does not actually SWIP (officially delegate via ARIN) these IP addresses to the client, so the registration with ARIN will not reflect the owner of the server an IP currently points to.
tl;dr When a packet goes to an IP belonging to an AS registered with a certain geolocation, the AS can switch that packet to wherever it wants.
While the other commenters may be correct and seem to know more about this than I, almost every time I've seen stuff geolocate to "Kansas" it's geolocating to the United States, with no further level of detail available. The mapping software finds the geographic center of the United States (which is somewhere in Kansas) and puts it there
anyone else think it is curious that there is hardly any Tor traffic in/out of Seattle? You would think with the high density of tech-types, and proximity to pacific links, that there would at least be something?
I'm wondering if this might because Australia has less traffic per node, so most of the Australian nodes aren't reaching the display threshold (top 500 or whatever nodes).
[+] [-] pierrec|10 years ago|reply
I think it doesn't exactly reflect how paths are chosen based on relay bandwidth scores, if we compare to the actual path selection algorithm: http://tor.stackexchange.com/a/114
I might be missing something, but it seems that relay same-family and same-/16-subnet exclusions are ignored. This might bias the visualization to increase the apparent traffic between popular nodes, while in reality, the traffic should be slightly more evened out with less popular nodes. Hard to tell if this effect makes any visible difference without analyzing the data, though. Either way, because of the way the code is structured, it shouldn't be too hard to fix: just simulate full paths instead of single connections between nodes.
[+] [-] chris-dickson|10 years ago|reply
https://github.com/unchartedsoftware/torflow/issues/4
[+] [-] khgvljhkb|10 years ago|reply
[+] [-] comboy|10 years ago|reply
I think they could improve they ip2address tool, because I would expect some bright spot at hetzner datacenter and it's not there (while whois for IPs of my servers there returns proper location of the datacenter).
Nevertheless, awesome visualization.
[+] [-] stryk|10 years ago|reply
[+] [-] a3n|10 years ago|reply
[+] [-] mih|10 years ago|reply
[+] [-] neerdowell|10 years ago|reply
There are less than 50 relays in Australia and none of them come close to IPredator. Every AU relay combined has a middle probability of 0.0246% and an exit probability of 0.0060%.
IPredator alone has an exit probability of 2.1961%.
(You can see these stats with Tor Compass: https://compass.torproject.org/)
[+] [-] msvan|10 years ago|reply
[+] [-] saosebastiao|10 years ago|reply
[+] [-] ithinkso|10 years ago|reply
[+] [-] rapht|10 years ago|reply
[+] [-] dylz|10 years ago|reply
OVH and Free Telecom probably host a huge amount of Tor traffic in FR. Easily do 300 Mbps 24x7 for sub-$15/m dedicated server.
OVH also has subsidiaries in other EU countries that will geolocate back to those countries (hosted in FR physically).
[+] [-] enedil|10 years ago|reply
[+] [-] Grue3|10 years ago|reply
[+] [-] uxwtf|10 years ago|reply
[+] [-] cmnzs|10 years ago|reply
[+] [-] aphrax|10 years ago|reply
[+] [-] sklivvz1971|10 years ago|reply
[+] [-] cornedor|10 years ago|reply
[+] [-] looki|10 years ago|reply
[+] [-] yk|10 years ago|reply
[+] [-] luchs|10 years ago|reply
[+] [-] niij|10 years ago|reply
[+] [-] aw3c2|10 years ago|reply
[+] [-] detaro|10 years ago|reply
[+] [-] Thriptic|10 years ago|reply
[+] [-] chatmasta|10 years ago|reply
Server providers register as autonomous systems, and purchase IP space in large blocks. They often have servers at multiple data centers, with VLAN routing configured to switch packets at the ingress IP to whichever server that IP is assigned to. When a client rents a server from a provider, the provider assigns the client some number of IP addresses from its available pool. Many times, the provider does not actually SWIP (officially delegate via ARIN) these IP addresses to the client, so the registration with ARIN will not reflect the owner of the server an IP currently points to.
tl;dr When a packet goes to an IP belonging to an AS registered with a certain geolocation, the AS can switch that packet to wherever it wants.
[+] [-] anc84|10 years ago|reply
[+] [-] finnn|10 years ago|reply
[+] [-] incredulousk|10 years ago|reply
[+] [-] emilburzo|10 years ago|reply
[+] [-] awl130|10 years ago|reply
Unnamed Rd, Charleston, SC 29492, USA 32.912336, -79.862333
https://www.google.ca/maps/place/32%C2%B054'44.4%22N+79%C2%B...
[+] [-] jorgecurio|10 years ago|reply
[+] [-] drakenot|10 years ago|reply
[+] [-] jandrese|10 years ago|reply
[+] [-] x1798DE|10 years ago|reply
[+] [-] aw3c2|10 years ago|reply
[+] [-] unknown|10 years ago|reply
[deleted]
[+] [-] pavki|10 years ago|reply
[+] [-] Forbo|10 years ago|reply
[+] [-] lindx|10 years ago|reply
[+] [-] rnhmjoj|10 years ago|reply