Hi All,
Not sure where the problem is at but several packets are being dropped
to several different hosts from the DC area. (This is not the Google
DNS problem)
I tried connecting to several different known sites with roughly 40%
being unresponsive from two seperate ISPs (Speakeasy and Comcast.)
Traceroute to sans.org via Comcast:
Looks OK to me (from Verizon DSL in NY):
Traceroute to (64.112.229.131)
1 * (10.32.19.1) 20 ms 22 ms 22 ms
2 * (130.81.11.161) 22 ms 22 ms 22 ms
3 so-6-0-0-0.BB-RTR2.NY325.verizon-gni.net (130.81.18.90) 22 ms 22 ms 22 ms
4 so-6-0-0-0.BB-RTR2.NY60.verizon-gni.net (130.81.7.201) 22 ms 24 ms 22 ms
5 so-2-0-0-0.PEER-RTR1.NY60.verizon-gni.net (130.81.4.214) 24 ms 22 ms 22 ms
6 jfk-edge-20.inet.qwest.net (65.116.172.85) 22 ms 22 ms 22 ms
7 jfk-core-01.inet.qwest.net (205.171.230.14) 22 ms 22 ms 22 ms
8 stl-core-01.inet.qwest.net (205.171.5.81) 94 ms 122 ms 94 ms
9 egn-core-01.inet.qwest.net (205.171.5.126) 100 ms 100 ms 100 ms
10 eug-edge-02.inet.qwest.net (205.171.150.18) 102 ms 100 ms 100 ms
11 * (207.109.243.74) 100 ms 100 ms 102 ms
12 64-112-224-3-ips-eug-or-core02.tcpipservices.net (64.112.224.3) 116 ms 116 ms 118 ms
13 64-112-227-69-ips-eug-or-lb01-2.tcpipservices.net (64.112.227.69) 116 ms 118 ms 118 ms
14 maverick31.sans.org (64.112.229.131) 142 ms 116 ms 118 ms
Mark Owen wrote:
Everything is back up now. Guess it was a router glitch somewhere to
compliment Google's DNS issue.