GBLX Fiber Cut - San Fran or Oakland
Anyone know any more? Is it actually GBLX or were they riding someone else's fiber that was cut? Their NOC said they wouldn't know anything for another 30 minutes. ?? Our web site's outa commision. Thanks Global Center for your robust fault tolerant design. (Grrrrr.)
Well it's affecting southern california. since I can't reach my T1 out there. 7 pos5-0-622M.cr1.NUQ.gblx.net (206.132.254.6) 13.964 ms 14.809 ms 14.423 ms 8 pos9-0-0-155M.cr2.BUR.gblx.net (206.251.1.50) 107.628 ms 103.784 ms 101.719 ms 9 pos0-3-155M.cr1.NUQ.gblx.net (206.251.1.49) 1009.959 ms 1047.401 ms 973.378 ms 10 pos9-0-0-155M.cr2.BUR.gblx.net (206.251.1.50) 1040.317 ms * * 11 pos0-3-155M.cr1.NUQ.gblx.net (206.251.1.49) 2044.301 ms * * Derrick On Fri, 8 Sep 2000, Michael Medwid wrote:
Anyone know any more? Is it actually GBLX or were they riding someone else's fiber that was cut? Their NOC said they wouldn't know anything for another 30 minutes. ??
Our web site's outa commision. Thanks Global Center for your robust fault tolerant design. (Grrrrr.)
On Fri, Sep 08, 2000 at 10:07:39AM -0700, Michael Medwid wrote:
Anyone know any more? Is it actually GBLX or were they riding someone else's fiber that was cut? Their NOC said they wouldn't know anything for another 30 minutes. ??
I haven't seen anything on their outage notification list yet, but something's definitely ill. I'm shutting down my BGP session with them for now. FYI: 7 pos5-0-622M.wr2.NYC2.gblx.net (206.132.249.165) [AS 3549] 4 msec 8 msec 4 msec [...] 12 pos7-0-2488M.wr1.lax1.gblx.net (206.132.116.145) [AS 3549] 72 msec 76 msec 72 msec 13 * pos11-0-0-155M.cr1.BUR.gblx.net (206.132.112.106) [AS 3549] 2368 msec 2312 msec 14 * fe8-0-0.cr2.BUR.gblx.net (207.218.173.51) [AS 3549] 2220 msec 2236 msec 15 * * * -adam
On Fri, Sep 08, 2000 at 02:23:13PM -0400, Adam Rothschild wrote:
I haven't seen anything on their outage notification list yet, but something's definitely ill.
traceroute -A animal.sf.oven.com
According to their (Phoenix?) NOC, the mail servers they normally use to send domestic-* outage notifications are unreachable as a result of this, so NOCs in other locations will be sending out details shortly. Here's what I'm seeing from LGA2 (their NYC customer colo): border1.nyc1.us#trace animal.sf.oven.com Type escape sequence to abort. Tracing the route to animal.sf.oven.com (209.143.240.3) 1 fe3-1-0.hr1.LGA2.gblx.net (206.41.16.249) [AS 3549] 4 msec 0 msec 0 msec 2 pos2-2-155M.cr1.LGA2.gblx.net (206.41.19.81) [AS 3549] 0 msec 4 msec 0 msec 3 pos1-0-622M.cr1.SFO1.gblx.net (206.132.110.122) [AS 3549] 2628 msec * 2712 msec 4 pos0-0-0-155M.ar1.SFO1.gblx.net (206.132.110.130) [AS 3549] 2872 msec * 2820 msec 5 oven-digital.s11-1-0-22-0.ar1.SFO1.gblx.net (207.138.186.246) [AS 3549] 2848 msec * * [...] ...however, here's a traceroute run at the same time, off someone with AS3549 transit in EWR (Whippany, NJ): traceroute to animal.sf.oven.com (209.143.240.3), 30 hops max, 40 byte packets [...] 3 s4-1.core1.whi.nac.net (209.123.11.153) [AS8001] 4 ms 2 ms 2 ms 4 global-crossing.transit.nac.net (207.99.10.2) [AS8001] 3 ms 2 ms 2 ms 5 s3-0-1-45M.br1.NYC2.gblx.net (206.132.29.161) [AS3549] 5 ms 14 ms 3 ms 6 pos2-1-155M.cr2.NYC2.gblx.net (206.132.249.193) [AS3549] 3 ms 4 ms 5 ms 7 pos1-0-622M.cr2.SFO1.gblx.net (206.132.110.126) [AS3549] 152 ms 155 ms 150 ms 8 pos1-0-0-155M.ar1.SFO1.gblx.net (206.132.110.138) [AS3549] 161 ms 152 ms 153 ms 9 oven-digital.s11-1-0-22-0.ar1.SFO1.gblx.net (207.138.186.246) [AS3549] 169 ms 161 ms 163 ms [...] -adam
participants (3)
-
Adam Rothschild -
Derrick -
Michael Medwid