Can anyone from Verizon take a look at this behavior for us?
We’re having multiple Verizon FiOS users in the NYC/NJ area appear to teleport from their FiOS router to our IP in the Pittsburgh region. Users are seeing extreme slowness with TCP traffic, but ping times seem reasonable.
User 1:
1 fios_quantum_gateway (192.168.1.1) 1.575 ms 2.426 ms 3.193 ms
2 204.16.244.8 (204.16.244.8) 2.269 ms 3.055 ms 2.727 ms
User 2:
1 fios_quantum_gateway (192.168.1.1) 1.565 ms 1.048 ms 0.947 ms
2 204.16.244.8 (204.16.244.8) 2.162 ms 3.588 ms 3.048 ms
I can provide end-user NYC/NJ IPs off-list if desirable.
Here’s a normal looking trace from an FiOS line locally in the Pittsburgh region:
IP: 108.39.229.34
Tracing route to four.libsyn.com [204.16.244.8]
over a maximum of 30 hops:
Is this a possible traffic engineering blip? I can’t say we’ve ever seen trace routes return such sparse results and actually make it to the destination.
Can anyone from Verizon take a look at this behavior for us?
We’re having multiple Verizon FiOS users in the NYC/NJ area appear to
teleport from their FiOS router to our IP in the Pittsburgh region.
Verizon is doing something seriously weird to windows traceroute:
C:\Users\Lee>tracert www.yahoo.com
Tracing route to atsv2-fp-shed.wg1.b.yahoo.com [98.138.219.232]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms fw.home.net
2 1 ms <1 ms <1 ms vbz-router.home.net [192.168.1.1]
3 8 ms 3 ms 6 ms
media-router-fp2.prod1.media.vip.ne1.yahoo.com [98.138.219.232]
Trace complete.
C:\Users\Lee>ping -i 12 www.yahoo.com.
Pinging atsv2-fp-shed.wg1.b.yahoo.com [98.138.219.232] with 32 bytes of data:
Reply from 98.138.0.87: TTL expired in transit.
Reply from 98.138.0.87: TTL expired in transit.
Reply from 98.138.0.87: TTL expired in transit.
Reply from 98.138.0.87: TTL expired in transit.
Ping statistics for 98.138.219.232:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\Users\Lee>ping -i 13 www.yahoo.com.
Pinging atsv2-fp-shed.wg1.b.yahoo.com [98.138.219.232] with 32 bytes of data:
Reply from 98.138.219.232: bytes=32 time=32ms TTL=54
Reply from 98.138.219.232: bytes=32 time=31ms TTL=54
Reply from 98.138.219.232: bytes=32 time=33ms TTL=54
Reply from 98.138.219.232: bytes=32 time=33ms TTL=54
Ping statistics for 98.138.219.232:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 33ms, Average = 32ms
Windows traceroute uses ICMP by default, Unix based systems use UDP. For example from my Mac on Fios in Westchester, NY (and yes, they are doing something with ICMP traceroutes, possibly within their gateway box):