Ticket ID: SIXXS #3298169 Ticket Status: Remote Problem PoP: dkcph01 - Availo (Copenhagen)
Peering issue in the state of Denmark
![]()
Youletide greetings.
It seems that connectivity from your pop to easyspeedy deteriorated sometime in November. Not a huge issue, but it does generate a bit of packet drops, jitter and delay.
This is the view from tunnel id T35785 to the Copenhagen POP.
ipv4 address 82.103.129.122, ipv6 tunnel 2001:16d8:dd00:b8::/64. The pop is at 93.158.77.42.
[root@faxe ~]# ping a.nic.dk
PING a.nic.dk (212.88.78.122) 56(84) bytes of data.
64 bytes from a.nic.dk (212.88.78.122): icmp_seq=1 ttl=52 time=18.8 ms
64 bytes from a.nic.dk (212.88.78.122): icmp_seq=2 ttl=52 time=18.9 ms
--- a.nic.dk ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 18.812/18.881/18.950/0.069 ms
[root@faxe ~]# ip tun show sit8
sit8: ipv6/ip remote 93.158.77.42 local 82.103.129.122 ttl 64
[root@faxe ~]# ip addr show dev eth0
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:01:29:93:8e:e3 brd ff:ff:ff:ff:ff:ff
inet 82.103.129.122/20 brd 82.103.143.255 scope global eth0
inet 82.103.133.139/20 scope global secondary eth0
inet6 fe80::201:29ff:fe93:8ee3/64 scope link
valid_lft forever preferred_lft forever
[root@faxe ~]# ip -6 addr show dev sit8
5: sit8@NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280
inet6 2001:16d8:dd00:b8::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::5267:817a/64 scope link
valid_lft forever preferred_lft forever
[root@faxe ~]# ping 93.158.77.42
PING 93.158.77.42 (93.158.77.42) 56(84) bytes of data.
64 bytes from 93.158.77.42: icmp_seq=1 ttl=53 time=42.2 ms
64 bytes from 93.158.77.42: icmp_seq=2 ttl=53 time=42.2 ms
--- 93.158.77.42 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 42.256/42.261/42.266/0.005 ms
[root@faxe ~]# ping6 2001:16d8:dd00:b8::2
PING 2001:16d8:dd00:b8::2(2001:16d8:dd00:b8::2) 56 data bytes
64 bytes from 2001:16d8:dd00:b8::2: icmp_seq=0 ttl=64 time=0.131 ms
64 bytes from 2001:16d8:dd00:b8::2: icmp_seq=1 ttl=64 time=0.127 ms
--- 2001:16d8:dd00:b8::2 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.127/0.129/0.131/0.002 ms, pipe 2
[root@faxe ~]# ping6 2001:16d8:dd00:b8::1
PING 2001:16d8:dd00:b8::1(2001:16d8:dd00:b8::1) 56 data bytes
64 bytes from 2001:16d8:dd00:b8::1: icmp_seq=0 ttl=64 time=42.0 ms
64 bytes from 2001:16d8:dd00:b8::1: icmp_seq=1 ttl=64 time=41.9 ms
64 bytes from 2001:16d8:dd00:b8::1: icmp_seq=2 ttl=64 time=41.9 ms
--- 2001:16d8:dd00:b8::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 41.971/41.993/42.023/0.168 ms, pipe 2
[root@faxe ~]# traceroute 93.158.77.42
traceroute to 93.158.77.42 (93.158.77.42), 30 hops max, 40 byte packets
1 82.103.143.2 (82.103.143.2) 0.322 ms 0.224 ms 0.191 ms
2 gi9-4.ccr01.cph01.atlas.cogentco.com (149.6.136.81) 0.568 ms 0.581 ms 0.574 ms
3 te0-3-0-2.ccr21.ham01.atlas.cogentco.com (130.117.2.149) 6.438 ms 6.248 ms 6.260 ms
4 te0-0-0-3.mpd21.ams03.atlas.cogentco.com (130.117.50.57) 15.521 ms te0-1-0-3.ccr21.ams03.atlas.cogentco.com (130.117.50.45) 15.498 ms 15.419 ms
5 te7-4.ccr01.lon01.atlas.cogentco.com (130.117.48.141) 328.888 ms te1-2.mpd02.lon01.atlas.cogentco.com (130.117.38.125) 23.046 ms 23.118 ms
6 te2-2.mpd01.lon01.atlas.cogentco.com (130.117.1.74) 23.016 ms 23.192 ms te1-7.mpd01.lon01.atlas.cogentco.com (130.117.2.25) 22.994 ms
7 sprint.lon01.atlas.cogentco.com (130.117.15.66) 22.897 ms sl-bb22-lon-11-0-1.sprintlink.net (213.206.131.29) 22.785 ms sprint.lon01.atlas.cogentco.com (130.117.15.66) 22.763 ms
8 sl-bb20-bru-14-0-0.sprintlink.net (213.206.129.42) 23.500 ms 23.384 ms 23.342 ms
9 sl-bb21-bru-15-0-0.sprintlink.net (80.66.128.42) 23.559 ms 23.471 ms 23.688 ms
10 sl-bb20-ams-14-0-0.sprintlink.net (213.206.129.45) 23.773 ms 23.706 ms 23.600 ms
11 sl-bb21-ham-6-0-0.sprintlink.net (213.206.129.145) 29.526 ms 29.459 ms 29.448 ms
12 sl-bb21-cop-13-0-0.sprintlink.net (213.206.129.57) 34.609 ms 34.623 ms 34.523 ms
13 sl-bb21-sto-14-0-0.sprintlink.net (213.206.129.34) 31.746 ms 31.771 ms 31.717 ms
14 sl-gw10-sto-15-0-0.sprintlink.net (80.77.96.42) 31.724 ms 31.693 ms 31.686 ms
15 80.77.101.2 (80.77.101.2) 32.217 ms 32.169 ms 32.420 ms
16 te2-1-r73.cr0-r72.svv-cph.dk.p80.net (82.96.1.26) 41.822 ms 41.702 ms 41.617 ms
17 dkcph01.sixxs.net (93.158.77.42) 41.944 ms 41.966 ms 41.989 ms
[root@faxe ~]#
copenhagen-hamburg-amsterdam-london-brussels-amsterdam-hamburg-copenhagen-stockholm-copenhagen. And back, some other route.
Considering that, 42 milliseconds is not that bad.
Best regards,
Morten Reistad
mrl5-sixxs <$fornavn@$etternavn.name>
State change: remoteproblem
![]() ![]()
The state of this ticket has been changed to remoteproblem
Peering issue in the state of Denmark
Ask your local ISP to resolve their peering issues, clearly they are sending everything over transit instead.
|