Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: tserv11.ams1 problems?  (Read 2880 times)

searchy

  • Newbie
  • *
  • Posts: 1
tserv11.ams1 problems?
« on: January 09, 2011, 03:49:11 AM »

Are there any known problems with tserv11.ams1?  I can't get any response from it.
Logged

hisken

  • Jr. Member
  • **
  • Posts: 62
Re: tserv11.ams1 problems?
« Reply #1 on: January 09, 2011, 03:57:27 AM »

Are there any known problems with tserv11.ams1?  I can't get any response from it.
Same problem here. All my tunnel endpoints connecting to tserv11.ams1 are getting timeouts.

http://tunnelbroker.net/status.php doesn't mention anything concerning this downtime.
Logged

hisken

  • Jr. Member
  • **
  • Posts: 62
Re: tserv11.ams1 problems?
« Reply #2 on: January 09, 2011, 04:32:23 AM »

My tunnel is up again. The tunnel latency has increased however, and a traceroute shows me the peering has changed.

C:\Users\shisken>tracert  -4 tserv11.ams1.ipv6.he.net

Tracing route to tserv11.ams1.ipv6.he.net [216.66.84.46]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  artemis.lan [172.19.94.254]
  2     7 ms     5 ms     8 ms  gravenburg.wan [10.204.220.1]
  3     5 ms     5 ms     9 ms  gn-rc0002-cr102-irb-202.core.as9143.net [213.51.133.241]
  4    10 ms    10 ms     9 ms  asd-tr0409-cr101-ae2-0.core.as9143.net [213.51.158.16]
  5     9 ms    11 ms     9 ms  Te2-2.ar2.AMS1.gblx.net [208.51.117.93]
  6    17 ms    19 ms    16 ms  HURRICANE-ELECTRIC-LLC.TenGigabitEthernet1-3.ar4.FRA3.gblx.net [64.212.32.46]
  7    17 ms    21 ms    24 ms  10gigabitethernet1-4.core1.ams1.he.net [72.52.92.94]
  8    16 ms    17 ms    19 ms  tserv11.ams1.ipv6.he.net [216.66.84.46]

Trace complete.

C:\Users\shisken>

The traceroute used to show me directly after hop 4 a "10gigabitethernet-*blabla*.he.net" and after that the tunnel server. Since the peering has changed this morning it is being routed via gblx/Frankfurt if I understand it correctly.

@broquea or other HE staff: what could be the cause of this sudden peering change?


Everything is back to normal. Thanks.
C:\Users\shisken>tracert -4 tserv11.ams1.ipv6.he.net

Tracing route to tserv11.ams1.ipv6.he.net [216.66.84.46]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  artemis.lan [172.19.94.254]
  2     5 ms     5 ms     5 ms  gravenburg.wan [10.204.220.1]
  3     7 ms     5 ms     6 ms  gn-rc0002-cr102-irb-202.core.as9143.net [213.51.133.241]
  4     9 ms    11 ms     9 ms  asd-tr0409-cr101-ae2-0.core.as9143.net [213.51.158.16]
  5    9 ms    9 ms    10 ms  20gigabitethernet1-3.core1.ams1.he.net [195.69.145.150]
  6     9 ms     9 ms     9 ms  tserv11.ams1.ipv6.he.net [216.66.84.46]

Trace complete.

C:\Users\shisken>
« Last Edit: January 09, 2011, 04:47:31 AM by hisken »
Logged