Understanding Networks — Professor Tom Igoe

Trace Route Analysis

The way you learn the geography of the internet is to ask your neighbor about their neighbour — lets you know what machines sit between us and our virtual host. Discoveres a forward path by sending packets with increasing TTL values. Asterisk means the thng didnt answer. Paths can be asymetric.

Rough Guides

5 ms - Same metro
10-90 ms - same country
80-150 ms transoceanic
150 ms + something is off

What a network hop is

A hop is one router or layer-3 device along the path. Your packets cross many hops between a home or office network and a cloud instance.

Your PC -- hop 1 (edge router) -- hop 2 (ISP) -- hop 3 (backbone) -- ... -- target

Each hop decrements the IP TTL. When TTL reaches zero, the device is supposed to return an ICMP time exceeded message, which is what classic traceroute uses to discover that hop.

Types of Traces

ICMP Resembles ping some networks treat ICMP differnet than TCP or UDP
UDP Common default for traceroute implemenetations
TCP used for tcptraceroute or mtr -T can get past filtering on ICMP and UDP

Limitations

Firewalls, will produce asterisk
Asymetrical loading
local balancers and anycast

Trace route 1: Google.com

traceroute to google.com (142.251.45.78), 64 hops max, 40 byte packets

 1  192.168.1.1 (192.168.1.1)  3.190 ms  6.400 ms  2.725 ms

 2  10.96.46.129 (10.96.46.129)  3.238 ms  3.130 ms  3.509 ms

 3  10.69.50.14 (10.69.50.14)  17.541 ms  11.453 ms  31.032 ms

 4  wave-saratoga.mesh (10.70.253.160)  14.415 ms  20.977 ms  16.467 ms

 5  liteap-vernon.mesh (10.70.253.26)  52.084 ms  27.314 ms  48.189 ms

 6  eh8010-sslope.mesh (10.70.253.4)  40.192 ms  47.210 ms  22.742 ms

 7  eh8010-sn3.mesh (10.70.253.111)  34.645 ms  40.722 ms  45.596 ms

 8  10.70.89.131 (10.70.89.131)  16.477 ms  20.100 ms  15.999 ms

 9  ar01.jfk09.pilotfiber.net (142.154.197.1)  17.935 ms  17.348 ms  14.998 ms

10  et-0-0-49.ar01.jfk09.pilotfiber.net (104.129.141.102)  42.743 ms  32.453 ms  13.820 ms

11  et-0-1-3.cr01.r16.jfk00.pilotfiber.net (192.81.138.166)  18.107 ms  99.650 ms  18.990 ms

12  br01.jfk05.pilotfiber.net (192.81.139.197)  27.107 ms  15.136 ms  9.286 ms

13  142.250.175.94 (142.250.175.94)  17.596 ms  38.900 ms  22.330 ms

14  dfw25s48-in-f14.1e100.net (142.251.45.78)  30.999 ms  11.146 ms  17.151 ms

this is me
1 192.168.1.1 (192.168.1.1) 3.190 ms 6.400 ms 2.725 ms

this is my NYC mesh router on my roof
2 10.96.46.129 (10.96.46.129) 3.238 ms 3.130 ms 3.509 ms

NYC Mesh router on the roof, hop 2 of the trace

This is Eldert, a NYC Mesh Station
3 10.69.50.14 (10.69.50.14) 17.541 ms 11.453 ms 31.032 ms

Eldert NYC Mesh station, hop 3 of the trace

Now Saratoga
4 wave-saratoga.mesh (10.70.253.160) 14.415 ms 20.977 ms 16.467 ms

Getting larger now here to Vernon
5 liteap-vernon.mesh (10.70.253.26) 52.084 ms 27.314 ms 48.189 ms

There are two ways it could go here, to downtown or to park slope, Im pretty sure this is park slope becuase it says sslope
6 eh8010-sslope.mesh (10.70.253.4) 40.192 ms 47.210 ms 22.742 ms

Now to my knowledge we should be home free down the big tube SuperNode3
7 eh8010-sn3.mesh (10.70.253.111) 34.645 ms 40.722 ms 45.596 ms

eh8010-sn3.mesh SuperNode3, hop 7 of the trace

And then out into the borader internet at large

The Bogon

