|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Wed, 15 Jul 1998 14:29:13 -0700 To: nanog@merit.edu From: Donn Lasher <dlasher@owt.com> Cc: "Jason L. Weisberger" <jweis@softaware.com> In-Reply-To: <Pine.LNX.3.96.980715123135.27933C-100000@docholliday.softa ware.com> > 6 sl-bb21-ana-0-3.sprintlink.net (144.232.1.49) 2.843 ms 2.281 ms >3.05 ms > 7 sl-bb10-sj-0-0.sprintlink.net (144.232.8.130) 10.531 ms 11.275 ms >11.891 >ms > 8 sl-bb1-sj-0-0-0.sprintlink.net (144.232.3.2) 11.816 ms 11.561 ms >11.007 m >s > 9 sl-w2-mae-0-1-0.sprintlink.net (144.232.8.10) 1893.24 ms 1759.43 ms >1851. Called Sprint's NOC (Helpful, as always 1-800-232-6895) about 11am PST, and the tech I talked to was monitoring one of the four FDDI connects they have to MAEW. This comment was "Wow, the 5 min traffic for this link(T3) was 71 meg. I think that pipe is a little busy" My comment "Man you guys should get some compression on that line, what a slow T3!" He laughed. (No need for a Tx primer, it was a joke..) Since there was no offical "outage" they haven't informed their customers. I would attribute this to one of two things: 1. One of the pipes died, therefore all traffic is being carried over the other 3(?!) 2. Rush Limbaugh mentioned an interesting web site this morning, and they've been flooded ever since. I'll leave it up to you to figure out which one it is. Donn
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |