| Anyone know what is going on? @unknown:~$ traceroute 4.2.2.2
traceroute to 4.2.2.2 (4.2.2.2), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 0.672 ms 0.797 ms 0.970 ms
2 10.150.0.1 (10.150.0.1) 979.205 ms 979.580 ms 980.111 ms
3 24.215.3.130 (24.215.3.130) 981.624 ms 982.392 ms 982.769 ms
4 core2.bgp.mountaincable.net (24.215.3.186) 980.714 ms 981.096 ms 981.885 ms
5 colosseum-tor-gw.peer1.net (66.199.142.249) 983.215 ms 983.572 ms 983.931 ms
6 216.187.114.105 (216.187.114.105) 984.309 ms 1084.333 ms 1017.840 ms
7 10ge.xe-0-0-0.tor-1yg-cor-1.peer1.net (216.187.114.133) 1018.313 ms 1030.158 ms 1030.518 ms
8 oc48-po5-0.chi-eqx-dis-1.peer1.net (216.187.114.141) 1040.765 ms * *
9 * * *
10 vnsc-bak.sys.gtei.net (4.2.2.2) 613.016 ms 747.961 ms 937.184 ms
@unknown:~$ ping 4.2.2.2
PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data.
64 bytes from 4.2.2.2: icmp_seq=1 ttl=54 time=1081 ms
64 bytes from 4.2.2.2: icmp_seq=2 ttl=54 time=898 ms
64 bytes from 4.2.2.2: icmp_seq=3 ttl=54 time=744 ms
64 bytes from 4.2.2.2: icmp_seq=4 ttl=54 time=846 ms
64 bytes from 4.2.2.2: icmp_seq=5 ttl=54 time=751 ms
64 bytes from 4.2.2.2: icmp_seq=6 ttl=54 time=987 ms
64 bytes from 4.2.2.2: icmp_seq=7 ttl=54 time=1048 ms
^C
--- 4.2.2.2 ping statistics ---
8 packets transmitted, 7 received, 12% packet loss, time 7011ms
rtt min/avg/max/mdev = 744.544/908.248/1081.061/125.855 ms, pipe 2
@unknown:~$ ping 192.168.100.1
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_seq=1 ttl=63 time=2.18 ms
64 bytes from 192.168.100.1: icmp_seq=2 ttl=63 time=2.03 ms
64 bytes from 192.168.100.1: icmp_seq=3 ttl=63 time=2.16 ms
64 bytes from 192.168.100.1: icmp_seq=4 ttl=63 time=2.09 ms
64 bytes from 192.168.100.1: icmp_seq=5 ttl=63 time=2.35 ms
64 bytes from 192.168.100.1: icmp_seq=6 ttl=63 time=2.46 ms
64 bytes from 192.168.100.1: icmp_seq=7 ttl=63 time=2.09 ms
64 bytes from 192.168.100.1: icmp_seq=8 ttl=63 time=2.00 ms
^C
--- 192.168.100.1 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7029ms
rtt min/avg/max/mdev = 2.000/2.173/2.465/0.152 ms
Anyone know what is causing 1000ms pings? |
 MikeGPremium
join:2004-10-02
Hamilton, ON | Not seeing any problems, 5:46pm
Tracing route to vnsc-bak.sys.gtei.net [4.2.2.2]
over a maximum of 30 hops:
1 8 ms 7 ms 8 ms 10.150.0.1
2 10 ms 10 ms 9 ms 24.215.3.130
3 9 ms 9 ms 10 ms core2.bgp.mountaincable.net [24.215.3.186]
4 13 ms 10 ms 11 ms colosseum-tor-gw.peer1.net [66.199.142.249]
5 11 ms 10 ms 10 ms oc48-po5-0.tor-151f-cor-1.peer1.net [216.187.114.150]
6 12 ms 15 ms 10 ms 10ge.xe-0-0-0.tor-1yg-cor-1.peer1.net [216.187.114.133]
7 30 ms 27 ms 25 ms oc48-po5-0.chi-eqx-dis-1.peer1.net [216.187.114.141]
8 21 ms 20 ms 24 ms ge-7-23.car4.Chicago1.Level3.net [4.71.102.97]
9 21 ms 27 ms 21 ms ae-21-56.car1.Chicago1.Level3.net [4.68.101.162]
10 22 ms 24 ms 21 ms vnsc-bak.sys.gtei.net [4.2.2.2]
Trace complete.
--
Success is measured by effort.. |
