Outage between GBLX and HE?

Mailman List Mirror (Read Only)
1

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?

2

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.

3

Brielle Bruns wrote:

4

* 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

5

It looks like it's back now. I was seeing spotting US connectivity via GLBX upto 08:57 GMT.

6

I may have spoken too soon... issues are on going.

7

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

8

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. :slight_smile:

http://www.printfection.com/ras/Global-Double-Crossing-2-T-Shirt/_p_4935066

9

Glad its not just me. Guess I don't have to reboot my Mac or my Linux firewall, eh? :slight_smile:

10

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.

11

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