SixXS::Sunset 2017-06-06

Kewlio POP having problems?
[gb] Shadow Hawkins on Tuesday, 30 March 2004 07:17:03
For the past few days my IPv6 connection through Kewlio has become pretty unusable. It's very laggy. Traceroutes seem to take quite a while to complete, and websites are pretty much impossible to get. Anyone know what's going on? Here's a couple of traceroutes: james@lister:~% traceroute6 noc.sixxs.net traceroute6 to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 3ffe:4005:1000:16::2, 30 hops max, 12 byte packets 1 kewlio 32.025 ms 32.848 ms 31.465 ms 2 dc-0-IPv6-providence.thn.kewlio.net.uk 32.415 ms 45.104 ms * 3 2001:7f8:5::3d57:1 41.477 ms * 41.981 ms 4 * ams-ix.ipv6.concepts.nl 104.407 ms * 5 se1.breda.ipv6.concepts-ict.net 44.196 ms 44.727 ms * 6 noc.sixxs.net 45.201 ms * 44.344 ms james@lister:~% traceroute6 irc.ipv6.freenode.net traceroute6 to irc.ipv6.freenode.net (2001:898:2000:3::1) from 3ffe:4005:1000:16::2, 30 hops max, 12 byte packets 1 kewlio 32.709 ms 32.284 ms 32.642 ms 2 dc-0-IPv6-providence.thn.kewlio.net.uk 165.428 ms * 32.836 ms 3 * 2001:7f8:5::52a3:1 42.604 ms * 4 * ge-0-2-0-1.core01.ipv6.int.rb.proserve.nl 41.408 ms * 5 2001:7f8:1::a500:6696:2 41.938 ms * 42.221 ms 6 * 2001:898:1000:cc::2 42.209 ms * 7 2001:898:2000:3::1 42.618 ms * 42.204 ms Note that each of these traceroutes takes >30secs to complete, and has trouble resolving a lot of the time (all of those hosts used to resolve fine) So I guess the big question is, is it my end or theirs? Cheers, James
Kewlio POP having problems?
[gb] Shadow Hawkins on Wednesday, 14 April 2004 14:17:39
I'm still having major problems with this. Is there a way I can find out if it's a problem at my end or with Kewlio? While I can "use" the v6 connection from the server holding the endpoint (albeit with very high latency), it's pretty much unusable (for example, for retrieving websites) from my workstation. Here's a traceroute from the workstation:
james@fenix:~% traceroute6 noc.sixxs.net 13:07:49 04-04-14 traceroute6 to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 3ffe:4005:1007:1::3, 64 hops max, 12 byte packets 1 lister.ipv6.jamesog.net 0.556 ms 0.400 ms 0.173 ms 2 kewlio 30.985 ms 29.435 ms 29.165 ms 3 * bge-0.2-IPv6-providence.thn.kewlio.net.uk 30.990 ms 70.602 ms 4 * 2001:7f8:5::3d57:1 36.804 ms 37.525 ms 5 * ams-ix.ipv6.concepts.nl 39.080 ms * 6 * se1.breda.ipv6.concepts-ict.net 40.886 ms * 7 noc.sixxs.net 40.249 ms * * james@fenix:~% 13:08:52 04-04-14
I can't even get this site using IPv6. It always times out and switches to v4. Would a change in POP help me? Thanks
Kewlio POP having problems?
[pl] Shadow Hawkins on Saturday, 17 April 2004 17:32:34
Unfortunetly I have the same problem. Tunnel I have set up few hours ago. Access to almost any v6 server impossible. mtr to noc.sixxs.net 2001:838:1:1:210:dcff:fe20:7c7c Packets Pings Hostname %Loss Rcv Snt Last Best Avg Worst 1. gw-34.lon-01.gb.sixxs.net 0% 684 684 60 59 63 288 2. bge-0.2-IPv6-providence.thn.kewlio.net.uk 88% 82 684 71 60 86 276 3. 2001:7f8:5::3d57:1 86% 102 684 69 68 77 235 4. ams-ix.ipv6.concepts.nl 91% 65 684 71 68 82 303 5. 2001:838:0:10::2 94% 43 684 74 71 84 299 6. 2001:838:1:1:210:dcff:fe20:7c7c 95% 40 684 73 71 88 314

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

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