8 10.70.89.131 (10.70.89.131) 16.477 ms 20.100 ms 15.999 ms
this is what I get at this site, I dont understand it but maybe its some super users terminal?

admin is not the password, I checked.
it says its this, a private IP address LAN, its weird because its after the super node in nyc and super public

great, another fucking bogon. I dont get what this is still

Search results for the bogon IP at hop 8

basically a false address, someone might have given it pretending its public or it could be an address they know is not in use. sometimes in order to attack a particular network try to spoof as one of its special IPs. someone is trying to attack me, but they want to hide who they are, so they try to get me to send out a package to a fake server that they can sniff it out.

I dont think theyre trying to attack me here, because its a public search. Google also says it's a private IPV for address defined by RFC 1918. Internal communication, not readable on the public Internet shared globally I don't understand. oh well, onto the next

public baby

9 ar01.jfk09.pilotfiber.net (142.154.197.1) 17.935 ms 17.348 ms 14.998 ms

ar01.jfk09.pilotfiber.net lookup, hop 9 of the trace

Apparently this is come kind of flexible IP address because a lot of numbers go to it. It manages the NYC area and has many associated numbers.

Upstreams

to -

AS6762 - Telecom Italia Sparkle (Seabone)
AS3356 - Lumen (Level 3)
AS2914 - NTT America, Inc.
AS3257 - GTT Communications Inc.
AS174 - Cogent Communications, LLC
AS1299 - Arelion (fka. Telia Carrier)

Who is

on this page it says

NetHandle:      NET-192-81-136-0-1
OrgID:          PF-176
Parent:         NET-192-0-0-0-0
NetName:        PF-176
NetRange:       192.81.136.0 - 192.81.139.255
NetType:        allocation
RegDate:        2023-07-21
Updated:        2023-07-21
Source:         ARIN



OrgID:          PF-176
OrgName:        Pilot Fiber, Inc.
CanAllocate:
Street:         1115 Broadway
Street:         Floor 12
City:           New York
State/Prov:     NY
Country:        US
PostalCode:     10010
Comment:        Pilot Network Operations
Comment:        NOC Phone: 855-578-5500
Comment:        NOC Email: noc@pilotfiber.com
Comment:        Website: pilotfiber.com
Comment:        Normal business hours are M-F 9A-6P EST, Network Operations Center is reachable for network related incidents 24/7.
RegDate:        2014-05-22
Updated:        2022-12-19
OrgAdminHandle: NETWO6963-ARIN
OrgTechHandle:  NETWO6963-ARIN
OrgAbuseHandle: ABUSE7999-ARIN
OrgNOCHandle:   NETWO6963-ARIN
Source:         ARIN

but crutially it says its in New York on 115 Broadway and the source is ARIN. I dont understand why the IP we used to get here is different from the range they have soecified.
NetRange: 192.81.136.0 - 192.81.139.255
vs
ar01.jfk09.pilotfiber.net (142.154.197.1)

this jump took 15ms, so we left the port out of nyc to go back to nyc, right into the heart of silicone alley.

There are offices avalible should I want to rub shoulders. Pilot Fiber has offices here

WHO IS ARIN

They say my address is 199.170.132.192, so that must be hop 0 on my computer.

More Pilot Fiber

10  et-0-0-49.ar01.jfk09.pilotfiber.net (104.129.141.102)  42.743 ms  32.453 ms  13.820 ms
11  et-0-1-3.cr01.r16.jfk00.pilotfiber.net (192.81.138.166)  18.107 ms  99.650 ms  18.990 ms
12  br01.jfk05.pilotfiber.net (192.81.139.197)  27.107 ms  15.136 ms  9.286 ms

GOOGLE LLC, WE MADE IT TO GOOGLE

13  142.250.175.94 (142.250.175.94)  17.596 ms  38.900 ms  22.330 ms

letch check the map of the internet

I dont see any 64 in this IP address

looks more like way out here in various registers.

This is another google page

14  dfw25s48-in-f14.1e100.net (142.251.45.78)  30.999 ms  11.146 ms  17.151 ms

I get a google 404 when I try to just go to it, so I think this is it. Google.com. Or some local hydronic head of it in the nyc area. that being said, its 30.99 ms away, so maybe its in chicago or ohio or something where they can put big datacenters.

