Verizon NJ <-> Hetzner DE, routes via LA?

Mailman List Mirror (Read Only)
1

Since yesterday, I've started to see an increase in latency between my self in NJ on Verizon FIOS and Hetzner in DE. Even using Verizon:s looking glass is giving me 250ms. This is an increase of about 150ms (Seems to be true for most of the US East Coast)
A traceroute seems to tell me that the traffic is routed via LA, which could explain the increase in latency.

Traceroute from Verizon looking glass page, sourcing Newark

traceroute to 144.76.94.10 (144.76.94.10), 30 hops max, 52 byte packets
  1 0.et-10-3-0.GW7.LAX15.ALTER.NET (140.222.235.147) 61.052 ms 61.522 ms 61.063 ms
  2 152.179.21.22 (152.179.21.22) 158.708 ms 158.683 ms 158.681 ms
  3 * * pd900ccde.dip0.t-ipconnect.de (217.0.204.222) 263.187 ms
  4 62.157.248.138 (62.157.248.138) 249.071 ms 248.570 ms 248.737 ms
  5 * * *
  6 ex9k2.dc10.fsn1.hetzner.com (213.239.229.62) 250.333 ms 252.488 ms 250.232 ms

Does anyone have any more insight? (Verizon status pages says everything is fine, ofc)

2

Since yesterday, I’ve started to see an increase in latency between my
self in NJ on Verizon FIOS and Hetzner in DE. Even using Verizon:s
looking glass is giving me 250ms. This is an increase of about 150ms
(Seems to be true for most of the US East Coast)
A traceroute seems to tell me that the traffic is routed via LA, which
could explain the increase in latency.

Traceroute from Verizon looking glass page, sourcing Newark
https://www.verizon.com/business/why-verizon/looking-glass/

traceroute to 144.76.94.10 (144.76.94.10), 30 hops max, 52 byte packets
1 0.et-10-3-0.GW7.LAX15.ALTER.NET (140.222.235.147) 61.052 ms 61.522
ms 61.063 ms
2 152.179.21.22 (152.179.21.22) 158.708 ms 158.683 ms 158.681 ms
3 * * pd900ccde.dip0.t-ipconnect.de (217.0.204.222) 263.187 ms

that’s odd to see, I had thought DTAG was a peer of 701 at some point.
maybe that’s an incorrect 15 yr old memory :frowning: (or maybe things changed!)

it happens that from IAD area … same path via LAX :frowning:
It also seems strange that 3320 would ONLY appear in LAX… maybe their east-coast
landings are feeling under the weather?

4 62.157.248.138 (62.157.248.138) 249.071 ms 248.570 ms 248.737 ms
5 * * *
6 ex9k2.dc10.fsn1.hetzner.com (213.239.229.62) 250.333 ms 252.488 ms
250.232 ms

Does anyone have any more insight? (Verizon status pages says everything
is fine, ofc)

the link you see above is a customer link ,so… sure, everything for VZ is fine :slight_smile:
their customer though MAY be having a sad day.