Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: [FIXED] Internap Denver <-> HE Connectivity is down  (Read 3519 times)

nayrnet

  • Newbie
  • *
  • Posts: 5
[FIXED] Internap Denver <-> HE Connectivity is down
« on: December 28, 2009, 10:34:50 AM »

This morning I noticed all my IPv6 Tunnels going thru Internap were down, regardless of tunnel endpoint.
all other tunnels were working fine on other providers.

I cant ping any tunnelbroker IPv4 endpoint, 97.5% packet loss over several hours.

I figured the issue was with my upstream provider who uses internap for there primary carrier, they quickly submitted a ticket on my behalf and this was the reply from there support team.

Code: [Select]
It looks like Hurricane-Electric is having issues. I dont have any
problems getting to the IP from outside Denver, where routes go over
Savvis, but as soon as I try going from a box in Denver, where once
packets leave our PNAP and hit Globix, there are issues. Since the IP in
question belongs to Hurricane-Electric we are going to have to say that
this issue belongs to them.

Can you comment if your having peering issues currently in Denver, CO?

Cheers,
-Ryan
« Last Edit: December 28, 2009, 12:03:14 PM by nayrnet »
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1705
Re: Internap Denver <-> HE Connectivity is down
« Reply #1 on: December 28, 2009, 10:47:00 AM »

All of our Internap ipv4/ipv6 peering is up, and without any sessions having bounced. Also we don't have presence in Denver, so no we wouldn't be having any issues there. Maybe some traceroutes, or telling us your IPv4 endpoint so we can test the return path, or you can do this with our looking glass.
« Last Edit: December 28, 2009, 10:52:43 AM by broquea »
Logged

nayrnet

  • Newbie
  • *
  • Posts: 5
Re: Internap Denver <-> HE Connectivity is down
« Reply #2 on: December 28, 2009, 11:10:21 AM »

208.72.157.57 is my endpoint, and its trying to connect to 72.52.104.74

which is fmnt2, I try to ping back thru looking lass and it fails as well.


Logged

nayrnet

  • Newbie
  • *
  • Posts: 5
Re: Internap Denver <-> HE Connectivity is down
« Reply #3 on: December 28, 2009, 11:18:45 AM »

my other tunnel is going through 216.218.226.238 from 208.72.157.56 and has the same issue, cant ping either end..
Logged

nayrnet

  • Newbie
  • *
  • Posts: 5
Re: Internap Denver <-> HE Connectivity is down
« Reply #4 on: December 28, 2009, 11:22:40 AM »

----216.218.226.238 PING Statistics----
80 packets transmitted, 3 packets received, 96% packet loss
round-trip (ms)  min/avg/max/stddev = 38.4/38.5/38.7/0.17

--- 72.52.104.74 ping statistics ---
347 packets transmitted, 17 received, 95% packet loss, time 346720ms
rtt min/avg/max/mdev = 30.077/30.311/31.693/0.425 ms


traceroute to 72.52.104.74 (72.52.104.74), 30 hops max, 40 byte packets
 1  208.72.157.3 (208.72.157.3)  1.141 ms  0.966 ms  0.929 ms
 2  10.255.255.5 (10.255.255.5)  0.910 ms  1.168 ms  1.030 ms
 3  border9.ge3-1.redrocks-1.den.pnap.net (216.52.42.117)  3.550 ms  3.412 ms  2.855 ms
 4  core5.ge2-0-bbnet1.den.pnap.net (216.52.40.19)  2.955 ms core5.ge2-2-bbnet2.den.pnap.net (216.52.40.83)  2.281 ms  2.140 ms
 5  ae0.421.ar3.DEN2.gblx.net (64.209.103.53)  2.651 ms  2.779 ms  2.639 ms
 6  * * *
 7  * * *
Logged

nayrnet

  • Newbie
  • *
  • Posts: 5
Re: Internap Denver <-> HE Connectivity is down
« Reply #5 on: December 28, 2009, 12:02:45 PM »

I gave the support ppl your looking glass addy and they quickly took ownership off the issue and have resolved it, all my tunnels are working great once again. Thanks for the assistance.
Logged