[Pool] Brief www outage

Daniel Frank ntp at tokuko.de
Sat May 18 19:23:30 UTC 2013


Hello,

seems to be a general issue in a backbone somewhere, not at Hetzner. 
Line 9 is already on the other side of the Atlantic. Line 6 seems to be 
in New York City, not sure where "lax" is supposed to be.

# traceroute6 ntppool.net
traceroute to ntppool.net (2607:f238:2::4) from 2a01:4f8:160:9061::2, 30 
hops max, 24 byte packets
  1  2a01:4f8:160:9060::1 (2a01:4f8:160:9060::1)  2.258 ms  0.851 ms 
0.859 ms
  2  hos-tr3.juniper2.rz16.hetzner.de (2a01:4f8:0:16:3:0:16:2)  0.226 ms 
  0.225 ms  0.197 ms
  3  hos-bb2.juniper4.ffm.hetzner.de (2a01:4f8:0:2::1:4)  6.216 ms  6.15 
ms  6.138 ms
  4  30gigabitethernet4-3.core1.fra1.he.net (2001:7f8::1b1b:0:1)  10.606 
ms  14.035 ms  6.526 ms
  5  10gigabitethernet5-3.core1.lon1.he.net (2001:470:0:1d2::1)  19.305 
ms  19.644 ms  19.325 ms
  6  10gigabitethernet10-4.core1.nyc4.he.net (2001:470:0:128::1)  88.125 
ms  88.519 ms  96.535 ms
  7  10gigabitethernet12-2.core1.lax1.he.net (2001:470:0:10e::1)  158.81 
ms  148.404 ms  148.64 ms
  8  10gigabitethernet1-3.core1.lax2.he.net (2001:470:0:72::2)  156.361 
ms  147.944 ms  149.477 ms
  9  * * *
10  2607:f238::cfab:1e01 (2607:f238::cfab:1e01)  160.455 ms  160.426 ms 
  160.456 ms
11  xe9-4.hr01.lax2.phyber.com (2607:f238:0:6::2)  160.301 ms  160.356 
ms  160.592 ms
12  * 2607:f238:0:13::2 (2607:f238:0:13::2)  160.653 ms *
13  2607:f238:2::4 (2607:f238:2::4)  160.804 ms !S  160.845 ms !S 
160.783 ms !S

Regards,
Daniel


On 18.05.2013 17:20, Christoph Lechleitner wrote:
> Am 2013-05-18 16:56, schrieb Ask Bjørn Hansen:
>> On Saturday, May 18, 2013 at 5:55 AM, Paul Staroch wrote:
>>> Is there some IPv6 routing problem since the migration?
>>>
>>> http://www.pool.ntp.org/scores/2a01:4f8:162:51e2::2 vs http://www.pool.ntp.org/scores/2a02:180:1:1::5b8f:533e
>> I'm looking into it. I suspect it's unrelated from moving rack.
>>
>>  From what I can tell at a glance it's mostly/only affecting Hetzner IPs.  Can you try doing an IPv6 traceroute to ntppool.net ?
>
> I come to the same conclusion.
>
> No problem from my SIXXS tunnel and a server at HostEurope, but problem
> from a root server at Hetzner:
>
> # traceroute6 ntppool.net
> traceroute to ntppool.net (2607:f238:2::4), 30 hops max, 80 byte packets
>   1  * * *
>   2  2a01:4f8:d16:4::1 (2a01:4f8:d16:4::1)  1.349 ms  1.258 ms  1.170 ms
>   3  hos-tr3.juniper3.rz12.hetzner.de (2a01:4f8:0:d1:3:0:12:3)  0.853 ms
> hos-tr2.juniper3.rz10.hetzner.de (2a01:4f8:0:d1:2:0:10:3)  0.774 ms
> hos-tr3.juniper3.rz12.hetzner.de (2a01:4f8:0:d1:3:0:12:3)  0.686 ms
>   4  hos-bb2.juniper4.ffm.hetzner.de (2a01:4f8:0:2::1:4)  6.173 ms  6.101
> ms  6.177 ms
>   5  30gigabitethernet4-3.core1.fra1.he.net (2001:7f8::1b1b:0:1)  6.793
> ms  6.487 ms  6.312 ms
>   6  10gigabitethernet5-3.core1.lon1.he.net (2001:470:0:1d2::1)  24.446
> ms  24.590 ms  24.507 ms
>   7  10gigabitethernet10-4.core1.nyc4.he.net (2001:470:0:128::1)  98.016
> ms  92.410 ms  107.700 ms
>   8  10gigabitethernet12-2.core1.lax1.he.net (2001:470:0:10e::1)  149.074
> ms  148.180 ms  149.227 ms
>   9  10gigabitethernet1-3.core1.lax2.he.net (2001:470:0:72::2)  147.492
> ms  147.325 ms  147.806 ms
> 10  * * *
> 11  2607:f238::cfab:1e01 (2607:f238::cfab:1e01)  160.664 ms  160.450 ms
>   160.207 ms
> 12  * * *
> 13  * * *
> (aborted with Ctrl-C after some more * * *)
>
>
> Regards, Christoph
>
>
> PS: Damn, I was thinking about moving our HostEurope host to Hetzner ...
>
> _______________________________________________
> pool mailing list
> pool at lists.ntp.org
> http://lists.ntp.org/listinfo/pool
>



More information about the pool mailing list