I'm noticing similar problems this AM with CW's backbone starting at bloomington heading back east to DC. Can anyone (preferrably from CW) provide a tidbit of information on what is happening, or when this will be fixed? Jay Stewart Vice President Olympia Networking Services http://www.olywa.net 15 * 1002 ms * core3-hssi3-0.Bloomington.cw.net [206.157.77.41] 16 1612 ms * * bordercore2.WashingtonEast.cw.net [166.48.246.1] 17 * 1081 ms * healthscribe-inc.WashingtonEast.cw.net [166.48.26.158] 18 * * * Request timed out. 19 1181 ms 1082 ms * 208.138.226.13 20 1442 ms 1172 ms * 208.138.226.13 21 1082 ms 1131 ms * 208.138.226.13 22 * 1131 ms * 208.138.226.13 23 1091 ms 1202 ms * 208.138.226.13 24 * * 1162 ms 208.138.226.13 -----Original Message----- From: Dan Hollis <goemon@sasami.anime.net> To: 'nanog@merit.edu' <nanog@merit.edu> Date: Sunday, October 25, 1998 7:58 PM Subject: cw/mci meltdown @ mae-west san fransisco?
So anyone know what the deal is with the cw/mci meltdown at mae-west san fransisco since approximately Oct 25 19:00 PST?
Anything going through borderx1-fddi-1.SanFrancisco.cw.net, core4.SanFrancisco.cw.net core6.SanFrancisco.cw.net, core7.SanFrancisco.cw.net, mae-west6-nap.SanFrancisco.cw.net etc are totally melty.
Anything through sacramento appears fine.
-Dan