[30349] in North American Network Operators' Group
above.net <=> bbnplanet.net?
daemon@ATHENA.MIT.EDU (Jeff.Hodges@kingsmountain.com)
Fri Jul 28 02:13:14 2000
Message-Id: <200007280611.XAA16334@breakaway.Stanford.EDU>
To: nanog@merit.edu
Cc: Jeff.Hodges@kingsmountain.com
From: Jeff.Hodges@kingsmountain.com
Reply-To: Jeff.Hodges@kingsmountain.com
Date: Thu, 27 Jul 2000 23:11:34 -0700
Errors-To: owner-nanog-outgoing@merit.edu
I have a (possibly naive) question..
The peering between above.net <=> bbnplanet.net seems to have (at least)two
states..
(1) "abysmal" (500..800 ms latecies)
:
9 dfw-lax-oc3.dfw.above.net (208.184.102.154) 59.474 ms 59.657 ms 59.794
ms
10 s3-0-6.crtntx1-cr1.bbnplanet.net (4.24.104.21) 758.127 ms 745.747 ms
741.110 ms
:
(2) "tolerable" (50..100 ms latencies)
:
8 lax-sjc-oc3.lax.above.net (216.200.0.165) 16.479 ms 16.523 ms 16.183 ms
9 dfw-lax-oc3.dfw.above.net (208.184.102.154) 61.052 ms 58.664 ms 59.898
ms
10 s3-0-6.crtntx1-cr1.bbnplanet.net (4.24.104.21) 62.212 ms 67.094 ms
65.389 ms
:
..with it being in state#1 for days at a time, and then suddenly being in
state #2 for a while (a few hours to a day or so). This has been going on for
months at least. Anybody have any idea what's up here? Has anyone else noticed
this?
today it exhibited a new state #3 for several hours: "near-death" (2000..3000+
ms latencies), after thankfully being in state #2 for a few hours. *sigh*.
Isn't this affecting at least a few other folks?
thanks,
JeffH