Claude Says:
Path shape: you're on Pilot Fiber in the NYC metro, handing off to Google. ar → access/aggregation router, cr → core, br → border — so hops 9–12 are the textbook walk outward through Pilot's own network, then hop 13 is Google's edge. Three network boundaries, 14 hops to destination. That's short.

Trace Route 2: My EC2 instance

I scrolled up in my command until I found

ssh -i "UndNet.pem" ubuntu@ec2-18-219-105-90.us-east-2.compute.amazonaws.com

So lets try a trace route to some of that stuff

I got this

Last login: Tue Sep 15 15:23:28 2026 from 216.165.95.141

ubuntu@ip-172-31-41-114:~$

So now I have three IP like things to contend with GAH. Lets try them out

ubuntu@ec2-18-219-105-90

codyfrost@CMB ~ % traceroute 2-18-219-105-90
traceroute: unknown host 2-18-219-105-90

Not an ip address.

private IP address 172-31-41-114

codyfrost@CMB ~ % traceroute 172-31-41-114
traceroute: unknown host 172-31-41-114

Nore for this, its a private ip address inside amazons servers. this seems to be typical for 172 according to

RFC 1918, 172.16.0.0/12 (172.16.0.0–172.31.255.255).

according to ARIN
https://www.arin.net/reference/research/statistics/address_filters/

According to standards set forth in Internet Engineering Task Force (IETF) document RFC-1918, the following IPv4 address ranges are reserved by the IANA for private internets, and are _not_ publicly routable on the global internet:

- 10.0.0.0/8 IP addresses: 10.0.0.0 – 10.255.255.255
- 172.16.0.0/12 IP addresses: 172.16.0.0 – 172.31.255.255
- 192.168.0.0/16 IP addresses: 192.168.0.0 – 192.168.255.255

from 216.165.95.141

This must be NYU because its taking forever to reconnect. We see the same pattern from before and then timeout at 64 hops. Except this time, we took 5 hops through pilot fiber.

ar to ar to br cr to br to edge of new york and then to Lumen Technologies afterwhich the NYU network must make it go dark

A big difference here is for google I go straight to 142.250.175.94 which is a google server which puts me to google.com where as with this trace I go to edge of new york first.

I am curious about this pattern.
ar to ar to br to cr to br
ar → access/aggregation router, cr → core, br → border

traceroute to 216.165.95.141 (216.165.95.141), 64 hops max, 40 byte packets

 1  192.168.1.1 (192.168.1.1)  4.066 ms  5.102 ms  3.236 ms

 2  10.96.46.129 (10.96.46.129)  3.196 ms  3.444 ms  5.796 ms

 3  10.69.50.14 (10.69.50.14)  40.360 ms  29.669 ms  12.278 ms

 4  wave-saratoga.mesh (10.70.253.160)  40.621 ms  26.882 ms  43.134 ms

 5  liteap-vernon.mesh (10.70.253.26)  39.853 ms  38.446 ms  30.649 ms

 6  eh8010-sslope.mesh (10.70.253.4)  22.551 ms  17.652 ms  30.046 ms

 7  eh8010-sn3.mesh (10.70.253.111)  36.138 ms  23.558 ms  11.713 ms

 8  10.70.89.131 (10.70.89.131)  43.254 ms  21.271 ms  20.776 ms

 9  ar01.jfk09.pilotfiber.net (142.154.197.1)  15.399 ms  21.561 ms  56.935 ms

10  et-0-0-49.ar01.jfk09.pilotfiber.net (104.129.141.102)  26.716 ms  38.973 ms  39.084 ms

11  et-2-1-0.br01.jfk07.pilotfiber.net (104.129.140.236)  30.973 ms

    et-0-1-3.cr01.r16.jfk00.pilotfiber.net (192.81.138.166)  21.663 ms  18.543 ms

12  br01.jfk05.pilotfiber.net (192.81.139.197)  21.434 ms  125.610 ms  27.140 ms

13  et-7-0-10.edge2.newyork6.level3.net (64.152.165.233)  28.546 ms  34.495 ms  91.501 ms

14  4.30.244.202 (4.30.244.202)  19.702 ms  21.250 ms  21.566 ms

15  * * *
16  * * *
…50 more hops of * * *, silence through hop 64

Claudes analysis agrees with me

Traceroute comparison — Google vs. NYU NAT pool

Two traces, same machine, minutes apart.

Shared path

