Hey All, Sorry to bother the list, but I'm noticing that I've got no connectivity to Hurricane Electric through GBLX from my Qwest DSL. In this case, I'm trying to get to tunnelbroker.net: ... 3 184-99-65-41.boid.qwest.net (184.99.65.41) 38.438 ms 49.250 ms 38.459 ms 4 sea-brdr-02.inet.qwest.net (67.14.41.14) 60.071 ms 53.198 ms 54.223 ms 5 te8-3-10g.ar5.sea1.gblx.net (64.208.110.141) 294.182 ms 437.842 ms * 6 * * * Testing out through the T1 which goes via twtelecom works fine, as does from co-loc in Seattle which goes through Integra. Don't suppose anyone else is noticing this as well? -- Brielle Bruns The Summit Open Source Development Group http://www.sosdg.org / http://www.ahbl.org
On 11/16/10 8:32 PM, Brielle Bruns wrote:
Hey All,
Sorry to bother the list, but I'm noticing that I've got no connectivity to Hurricane Electric through GBLX from my Qwest DSL.
In this case, I'm trying to get to tunnelbroker.net:
... 3 184-99-65-41.boid.qwest.net (184.99.65.41) 38.438 ms 49.250 ms 38.459 ms 4 sea-brdr-02.inet.qwest.net (67.14.41.14) 60.071 ms 53.198 ms 54.223 ms 5 te8-3-10g.ar5.sea1.gblx.net (64.208.110.141) 294.182 ms 437.842 ms * 6 * * *
Testing out through the T1 which goes via twtelecom works fine, as does from co-loc in Seattle which goes through Integra.
Don't suppose anyone else is noticing this as well?
Asymmetrical routing for the win. Did a trace from HE's LG to the DSL: core1.fmt1.he.net> traceroute 65.102.72.22 numeric Tracing the route to IP node from 1 to 30 hops 1 19 ms <1 ms 1 ms 66.160.158.242 2 14 ms 3 ms 1 ms 213.248.86.53 3 1 ms 1 ms 1 ms 213.248.87.50 4 * * * ? 5 * * * ? 6 * * * ? 7 * * * ? IP: Errno(8) Trace Route Failed, no response from target node. # Entry cached for another 32 seconds. Since i'm taking two separate paths, I'm not sure where the problem is exactly. -- Brielle Bruns The Summit Open Source Development Group http://www.sosdg.org / http://www.ahbl.org
Brielle Bruns wrote:
On 11/16/10 8:32 PM, Brielle Bruns wrote:
Hey All,
Sorry to bother the list, but I'm noticing that I've got no connectivity to Hurricane Electric through GBLX from my Qwest DSL.
7 * * * ? IP: Errno(8) Trace Route Failed, no response from target node. # Entry cached for another 32 seconds.
Since i'm taking two separate paths, I'm not sure where the problem is exactly.
Did you reboot your computer? (running and ducking!)
* Brielle Bruns <bruns@2mbit.com> [2010-11-17 04:34]:
Hey All,
Sorry to bother the list, but I'm noticing that I've got no connectivity to Hurricane Electric through GBLX from my Qwest DSL.
In this case, I'm trying to get to tunnelbroker.net:
... 3 184-99-65-41.boid.qwest.net (184.99.65.41) 38.438 ms 49.250 ms 38.459 ms 4 sea-brdr-02.inet.qwest.net (67.14.41.14) 60.071 ms 53.198 ms 54.223 ms 5 te8-3-10g.ar5.sea1.gblx.net (64.208.110.141) 294.182 ms 437.842 ms * 6 * * *
Hello from Old Europe, I just openend a case with GBLX because I'm unable to reach destinations in USA. As the technician told me they're having issues in the Seattle area and are trying to fix them at the moment. Kind Regards, Sebastian -- New GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) Old GPG Key-ID: 0x76B79F20 (0x1B6034F476B79F20) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant
It looks like it's back now. I was seeing spotting US connectivity via GLBX upto 08:57 GMT. -----Original Message----- From: Brielle Bruns [mailto:bruns@2mbit.com] Sent: 17 November 2010 03:32 To: NANOG list Subject: Outage between GBLX and HE? Hey All, Sorry to bother the list, but I'm noticing that I've got no connectivity to Hurricane Electric through GBLX from my Qwest DSL. In this case, I'm trying to get to tunnelbroker.net: ... 3 184-99-65-41.boid.qwest.net (184.99.65.41) 38.438 ms 49.250 ms 38.459 ms 4 sea-brdr-02.inet.qwest.net (67.14.41.14) 60.071 ms 53.198 ms 54.223 ms 5 te8-3-10g.ar5.sea1.gblx.net (64.208.110.141) 294.182 ms 437.842 ms * 6 * * * Testing out through the T1 which goes via twtelecom works fine, as does from co-loc in Seattle which goes through Integra. Don't suppose anyone else is noticing this as well? -- Brielle Bruns The Summit Open Source Development Group http://www.sosdg.org / http://www.ahbl.org
I may have spoken too soon... issues are on going. -----Original Message----- From: Paul Kelly :: Blacknight [mailto:paul@blacknight.com] Sent: 17 November 2010 09:21 To: 'Brielle Bruns'; NANOG list Subject: RE: Outage between GBLX and HE? It looks like it's back now. I was seeing spotting US connectivity via GLBX upto 08:57 GMT. -----Original Message----- From: Brielle Bruns [mailto:bruns@2mbit.com] Sent: 17 November 2010 03:32 To: NANOG list Subject: Outage between GBLX and HE? Hey All, Sorry to bother the list, but I'm noticing that I've got no connectivity to Hurricane Electric through GBLX from my Qwest DSL. In this case, I'm trying to get to tunnelbroker.net: ... 3 184-99-65-41.boid.qwest.net (184.99.65.41) 38.438 ms 49.250 ms 38.459 ms 4 sea-brdr-02.inet.qwest.net (67.14.41.14) 60.071 ms 53.198 ms 54.223 ms 5 te8-3-10g.ar5.sea1.gblx.net (64.208.110.141) 294.182 ms 437.842 ms * 6 * * * Testing out through the T1 which goes via twtelecom works fine, as does from co-loc in Seattle which goes through Integra. Don't suppose anyone else is noticing this as well? -- Brielle Bruns The Summit Open Source Development Group http://www.sosdg.org / http://www.ahbl.org
On Wed, Nov 17, 2010 at 09:55:10AM +0000, Paul Kelly :: Blacknight wrote:
I may have spoken too soon... issues are on going.
We were seeing routing irregularities with GBLX as well. It seems they sending out our prefix to their peers, but blackholing the traffic coming back. We've shutdown our session with AS3549 until someone there answers our ticket. -cjp
On Wed, Nov 17, 2010 at 10:36:09AM -0500, Christopher J. Pilkington wrote:
On Wed, Nov 17, 2010 at 09:55:10AM +0000, Paul Kelly :: Blacknight wrote:
I may have spoken too soon... issues are on going.
We were seeing routing irregularities with GBLX as well. It seems they sending out our prefix to their peers, but blackholing the traffic coming back. We've shutdown our session with AS3549 until someone there answers our ticket.
Probably another LSP blackholing issue, look at the archives a few weeks back you'll see the same issue on GX in Seattle. As for the issue this morning, they have a router that has been blackholing traffic in Ashburn for a good long while now. I almost put on my Global Double Crossing t-shit this morning too. :) http://www.printfection.com/ras/Global-Double-Crossing-2-T-Shirt/_p_4935066 -- Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
On 11/17/10 10:33 AM, Richard A Steenbergen wrote:
Probably another LSP blackholing issue, look at the archives a few weeks back you'll see the same issue on GX in Seattle. As for the issue this morning, they have a router that has been blackholing traffic in Ashburn for a good long while now.
I almost put on my Global Double Crossing t-shit this morning too.:)
http://www.printfection.com/ras/Global-Double-Crossing-2-T-Shirt/_p_4935066
Glad its not just me. Guess I don't have to reboot my Mac or my Linux firewall, eh? :-) -- Brielle Bruns The Summit Open Source Development Group http://www.sosdg.org / http://www.ahbl.org
We saw further evidence of this on paths traversing global crossing to a customer last night. I don't know about others but we are intending to make some efforts to move traffic other places, this type of repeated failure is just terrible, especially since they still continue to announce routes indicating reachability that does not exist. John @ AS11404 in Seattle. -----Original Message----- From: Richard A Steenbergen [mailto:ras@e-gerbil.net] Sent: Wednesday, November 17, 2010 9:33 AM To: Christopher J. Pilkington Cc: NANOG list Subject: Re: Outage between GBLX and HE? On Wed, Nov 17, 2010 at 10:36:09AM -0500, Christopher J. Pilkington wrote:
On Wed, Nov 17, 2010 at 09:55:10AM +0000, Paul Kelly :: Blacknight wrote:
I may have spoken too soon... issues are on going.
We were seeing routing irregularities with GBLX as well. It seems they sending out our prefix to their peers, but blackholing the traffic coming back. We've shutdown our session with AS3549 until someone there answers our ticket.
Probably another LSP blackholing issue, look at the archives a few weeks back you'll see the same issue on GX in Seattle. As for the issue this morning, they have a router that has been blackholing traffic in Ashburn for a good long while now. I almost put on my Global Double Crossing t-shit this morning too. :) http://www.printfection.com/ras/Global-Double-Crossing-2-T-Shirt/_p_4935066 -- Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
We saw further evidence of this on paths traversing global crossing to a customer last night. I don't know about others but we are intending to make some efforts to move traffic other places, this type of repeated failure is just terrible, especially since they still continue to announce routes indicating reachability that does not exist.
John @ AS11404 in Seattle.
This has been going on for some months, moving from market to market. LAX, SEA, now ASH. -Randy
participants (8)
-
Brielle Bruns -
Christopher J. Pilkington -
John van Oppen -
Mike -
Paul Kelly :: Blacknight -
Randy McAnally -
Richard A Steenbergen -
Sebastian Wiesinger