Something really interesting I have learned thru looking up AS and IP providers/vs their physical locations was “Data Center Alley” or the “Dulles Technology Corridor”. This area that includes Ashburn, Virginia (where many of my trace routes hopped to at some point before either going across the US or overseas), is a major data hub for the country, with estimates of up to 50% of America’s internet touching the zone. The roots of this bundle of infrastructure date back to ARPANET in the late 1960’s. From my understanding, arpanet laid the foundations of the structure of the modern internet, and was the first live environment in which IP/TCP was used. Essentially, this was where IP addresses came into play with networking in the modern way we still use them. It also allowed arpanet to connect to other university-based networks all over the country.
I find the concept of a physical internet zone especially interesting in the context of the On Distributed Communications essay reading this week. Within the grid diagrams of distributed networks, every node has even spacing, yet the existence of the Dulles Technology Corridor implies the opposite of that. While I do understand that this is not the only significant internet related internet hotspot within the united states (or the world, for that matter), the thought that some type of catastrophic event could knock huge amounts of our network grid offline is not comforting. This also made me think about last week’s reading about Google going offline, and how the wrong links off the nodes of a grid can effectively spread and poison a network.
Here are a few of the Traceroutes I performed this week. Out of 8 different sites I tried out, only two them actually finished, the rest timed out. Is this normal?
Bikepacking.com - Website I use to get off road trail routes for trips
1 cr1000a.mynetworksettings.com (192.168.1.1) 4.157 ms 3.690 ms 3.928 ms
- home router
2 lo0-100.nycmny-vfttp-395.verizon-gni.net (100.33.69.1) 7.235 ms 22.415 ms 9.060 ms
3 100.41.35.186 (100.41.35.186) 7.456 ms
100.41.35.172 (100.41.35.172) 5.203 ms 7.893 ms
- these three all ended up being NYC based Verizon owned IP's
4 * * *
5 customer.alter.net (63.125.121.2) 6.551 ms
- slightly upstate but still Verizon owned
209.85.149.208 (209.85.149.208) 5.452 ms 6.602 ms
- google owned back to NYC
6 53.36.231.35.bc.googleusercontent.com (35.231.36.53) 29.953 ms 28.945 ms 26.690 ms
- first one is owned by Mercedes Benz and based in Germany but the second IP is the correct google-owned one in North Carolina. My best bet from some research is that Mercedes owns a range of IP’s from google’s services and this one is pretty close to the addresses so the IP info lookup is wrongly attributing it to a Germany location. The mapping tool had no problem deciphering the correct location from the second IP address in the parentheses.

mjt.org - The Museum of Jurassic Technology in Los Angeles, one of my favorite museums in LA and a really fun website I send a lot of people to
1 cr1000a.mynetworksettings.com (192.168.1.1) 6.396 ms 3.077 ms 2.815 ms
2 lo0-100.nycmny-vfttp-395.verizon-gni.net (100.33.69.1) 5.116 ms 8.456 ms 5.349 ms
3 100.41.35.186 (100.41.35.186) 7.398 ms 6.496 ms
100.41.35.174 (100.41.35.174) 6.479 ms
Timed out afterwards, unfortunately.
11 * * *

vasamuseet.se - Vasa museum, Stockholm Sweden, great museum, not really used in my everyday life but I wanted something far away to traceroute
1 cr1000a.mynetworksettings.com (192.168.1.1) 5.148 ms 2.962 ms 2.636 ms
2 lo0-100.nycmny-vfttp-395.verizon-gni.net (100.33.69.1) 3.566 ms 5.099 ms 6.084 ms
3 100.41.35.186 (100.41.35.186) 7.242 ms
100.41.35.172 (100.41.35.172) 9.547 ms 7.437 ms
- home router, then Verizon networks local to nyc
4 * * *
5 * * ewr-b13-link.ip.twelve99.net (80.239.192.36) 11.840 ms
- Arelion Sweden AB owned based out of NYC by location. Interesting message pops up on IPinfo "Other providers place this IP in Hanover, Lower Saxony, DE, 6,112.3 kms away from its actual location. We're confident we have it right"
6 nyk-bb5-link.ip.twelve99.net (62.115.135.160) 8.318 ms 8.716 ms 8.919 ms
- owned by Arelion, based in Newburgh NY
7 rest-bb1-link.ip.twelve99.net (62.115.139.35) 14.583 ms
- Arelion, Ashburn Virginia
ash-bb2-link.ip.twelve99.net (62.115.136.201) 11.381 ms 65.870 ms
- same as above
8 * ash-b2-link.ip.twelve99.net (62.115.123.123) 14.698 ms
ash-b2-link.ip.twelve99.net (62.115.123.125) 14.393 ms
- same as above
9 nordunet-ic-309102.ip.twelve99-cust.net (213.248.85.174) 15.305 ms 16.184 ms 12.316 ms
- same as above
10 us-man2.nordu.net (109.105.97.142) 21.892 ms 23.236 ms 107.560 ms
- NORDUnet Core Backbone, NYC
11 nl-ams.nordu.net (109.105.97.65) 93.874 ms 97.982 ms 110.056 ms
- Nordu, Amsterdam
12 dk-esbj.nordu.net (109.105.97.74) 110.968 ms 107.402 ms 106.356 ms
-Nordu, Copenhagen
13 dk-bal3.nordu.net (109.105.97.2) 96.360 ms 96.960 ms 100.525 ms
- same as above
14 lnd88-r11.sunet.se (109.105.102.67) 99.383 ms 101.818 ms 162.915 ms
- same as above
15 vaxjo-vxj-r11.sunet.se (86.104.202.109) 101.784 ms 103.900 ms 99.231 ms
- Vetenskapsradet / SUNET, Växjö, Sweden
16 jonkoping-jkg-r11.sunet.se (86.104.202.54) 103.281 ms 104.417 ms 104.471 ms
- Vetenskapsradet / SUNET, Jönköping, Sweden
17 linkoping-lin3-r11.sunet.se (86.104.202.57) 104.847 ms 106.993 ms 107.400 ms
- Vetenskapsradet / SUNET, Linköping, Sweden
18 norrkoping-nkg188-r11.sunet.se (86.104.202.97) 107.326 ms 106.691 ms 168.094 ms
- Vetenskapsradet / SUNET, Stockholm, Sweden
19 stockholm-tug-r12.sunet.se (86.104.203.67) 107.399 ms 106.237 ms 106.966 ms
- same as above
20 stockholm-tug-r14.sunet.se (86.104.203.35) 186.813 ms 108.520 ms 107.333 ms
- same as above
21 maritima-tug.sunet.se (130.242.60.98) 106.589 ms 106.672 ms 120.310 ms
- same as above
Timed out afterwards