Hops 1–10 are topologically identical in both — same rooftop mesh, same Pilot Fiber. First mile is a controlled variable; all differences are downstream.

1 192.168.1.1 home router
2–3 mesh internal (10.96.x, 10.69.x)
4 wave-saratoga Ubiquiti Wave 60 GHz
5 liteap-vernon Ubiquiti LiteAP 5 GHz
6–7 eh8010-* Siklu EtherHaul 80 GHz
8–10 handoff → ar01.jfk09.pilotfiber.net

Looks like NYC Mesh → Pilot Fiber.

Divergence

	→ google.com	→ 216.165.95.141
Hop 11	`cr01.jfk00` only	two routers answer — ECMP
Hop 13	Google, direct peering	`edge2.newyork6.level3.net`
Hop 14	destination, 11.1 ms	still in Level3 `4.0.0.0/8`
Result	completed, 14 hops	50 hops of `* * *`

Same city, two classes of interconnect: settlement-free peering vs. Level3 transit.

Why NYU never finishes

PTR is 216-165-95-141.natpool.nyu.edu — a NAT egress address, the IP NYU traffic appears from. No inbound listener by design, so silence is expected, not failure. Confirmed: ping 100% loss; TCP 443/80 timeout with no RST — silence, not refusal. Border filtering may compound it; NAT alone explains it.

Trace Route 3: From my EC2 to Me

So I had to install traceroute on my EC2

ubuntu@ip-172-31-41-114:~$ traceroute 192.168.1.1

traceroute to 192.168.1.1 (192.168.1.1), 30 hops max, 60 byte packets

 1  100.64.89.91 (100.64.89.91)  102.913 ms 100.64.80.19 (100.64.80.19)  121.032 ms 100.64.89.101 (100.64.89.101)  64.356 ms

 2  * * *
 3  * * *
…29 more hops of * * *, silence through hop 30

I got 30 jumps which the routers didnt even care enough to respond.

1 100.64.89.91 (100.64.89.91) 102.913 ms 100.64.80.19 (100.64.80.19) 121.032 ms 100.64.89.101 (100.64.89.101) 64.356 ms

All three are

NetName: SHARED-ADDRESS-SPACE-RFC6598-IANA-RESERVED

from whois.arin.net

So, everyone hates my little ec2 instance.

Traceroute 4: Craiglist.com

traceroute to craiglist.com (208.82.237.135), 64 hops max, 40 byte packets
 1  192.168.1.1 (192.168.1.1)  4.497 ms  2.882 ms  2.567 ms
 2  10.96.46.129 (10.96.46.129)  3.198 ms  75.687 ms  3.571 ms
 3  10.69.50.14 (10.69.50.14)  17.135 ms  105.552 ms  13.253 ms
 4  wave-saratoga.mesh (10.70.253.160)  25.544 ms  9.195 ms  9.726 ms
 5  liteap-vernon.mesh (10.70.253.26)  25.327 ms  21.102 ms  44.394 ms
 6  eh8010-sslope.mesh (10.70.253.4)  19.796 ms  23.400 ms  55.654 ms
 7  eh8010-sn3.mesh (10.70.253.111)  21.432 ms  29.057 ms  40.649 ms
 8  10.70.89.131 (10.70.89.131)  23.769 ms  15.726 ms  12.981 ms
 9  ar01.jfk09.pilotfiber.net (142.154.197.1)  32.489 ms  26.067 ms  31.130 ms
10  et-0-0-49.ar01.jfk09.pilotfiber.net (104.129.141.102)  83.394 ms  23.608 ms  13.942 ms
11  et-2-1-0.br01.jfk07.pilotfiber.net (104.129.140.236)  23.375 ms  22.788 ms  15.240 ms
12  br01.jfk05.pilotfiber.net (192.81.139.197)  18.864 ms  28.668 ms  21.159 ms
13  * * *
14  be3495.ccr41.jfk02.atlas.cogentco.com (66.28.4.181)  54.490 ms  48.183 ms
    be3496.ccr42.jfk02.atlas.cogentco.com (154.54.0.141)  20.469 ms
15  port-channel4188.ccr92.dca04.atlas.cogentco.com (154.54.30.121)  21.258 ms
    port-channel8073.ccr91.dca04.atlas.cogentco.com (154.54.170.69)  30.495 ms
    port-channel4188.ccr92.dca04.atlas.cogentco.com (154.54.30.121)  25.325 ms
