SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #661510
Ticket Status: User

PoP: (not applicable)

PoP too "far" for me (ping >200ms)
[ua] Shadow Hawkins on Monday, 28 January 2008 16:40:26
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there: I have request tunnel to nlede01 PoP (ping ~70ms). But tunnel assigned to sesto01 with pings more than 230ms traceroute to sesto01.sixxs.net (82.96.56.14) 1 193.33.236.2 1.161 ms 1.039 ms 1.094 ms 2 80.91.177.133 197.610 ms 82.300 ms 200.831 ms 3 80.91.160.166 55.599 ms 68.163 ms 56.364 ms 4 81.222.4.137 56.628 ms 55.320 ms 60.183 ms 5 81.222.15.105 75.927 ms 82.825 ms 108.372 ms 6 82.96.1.65 246.603 ms 242.367 ms 234.055 ms 7 82.96.56.14 237.951 ms 234.076 ms 236.594 ms Can we change endpoint of this tunnel?
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Monday, 28 January 2008 17:08:45
Message is Locked
The state of this ticket has been changed to user
PoP too "far" for me (ping >200ms)
[ch] Jeroen Massar SixXS Staff on Monday, 28 January 2008 17:09:42
As you can see in your traceroute your first hop seems to be quite high in latency, which is most likely causing this problem.
PoP too "far" for me (ping >200ms)
[ua] Shadow Hawkins on Monday, 28 January 2008 20:50:51
problem was in the middle of 5 and 6 hops: from retn.net to se.p80.net. Now ping ~90ms.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker