traceroute to where? those two seem reasonable for x-country latencies what protocol(s) and port(s) are a problem, had you tried hping3 to test connectivity?
On Sat, Nov 9, 2013 at 9:41 PM, Sean Cline <scl...@riotgames.com> wrote: > Good evening everyone, for the past two days our customers using Verizon FIOS > (residential) have been complaining about high latency or intermittent > packetloss to several of our datacenters throughout the US. > > We have been trying to get in contact with Verizon but since we don't > directly peer with Verizon they have no obligation to answer us, we are not > getting very far with them directly. > > Here is a sample traceroutes, any information if you guys/girls are aware of > would be super helpful :) > > 1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1] > 2 5 ms 5 ms 4 ms 96.243.154.1 > 3 9 ms 11 ms 11 ms G0-9-1-6.TAMPFL-LCR-22.verizon-gni.net > [130.81.140.64] > 4 34 ms 10 ms 9 ms so-4-0-0-0.TPA01-BB-RTR2.verizon-gni.net > [130.81.199.28] > 5 96 ms 96 ms 78 ms 0.ae2.XL4.LAX15.ALTER.NET [140.222.227.21] > 6 63 ms 64 ms 64 ms POS7-0-0.GW3.LAX15.ALTER.NET [152.63.112.109] > 7 77 ms 78 ms 78 ms internapGIGE-gw.customer.alter.net > [157.130.236.110] > 8 77 ms 77 ms 77 ms border1.po2-20g-bbnet2.lax010.pnap.net > [216.52.255.103] > > 1 1 ms <1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1] > 2 5 ms 5 ms 5 ms L100.NYCMNY-VFTTP-32.verizon-gni.net > [71.125.61.1] > 3 8 ms 7 ms 7 ms G1-15-2-5.NYCMNY-LCR-22.verizon-gni.net > [130.81.218.58] > 4 7 ms 6 ms 6 ms ae4-0.NY5030-BB-RTR1.verizon-gni.net > [130.81.163.224] > 5 92 ms 91 ms 70 ms 0.xe-6-1-0.XL3.LAX15.ALTER.NET > [152.63.112.146] > 6 71 ms 69 ms 71 ms POS6-0-0.GW3.LAX15.ALTER.NET [152.63.112.105] > 7 81 ms 83 ms 83 ms internapGIGE-gw.customer.alter.net > [157.130.236.110] > 8 81 ms 81 ms 84 ms border1.po2-20g-bbnet2.lax010.pnap.net > [216.52.255.103]