ticket 9878479

[Robert Dinse <nanook@eskimo.com>]

     I sent the previous mail prematurely and lost most of what I sent in the
process.  I have two SprintLink T1's; while I am getting occasional spikes of
latency on one link and packet loss of around 4% on both (there was no packet
loss under normal circumstances until after you folks did some work the weekend
before last on route reflectors); about 45 minutes ago; connectivity to much of
the Internet went away or nearly so.

     Normally I see excellent packet loss and latency to ftp.digital.com, on
the order of 40ms, but right now I am seeing 2700ms latency approximately on
the few packets that do get through, about 75% packet loss.

     Here is a traceroute:

traceroute ftp.digital.com
traceroute to ftp.digital.com (204.123.2.4), 30 hops max, 40 byte packets
 1  3com.eskimo.net (204.122.16.1)  4 ms  3 ms  3 ms
 2  sl-gw2-sea-1-1.sprintlink.net (144.228.94.17)  6 ms  13 ms
sl-gw2-sea-3-1.sprintlink.net (144.228.94.105)  7 ms
 3  144.228.90.8 (144.228.90.8)  9 ms  9 ms  13 ms
 4  sl-bb10-sea-2-1.sprintlink.net (144.232.6.17)  6 ms  29 ms  23 ms
 5  sl-bb10-sea-2-0.sprintlink.net (144.232.8.218)  62 ms  68 ms  63 ms
 6  sl-bb11-pen-9-0.sprintlink.net (144.232.5.157)  62 ms  73 ms  70 ms
 7  icm-bb5-pen-1-0-0.icp.net (144.232.5.74)  1124 ms * *
 8  * * *
 9  * * *
10  * * *
11  * * *

     As you can see it barely makes it to icm-bb5-pen-1-0-0.icp.net, and
actually if I do the traceroute numerous times, other hops past that point
occasionally show up intermittantly with very high latency.

     Similarly to ftp.uu.net:

traceroute to ftp.uu.net (192.48.96.9), 30 hops max, 40 byte packets
 1  3com.eskimo.net (204.122.16.1)  3 ms  3 ms  3 ms
 2  sl-gw2-sea-1-1.sprintlink.net (144.228.94.17)  6 ms  17 ms
sl-gw2-sea-3-1.sprintlink.net (144.228.94.105)  8 ms
 3  sl-bb1-sea-0-0.sprintlink.net (144.228.90.1)  6 ms  7 ms  16 ms
 4  sl-bb11-sea-0-2.sprintlink.net (144.232.6.37)  7 ms  6 ms  8 ms
 5  sl-bb5-sea-4-0-0.sprintlink.net (144.232.6.6)  10 ms  8 ms  8 ms
 6  sl-bb7-dc-1-0-0.sprintlink.net (144.232.8.162)  63 ms  60 ms  67 ms
 7  144.228.20.100 (144.228.20.100)  441 ms  466 ms  448 ms

     Here is a trace to netserver.ewa.net:

traceroute to ftp.uu.net (192.48.96.9), 30 hops max, 40 byte packets
 1  3com.eskimo.net (204.122.16.1)  3 ms  3 ms  3 ms
 2  sl-gw2-sea-1-1.sprintlink.net (144.228.94.17)  6 ms  17 ms
sl-gw2-sea-3-1.sprintlink.net (144.228.94.105)  8 ms
 3  sl-bb1-sea-0-0.sprintlink.net (144.228.90.1)  6 ms  7 ms  16 ms
 4  sl-bb11-sea-0-2.sprintlink.net (144.232.6.37)  7 ms  6 ms  8 ms
 5  sl-bb5-sea-4-0-0.sprintlink.net (144.232.6.6)  10 ms  8 ms  8 ms
 6  sl-bb7-dc-1-0-0.sprintlink.net (144.232.8.162)  63 ms  60 ms  67 ms
 7  144.228.20.100 (144.228.20.100)  441 ms  466 ms  448 ms

     Notice that it shares the same router where things went bad going to
ftp.uu.net, 144.228.20.100.

     Here is a traceroute to one of ixpnet's addresses:

traceroute to 12.18.130.11 (12.18.130.11), 30 hops max, 40 byte packets
 1  3com.eskimo.net (204.122.16.1)  6 ms  2 ms  2 ms
 2  sl-gw2-sea-3-1.sprintlink.net (144.228.94.105)  10 ms  12 ms
sl-gw2-sea-1-1.sprintlink.net (144.228.94.17)  23 ms
 3  144.228.90.8 (144.228.90.8)  16 ms  11 ms  11 ms
 4  sl-bb11-sea-2-1.sprintlink.net (144.232.6.21)  14 ms  17 ms  8 ms
 5  sl-bb5-sea-4-0-0.sprintlink.net (144.232.6.6)  10 ms  16 ms  12 ms
 6  sl-bb7-dc-1-0-0.sprintlink.net (144.232.8.162)  59 ms  63 ms  62 ms
 7  144.228.20.100 (144.228.20.100)  523 ms *  602 ms

     .. Again at the 7th hop, it shares the same router.  I don't get any
response past this point. 

     I am really concerned about both problems, whatever is preventing me from
reaching many sites and causing high packet loss to those sites; and we can get
to other sites like ftp.apple.com, www.yahoo.com, www.netscape.com fine in
spite of not being to reach these other sites; but I am also concerned about
this 2-4% packet loss that has remained on both of our links after the work you
folks did the weekend before last. 

     Thank you.