I just noticed that traceroutes from my home to, e.g., 44.192.0.1, get stuck in a routing loop within the rr.com network. (I'm on Spectrum Cable, formerly Time Warner Cable which branded its service as "roadrunner" (rr.com). I suppose this means Amazon isn't BGP advertising these addresses yet.
Traces to, e.g, 44.0.0.1, 44.64.0.1 and 44.128.0.1 all behave as expected.
Just an observation.
Phil
Correct, the prefix isn’t announced.
http://lg.ring.nlnog.net/prefix_detail/lg01/ipv4?q=44.192.0.1
Can be used as a real time lookup.
Kind regards,
Job
On Fri, Jul 19, 2019 at 11:57 Phil Karn karn@ka9q.net wrote:
I just noticed that traceroutes from my home to, e.g., 44.192.0.1, get stuck in a routing loop within the rr.com network. (I'm on Spectrum Cable, formerly Time Warner Cable which branded its service as "roadrunner" (rr.com). I suppose this means Amazon isn't BGP advertising these addresses yet.
Traces to, e.g, 44.0.0.1, 44.64.0.1 and 44.128.0.1 all behave as expected.
Just an observation.
Phil
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
-
Job Snijders -
Phil Karn