16  be8413.ccr41.iad02.atlas.cogentco.com (154.54.5.218)  60.542 ms
    be3025.ccr42.iad02.atlas.cogentco.com (154.54.28.30)  38.609 ms
    be8481.ccr42.iad02.atlas.cogentco.com (154.54.25.18
17  hu0-0-0-37.rcr61.b023612-0.iad02.atlas.cogentco.com (154.54.95.41)  41.418 ms

    hu0-0-0-10.rcr61.b023612-0.iad02.atlas.cogentco.com (154.54.95.37)  47.877 ms

    hu0-0-0-37.rcr61.b023612-0.iad02.atlas.cogentco.com (154.54.95.41)  24.168 ms

18  mail.responsiveds.com (38.104.56.106)  67.431 ms  25.535 ms  48.668 ms

19  nonorg.craigslist.org (208.82.237.135)  38.377 ms * *

Ar-Ar-br- to a whole new set of IP's this time, this time to cogentco.com who drop it off to mail.responsiveds also cogentco apparently and then finally craiglist

Field	Value
OrgName	Cogent Communications, LLC
OrgId	COGC
Address	2450 N Street NW
City	Washington
State	DC
Postal	20037
Country	US
RegDate	2000-05-30
Updated	2025-09-23

Traceroute 5: spotify.com

traceroute to spotify.com (35.186.224.24), 64 hops max, 40 byte packets

 1  192.168.1.1 (192.168.1.1)  5.481 ms  2.927 ms  2.683 ms

 2  10.96.46.129 (10.96.46.129)  3.542 ms  6.176 ms  3.267 ms

 3  10.69.50.14 (10.69.50.14)  47.295 ms  29.577 ms  54.626 ms

 4  wave-saratoga.mesh (10.70.253.160)  48.710 ms  13.626 ms  16.289 ms

 5  liteap-vernon.mesh (10.70.253.26)  11.370 ms  26.750 ms  30.731 ms

 6  eh8010-sslope.mesh (10.70.253.4)  24.137 ms  12.319 ms  17.816 ms

 7  eh8010-sn3.mesh (10.70.253.111)  46.771 ms  21.418 ms  12.514 ms

 8  10.70.89.131 (10.70.89.131)  18.975 ms  46.305 ms  101.639 ms

 9  ar01.jfk09.pilotfiber.net (142.154.197.1)  28.597 ms  25.716 ms  49.868 ms

10  et-0-0-49.ar01.jfk09.pilotfiber.net (104.129.141.102)  19.083 ms  19.459 ms  14.426 ms

11  et-2-1-0.br01.jfk07.pilotfiber.net (104.129.140.236)  57.420 ms  76.583 ms

    et-0-1-3.cr01.r16.jfk00.pilotfiber.net (192.81.138.166)  48.246 ms

12  br01.jfk05.pilotfiber.net (192.81.139.197)  27.566 ms  80.060 ms  29.067 ms

13  142.250.175.94 (142.250.175.94)  19.256 ms  25.003 ms  20.471 ms

14  24.224.186.35.bc.googleusercontent.com (35.186.224.24)  29.864 ms  14.607 ms  16.360 ms

ar ar br cr combo again till 142.250.175.94 who is who but Google LLC who apparently owns 142 outright

Field	Value
NetRange	142.250.0.0 – 142.251.255.255
CIDR	142.250.0.0/15
NetName	GOOGLE
NetHandle	NET-142-250-0-0-1
Parent	NET142 (NET-142-0-0-0-0)
NetType	Direct Allocation
Organization	Google LLC (GOGL)
RegDate	2012-05-24
Updated	2012-05-24

Traceroute 6: Instagram.com

codyfrost@CMB ~ % traceroute instagram.com

traceroute to instagram.com (157.240.241.174), 64 hops max, 40 byte packets

 1  192.168.1.1 (192.168.1.1)  3.387 ms  28.113 ms  5.365 ms

 2  10.96.46.129 (10.96.46.129)  12.395 ms  3.295 ms  47.509 ms

 3  10.69.50.14 (10.69.50.14)  18.713 ms  10.523 ms  49.479 ms

 4  wave-saratoga.mesh (10.70.253.160)  12.691 ms  96.892 ms  10.076 ms

 5  liteap-vernon.mesh (10.70.253.26)  14.833 ms  34.384 ms  22.957 ms

 6  eh8010-sslope.mesh (10.70.253.4)  17.013 ms  65.975 ms  41.142 ms

 7  eh8010-sn3.mesh (10.70.253.111)  41.286 ms  42.132 ms  16.380 ms

 8  10.70.89.131 (10.70.89.131)  84.332 ms  17.398 ms  34.408 ms

 9  ar01.jfk09.pilotfiber.net (142.154.197.1)  30.595 ms  67.751 ms  17.708 ms

10  et-0-0-49.ar01.jfk09.pilotfiber.net (104.129.141.102)  44.623 ms  30.641 ms  78.373 ms

11  et-0-1-3.cr01.r16.jfk00.pilotfiber.net (192.81.138.166)  153.506 ms  24.468 ms

    et-2-1-0.br01.jfk07.pilotfiber.net (104.129.140.236)  53.252 ms

12  br01.jfk05.pilotfiber.net (192.81.139.197)  17.885 ms  20.888 ms  37.585 ms

13  198.32.160.51 (198.32.160.51)  48.439 ms

    ae3.pr03.lga1.tfbnw.net (198.32.160.184)  16.238 ms

    de-cix.nyc.fb.com (206.82.104.136)  35.565 ms

14  po4009.asw04.lga1.tfbnw.net (147.75.218.176)  68.758 ms

    po4000.asw03.lga1.tfbnw.net (147.75.211.164)  17.374 ms

    po4009.asw01.lga1.tfbnw.net (129.134.110.122)  29.720 ms

15  usw01.lga3.tfbnw.net (204.15.21.96)  40.123 ms

    usw02.lga3.tfbnw.net (129.134.62.112)  15.995 ms  38.651 ms

16  msw1ar.02.lga3.tfbnw.net (129.134.80.48)  20.526 ms

    163.77.189.17 (163.77.189.17)  25.265 ms

    msw1aq.02.lga3.tfbnw.net (129.134.80.49)  19.978 ms

17  * * *
…48 more hops of * * *, silence through hop 64

good old pilot fiber all the way until 13-16.

at 13 it takes three, for redundency, we made it here to tfbnw (the facebook network)

Something in staton island:		198.32.160.51 (198.32.160.51)  48.439 ms
Again:	    ae3.pr03.lga1.tfbnw.net (198.32.160.184)  16.238 ms
and de-cix in midtown:	    de-cix.nyc.fb.com (206.82.104.136)  35.565 ms

LGA is the quickest here so we take that, I think its hosted in staton island, or registered there? not sure.

14 Deeper into facebook

14  po4009.asw04.lga1.tfbnw.net (147.75.218.176)  68.758 ms

    po4000.asw03.lga1.tfbnw.net (147.75.211.164)  17.374 ms

    po4009.asw01.lga1.tfbnw.net (129.134.110.122)  29.720 ms

So Metas IP addresses are 147 and 129, both in the wasteland.

129 is registered to facebook Inc in calafornia

147 goes through RIPE to facebook israel

claude notes this is because of 30 years of aquisitians grabing IP's

All three are physically located in NYC, but 147.75.21.64 is quickets, so there we go

15 back to LGA

15  usw01.lga3.tfbnw.net (204.15.21.96)  40.123 ms

    usw02.lga3.tfbnw.net (129.134.62.112)  15.995 ms  38.651 ms

15 we have two choices usw01 or usw02, this is apparently in another building, iga3, this is claudes take

16

16  msw1ar.02.lga3.tfbnw.net (129.134.80.48)  20.526 ms

    163.77.189.17 (163.77.189.17)  25.265 ms

    msw1aq.02.lga3.tfbnw.net (129.134.80.49)  19.978 ms

again in lga3, different header msw1ar.

thank god it ends here because im over my head.

Trace Route 7 Claude.ai

traceroute to claude.ai (160.79.104.10), 64 hops max, 40 byte packets

 1  192.168.1.1 (192.168.1.1)  32.262 ms  2.812 ms  2.890 ms

 2  10.96.46.129 (10.96.46.129)  3.376 ms  3.429 ms  9.095 ms

 3  10.69.50.14 (10.69.50.14)  23.712 ms  16.009 ms  70.921 ms

 4  wave-saratoga.mesh (10.70.253.160)  24.821 ms  36.723 ms  40.021 ms

 5  liteap-vernon.mesh (10.70.253.26)  32.018 ms  11.932 ms  15.445 ms

 6  eh8010-sslope.mesh (10.70.253.4)  54.205 ms  14.936 ms  79.495 ms

 7  eh8010-sn3.mesh (10.70.253.111)  32.313 ms  46.260 ms  17.352 ms

 8  10.70.89.131 (10.70.89.131)  16.725 ms  18.767 ms  18.757 ms

 9  ar01.jfk09.pilotfiber.net (142.154.197.1)  46.183 ms  25.816 ms  20.509 ms

10  et-0-0-49.ar01.jfk09.pilotfiber.net (104.129.141.102)  17.037 ms  41.271 ms  20.105 ms

11  et-2-1-0.br01.jfk07.pilotfiber.net (104.129.140.236)  31.020 ms  26.102 ms  15.341 ms

12  br01.jfk05.pilotfiber.net (192.81.139.197)  31.362 ms  112.306 ms  38.739 ms

13  * 162.158.61.34 (162.158.61.34)  44.722 ms  42.365 ms

14  162.158.61.127 (162.158.61.127)  16.080 ms  95.585 ms

    162.158.61.111 (162.158.61.111)  20.675 ms

15  160.79.104.10 (160.79.104.10)  31.143 ms  20.831 ms  22.645 ms

Easy again through 14 and then weirder. Unlike facebook this ones all numbers. Less paralleling.

Now its ar - ar br br, weird

13,14 is cloudflair

15 is Anthropic

I wonder if they have less they need to serve and can get away with less IP's or, why does facebook alternatively have so many?

Traceroute 8 CCFrost.com

codyfrost@CMB ~ % traceroute ccfrost.com

traceroute: Warning: ccfrost.com has multiple addresses; using 18.165.9.44

traceroute to ccfrost.com (18.165.9.44), 64 hops max, 40 byte packets

 1  192.168.1.1 (192.168.1.1)  5.546 ms  8.273 ms  2.659 ms

 2  10.96.46.129 (10.96.46.129)  3.022 ms  9.393 ms  2.553 ms

 3  10.69.50.14 (10.69.50.14)  84.039 ms  68.576 ms  61.836 ms

 4  wave-saratoga.mesh (10.70.253.160)  108.249 ms  134.788 ms  29.663 ms

 5  liteap-vernon.mesh (10.70.253.26)  12.980 ms  24.101 ms  137.918 ms

 6  eh8010-sslope.mesh (10.70.253.4)  111.472 ms  18.589 ms  19.680 ms

 7  eh8010-sn3.mesh (10.70.253.111)  84.719 ms  35.581 ms  55.325 ms

 8  10.70.89.131 (10.70.89.131)  37.013 ms  22.283 ms  29.696 ms

 9  ar01.jfk09.pilotfiber.net (142.154.197.1)  14.179 ms  24.091 ms  18.557 ms

10  et-0-0-49.ar01.jfk09.pilotfiber.net (104.129.141.102)  31.414 ms  51.019 ms  18.308 ms

11  et-0-1-3.cr01.r16.jfk00.pilotfiber.net (192.81.138.166)  36.259 ms  108.380 ms  14.088 ms

12  cr01.ewr01.pilotfiber.net (192.81.139.204)  63.469 ms  25.688 ms  109.858 ms

13  * * *

14  ae-9.a01.nwrknj03.us.bb.gin.ntt.net (168.143.191.162)  30.672 ms  106.927 ms  34.191 ms

15  * * *

16  * * *

17  ae-17.a05.asbnva02.us.bb.gin.ntt.net (129.250.5.7)  34.695 ms

    ae-1.a04.asbnva02.us.bb.gin.ntt.net (129.250.2.125)  21.774 ms  49.695 ms

18  * * *

19  * * *

20  * * *

21  * * *

22  * * *

23  * * *

24  15.230.248.1 (15.230.248.1)  53.174 ms  41.662 ms  42.065 ms

25  * * *

26  * * *

27  * * *

this one times out as well. My insight here is that it gets to AWS on step 24 which is where my site is hosted via amplify. I know for a fact my server is in ohio, but I might have set it up on multiple hosting. IDK

Traceroute 9: Amazon.com

traceroute amazon.com

traceroute: Warning: amazon.com has multiple addresses; using 98.87.170.71

traceroute to amazon.com (98.87.170.71), 64 hops max, 40 byte packets

 1  192.168.1.1 (192.168.1.1)  3.009 ms  3.236 ms  2.824 ms

 2  10.96.46.129 (10.96.46.129)  3.353 ms  3.358 ms  6.077 ms

 3  10.69.50.14 (10.69.50.14)  22.524 ms  34.244 ms  13.220 ms

 4  wave-saratoga.mesh (10.70.253.160)  10.248 ms  58.938 ms  12.790 ms

 5  liteap-vernon.mesh (10.70.253.26)  11.540 ms  13.064 ms  11.267 ms

 6  eh8010-sslope.mesh (10.70.253.4)  17.023 ms  21.612 ms  11.393 ms

 7  eh8010-sn3.mesh (10.70.253.111)  25.119 ms  15.366 ms  21.981 ms

 8  10.70.89.131 (10.70.89.131)  39.789 ms  18.230 ms  16.922 ms

 9  ar01.jfk09.pilotfiber.net (142.154.197.1)  11.465 ms  33.530 ms  21.664 ms

10  et-0-0-49.ar01.jfk09.pilotfiber.net (104.129.141.102)  18.394 ms  19.363 ms  17.367 ms

11  et-0-1-3.cr01.r16.jfk00.pilotfiber.net (192.81.138.166)  20.294 ms  43.532 ms  166.128 ms

12  cr01.ewr01.pilotfiber.net (192.81.139.204)  49.998 ms  22.554 ms  14.464 ms

13  * * *
14  * * *
…19 more hops of * * *, silence through hop 31

this also timed out, not very interesting

Traceroute 10: NYU.EDU

codyfrost@CMB ~ % traceroute nyu.edu

traceroute to nyu.edu (216.165.61.24), 64 hops max, 40 byte packets

 1  192.168.1.1 (192.168.1.1)  7.775 ms  2.787 ms  2.707 ms

 2  10.96.46.129 (10.96.46.129)  2.540 ms  4.908 ms  12.965 ms

 3  10.69.50.14 (10.69.50.14)  19.102 ms  34.209 ms  12.529 ms

 4  wave-saratoga.mesh (10.70.253.160)  15.053 ms  14.336 ms  13.531 ms

 5  liteap-vernon.mesh (10.70.253.26)  16.132 ms  18.984 ms  20.995 ms

 6  eh8010-sslope.mesh (10.70.253.4)  54.866 ms  16.913 ms  34.849 ms

 7  eh8010-sn3.mesh (10.70.253.111)  28.070 ms  38.085 ms  18.735 ms

 8  10.70.89.131 (10.70.89.131)  23.863 ms  49.232 ms  14.643 ms

 9  ar01.jfk09.pilotfiber.net (142.154.197.1)  20.695 ms  44.256 ms  26.344 ms

10  et-0-0-49.ar01.jfk09.pilotfiber.net (104.129.141.102)  12.930 ms  29.860 ms  31.713 ms

11  et-0-1-3.cr01.r16.jfk00.pilotfiber.net (192.81.138.166)  26.442 ms  111.414 ms

    et-2-1-0.br01.jfk07.pilotfiber.net (104.129.140.236)  28.658 ms

12  br01.jfk05.pilotfiber.net (192.81.139.197)  35.067 ms  16.778 ms  13.218 ms

13  et-7-0-10.edge2.newyork6.level3.net (64.152.165.233)  35.681 ms  16.608 ms  68.254 ms

14  4.30.244.202 (4.30.244.202)  33.099 ms  35.758 ms  15.380 ms

15  * * *

16  * * *

17  pa7500-ae13092.net.nyu.edu (128.122.254.200)  15.709 ms  14.870 ms  25.097 ms

18  * * *
…14 more hops of * * *, silence through hop 31

taking forever and my patience is thin

at 17 we see NYU! yay!

Reflections

My first 13 hops are the same every time an average round trip of 24.311 ms thats same country vibes every time. 2 to 3 is also a major jump for me. I wonder how this will be different at NYU or on a cloudy day, since Im nyc mesh and weather affects it.