Helft mir doch mal eben bitte, OpenBSD.amsterdam zu debuggen.

dettus · 30 August 2024

Hey hey!

(I am writing this in English, so that I can give mischa@ a link to this thread...)
So, I am under the impression that openbsd.amsterdam has gotten slower.

I did a couple of experiments, and it looks like it actually depends on the size of some packages.
So I tried pinging: (Telekom)

Code:

; ping -c 10  openbsd.amsterdam
PING openbsd.amsterdam (46.23.88.15): 56 data bytes
64 bytes from 46.23.88.15: icmp_seq=0 ttl=246 time=11.354 ms
64 bytes from 46.23.88.15: icmp_seq=1 ttl=246 time=11.398 ms
64 bytes from 46.23.88.15: icmp_seq=2 ttl=246 time=11.028 ms
64 bytes from 46.23.88.15: icmp_seq=3 ttl=246 time=11.367 ms
64 bytes from 46.23.88.15: icmp_seq=4 ttl=246 time=11.384 ms
64 bytes from 46.23.88.15: icmp_seq=5 ttl=246 time=11.052 ms
64 bytes from 46.23.88.15: icmp_seq=6 ttl=246 time=11.413 ms
64 bytes from 46.23.88.15: icmp_seq=7 ttl=246 time=11.048 ms
64 bytes from 46.23.88.15: icmp_seq=8 ttl=246 time=11.365 ms
64 bytes from 46.23.88.15: icmp_seq=9 ttl=246 time=11.427 ms

--- openbsd.amsterdam ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 11.028/11.284/11.427/0.159 ms


; ping -c 10 -s 8192 openbsd.amsterdam
PING openbsd.amsterdam (46.23.88.15): 8192 data bytes
8200 bytes from 46.23.88.15: icmp_seq=0 ttl=246 time=12.085 ms
8200 bytes from 46.23.88.15: icmp_seq=1 ttl=246 time=12.200 ms
8200 bytes from 46.23.88.15: icmp_seq=2 ttl=246 time=11.878 ms

--- openbsd.amsterdam ping statistics ---
10 packets transmitted, 3 packets received, 70.0% packet loss
round-trip min/avg/max/std-dev = 11.878/12.054/12.200/0.133 ms

Apparently, some of the larger packages are getting lost along the way. This is consistent with the slower download time I experienced.
To rule out an issue with my connection at home, I tried:

Code:

; ping -c 10 -s 8192 npo.nl
ping: Warning: npo.nl has multiple addresses; using 3.165.232.82
PING npo.nl (3.165.232.82): 8192 data bytes
8200 bytes from 3.165.232.82: icmp_seq=0 ttl=248 time=27.443 ms
8200 bytes from 3.165.232.82: icmp_seq=1 ttl=248 time=27.288 ms
8200 bytes from 3.165.232.82: icmp_seq=2 ttl=248 time=27.377 ms
8200 bytes from 3.165.232.82: icmp_seq=3 ttl=248 time=27.277 ms
8200 bytes from 3.165.232.82: icmp_seq=4 ttl=248 time=27.357 ms
8200 bytes from 3.165.232.82: icmp_seq=5 ttl=248 time=27.332 ms
8200 bytes from 3.165.232.82: icmp_seq=6 ttl=248 time=27.298 ms
8200 bytes from 3.165.232.82: icmp_seq=7 ttl=248 time=27.298 ms
8200 bytes from 3.165.232.82: icmp_seq=8 ttl=248 time=27.376 ms
8200 bytes from 3.165.232.82: icmp_seq=9 ttl=248 time=27.363 ms

--- npo.nl ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 27.277/27.341/27.443/0.049 ms

MAY I BOTHER you guys to also ping his website, as well as some other pages, and post the results here?

CommanderZed · 30 August 2024

I'll try my best

From my home router (Deutsche Glasfaser):

router-1$ ping -c 10 openbsd.amsterdam
PING openbsd.amsterdam (46.23.88.15): 56 data bytes
64 bytes from 46.23.88.15: icmp_seq=0 ttl=246 time=30.245 ms
64 bytes from 46.23.88.15: icmp_seq=1 ttl=246 time=30.522 ms
64 bytes from 46.23.88.15: icmp_seq=2 ttl=246 time=30.677 ms
64 bytes from 46.23.88.15: icmp_seq=3 ttl=246 time=30.399 ms
64 bytes from 46.23.88.15: icmp_seq=4 ttl=246 time=30.355 ms
64 bytes from 46.23.88.15: icmp_seq=5 ttl=246 time=30.287 ms
64 bytes from 46.23.88.15: icmp_seq=6 ttl=246 time=30.450 ms
64 bytes from 46.23.88.15: icmp_seq=7 ttl=246 time=30.356 ms
64 bytes from 46.23.88.15: icmp_seq=8 ttl=246 time=30.349 ms
64 bytes from 46.23.88.15: icmp_seq=9 ttl=246 time=30.504 ms

router-1$ ping -c 10 -s 8192 openbsd.amsterdam
PING openbsd.amsterdam (46.23.88.15): 8192 data bytes
8200 bytes from 46.23.88.15: icmp_seq=0 ttl=246 time=32.922 ms
8200 bytes from 46.23.88.15: icmp_seq=1 ttl=246 time=32.791 ms
8200 bytes from 46.23.88.15: icmp_seq=2 ttl=246 time=32.813 ms
8200 bytes from 46.23.88.15: icmp_seq=3 ttl=246 time=33.344 ms
8200 bytes from 46.23.88.15: icmp_seq=4 ttl=246 time=33.231 ms
8200 bytes from 46.23.88.15: icmp_seq=5 ttl=246 time=33.090 ms
8200 bytes from 46.23.88.15: icmp_seq=6 ttl=246 time=32.888 ms
8200 bytes from 46.23.88.15: icmp_seq=7 ttl=246 time=33.077 ms
8200 bytes from 46.23.88.15: icmp_seq=8 ttl=246 time=33.068 ms
8200 bytes from 46.23.88.15: icmp_seq=9 ttl=246 time=33.160 ms

router-1$ ping -c 10 -s 8192 npo.nl
ping: Warning: npo.nl has multiple addresses; using 3.165.232.82
PING npo.nl (3.165.232.82): 8192 data bytes
8200 bytes from 3.165.232.82: icmp_seq=0 ttl=245 time=49.118 ms
8200 bytes from 3.165.232.82: icmp_seq=1 ttl=245 time=48.728 ms
8200 bytes from 3.165.232.82: icmp_seq=2 ttl=245 time=49.393 ms
8200 bytes from 3.165.232.82: icmp_seq=3 ttl=245 time=49.083 ms
8200 bytes from 3.165.232.82: icmp_seq=4 ttl=245 time=49.259 ms
8200 bytes from 3.165.232.82: icmp_seq=5 ttl=245 time=48.753 ms
8200 bytes from 3.165.232.82: icmp_seq=6 ttl=245 time=49.109 ms
8200 bytes from 3.165.232.82: icmp_seq=7 ttl=245 time=48.814 ms
8200 bytes from 3.165.232.82: icmp_seq=8 ttl=245 time=49.068 ms
8200 bytes from 3.165.232.82: icmp_seq=9 ttl=245 time=48.975 ms

--- npo.nl ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 48.728/49.030/49.393/0.205 ms

And from my VPS at netcup

ping -c 10 openbsd.amsterdam
PING openbsd.amsterdam (46.23.88.15): 56 data bytes
64 bytes from 46.23.88.15: icmp_seq=0 ttl=247 time=11.230 ms
64 bytes from 46.23.88.15: icmp_seq=1 ttl=247 time=10.748 ms
64 bytes from 46.23.88.15: icmp_seq=2 ttl=247 time=10.676 ms
64 bytes from 46.23.88.15: icmp_seq=3 ttl=247 time=10.608 ms
64 bytes from 46.23.88.15: icmp_seq=4 ttl=247 time=10.663 ms
64 bytes from 46.23.88.15: icmp_seq=5 ttl=247 time=10.829 ms
64 bytes from 46.23.88.15: icmp_seq=6 ttl=247 time=10.670 ms
64 bytes from 46.23.88.15: icmp_seq=7 ttl=247 time=10.714 ms
64 bytes from 46.23.88.15: icmp_seq=8 ttl=247 time=11.401 ms
64 bytes from 46.23.88.15: icmp_seq=9 ttl=247 time=10.675 ms

--- openbsd.amsterdam ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 10.608/10.822/11.401/0.256 ms

--- openbsd.amsterdam ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 10.608/10.822/11.401/0.256 ms
jana@mailx-1:/home/jana $ ping -c 10 -s 8192 openbsd.amsterdam
PING openbsd.amsterdam (46.23.88.15): 8192 data bytes
8200 bytes from 46.23.88.15: icmp_seq=0 ttl=247 time=10.719 ms
8200 bytes from 46.23.88.15: icmp_seq=1 ttl=247 time=10.674 ms
8200 bytes from 46.23.88.15: icmp_seq=2 ttl=247 time=10.886 ms
8200 bytes from 46.23.88.15: icmp_seq=3 ttl=247 time=10.927 ms
8200 bytes from 46.23.88.15: icmp_seq=4 ttl=247 time=10.739 ms
8200 bytes from 46.23.88.15: icmp_seq=5 ttl=247 time=10.849 ms
8200 bytes from 46.23.88.15: icmp_seq=6 ttl=247 time=10.798 ms
8200 bytes from 46.23.88.15: icmp_seq=7 ttl=247 time=10.673 ms
8200 bytes from 46.23.88.15: icmp_seq=8 ttl=247 time=10.799 ms
8200 bytes from 46.23.88.15: icmp_seq=9 ttl=247 time=10.810 ms

--- openbsd.amsterdam ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 10.673/10.788/10.927/0.082 ms

And for the record ipv6 from home:

10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 48.728/49.030/49.393/0.205 ms
router-1$ ping6 -c 10 -s 8192 openbsd.amsterdam
PING openbsd.amsterdam (2a03:6000:880::15): 8192 data bytes
8200 bytes from 2a03:6000:880::15: icmp_seq=0 hlim=55 time=33.016 ms
8200 bytes from 2a03:6000:880::15: icmp_seq=1 hlim=55 time=33.340 ms
8200 bytes from 2a03:6000:880::15: icmp_seq=2 hlim=55 time=33.397 ms
8200 bytes from 2a03:6000:880::15: icmp_seq=3 hlim=55 time=33.350 ms
8200 bytes from 2a03:6000:880::15: icmp_seq=4 hlim=55 time=33.376 ms
8200 bytes from 2a03:6000:880::15: icmp_seq=5 hlim=55 time=33.363 ms
8200 bytes from 2a03:6000:880::15: icmp_seq=6 hlim=55 time=33.443 ms
8200 bytes from 2a03:6000:880::15: icmp_seq=7 hlim=55 time=33.369 ms
8200 bytes from 2a03:6000:880::15: icmp_seq=8 hlim=55 time=33.387 ms
8200 bytes from 2a03:6000:880::15: icmp_seq=9 hlim=55 time=33.391 ms

--- openbsd.amsterdam ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 33.016/33.343/33.443/0.112 ms

medV2 · 30 August 2024

Some Pings from Austria:

Code:

ping -c 10  openbsd.amsterdam
PING openbsd.amsterdam (46.23.88.15) 56(84) bytes of data.
64 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=1 ttl=242 time=67.7 ms
64 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=2 ttl=242 time=66.3 ms
64 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=3 ttl=242 time=64.8 ms
64 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=4 ttl=242 time=63.5 ms
64 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=5 ttl=242 time=62.3 ms
64 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=6 ttl=242 time=62.7 ms
64 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=7 ttl=242 time=60.7 ms
64 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=8 ttl=242 time=58.4 ms
64 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=9 ttl=242 time=57.0 ms
64 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=10 ttl=242 time=55.8 ms

--- openbsd.amsterdam ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 55.772/61.914/67.661/3.722 ms


ping -c 10 -s 8192 openbsd.amsterdam
PING openbsd.amsterdam (46.23.88.15) 8192(8220) bytes of data.
8200 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=1 ttl=242 time=83.3 ms
8200 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=2 ttl=242 time=83.3 ms
8200 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=3 ttl=242 time=81.5 ms
8200 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=4 ttl=242 time=78.1 ms
8200 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=5 ttl=242 time=76.3 ms
8200 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=6 ttl=242 time=75.5 ms
8200 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=7 ttl=242 time=74.0 ms
8200 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=8 ttl=242 time=80.1 ms
8200 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=9 ttl=242 time=71.3 ms
8200 bytes from openbsd.amsterdam (46.23.88.15): icmp_seq=10 ttl=242 time=69.5 ms

--- openbsd.amsterdam ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9016ms
rtt min/avg/max/mdev = 69.469/77.287/83.313/4.591 ms


ping -c 10 -s 8192 npo.nl
PING npo.nl (3.165.232.56) 8192(8220) bytes of data.
8200 bytes from server-3-165-232-56.dub56.r.cloudfront.net (3.165.232.56): icmp_seq=1 ttl=236 time=89.7 ms
8200 bytes from server-3-165-232-56.dub56.r.cloudfront.net (3.165.232.56): icmp_seq=2 ttl=236 time=88.2 ms
8200 bytes from server-3-165-232-56.dub56.r.cloudfront.net (3.165.232.56): icmp_seq=3 ttl=236 time=85.7 ms
8200 bytes from server-3-165-232-56.dub56.r.cloudfront.net (3.165.232.56): icmp_seq=4 ttl=236 time=84.6 ms
8200 bytes from server-3-165-232-56.dub56.r.cloudfront.net (3.165.232.56): icmp_seq=5 ttl=236 time=83.0 ms
8200 bytes from server-3-165-232-56.dub56.r.cloudfront.net (3.165.232.56): icmp_seq=6 ttl=236 time=88.1 ms
8200 bytes from server-3-165-232-56.dub56.r.cloudfront.net (3.165.232.56): icmp_seq=7 ttl=236 time=88.8 ms
8200 bytes from server-3-165-232-56.dub56.r.cloudfront.net (3.165.232.56): icmp_seq=8 ttl=236 time=80.0 ms
8200 bytes from server-3-165-232-56.dub56.r.cloudfront.net (3.165.232.56): icmp_seq=9 ttl=236 time=78.8 ms
8200 bytes from server-3-165-232-56.dub56.r.cloudfront.net (3.165.232.56): icmp_seq=10 ttl=236 time=84.6 ms

--- npo.nl ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9013ms
rtt min/avg/max/mdev = 78.828/85.162/89.663/3.511 ms

dettus · 30 August 2024

May I bother you guys to add a traceroute as well?

Code:

traceroute to openbsd.amsterdam (46.23.88.15), 64 hops max, 40 byte packets
 1  holzbrettchen (192.168.23.5)  0.315 ms  0.248 ms  0.294 ms
 2  p5092800b.dip0.t-ipconnect.de (80.146.128.11)  1.734 ms  1.05 ms  1.62 ms
 3  f-ed12-i.F.DE.NET.DTAG.DE (217.5.116.178)  6.854 ms  6.421 ms  6.562 ms
 4  f-ed12-i.F.DE.NET.DTAG.DE (217.5.116.178)  6.039 ms  6.402 ms  6.235 ms
 5  62.157.249.186 (62.157.249.186)  5.296 ms  5.888 ms  5.176 ms
 6  ae-3.r21.frnkge13.de.bb.gin.ntt.net (129.250.3.28)  12.604 ms  5.794 ms  16.585 ms
 7  ae-7.r21.amstnl07.nl.bb.gin.ntt.net (129.250.3.77)  25.184 ms  10.974 ms  10.738 ms
 8  ae-1.a00.amstnl09.nl.bb.gin.ntt.net (129.250.2.233)  12.285 ms  12.692 ms  26.708 ms
 9  ntt-100G.a2b-internet.com (81.20.69.70)  10.892 ms  10.832 ms  11.039 ms
10  219-4-244-46.a2b-internet.com (46.244.4.219)  12.529 ms *  12.024 ms
11  openbsd.amsterdam (46.23.88.15)  10.874 ms  11.256 ms  10.4 ms

When I ping each of those IP addresses individually, the losses start somewhere between 129.250.3.28 (0% loss) and 81.20.69.70 (70% loss)

medV2 · 30 August 2024

Code:

traceroute to openbsd.amsterdam (46.23.88.15), 30 hops max, 60 byte packets
 1  _gateway (192.168.0.1)  0.456 ms  0.395 ms  0.336 ms
 2  172.18.176.1 (172.18.176.1)  13.504 ms  13.719 ms  14.048 ms
 3  lilzgate01a-LG02-E6000-pri.liwest.at (212.33.34.105)  13.404 ms  13.836 ms  14.222 ms
 4  mcn-b1-link.ip.twelve99.net (213.248.74.70)  27.473 ms  27.416 ms  27.560 ms
 5  ffm-bb2-link.ip.twelve99.net (62.115.136.38)  32.161 ms  32.042 ms  32.263 ms
 6  * * ffm-b11-link.ip.twelve99.net (62.115.124.119)  76.671 ms
 7  gtt-ic-342859.ip.twelve99-cust.net (62.115.172.123)  76.536 ms  29.468 ms  29.953 ms
 8  ae3.cr4-ams1.ip4.gtt.net (89.149.181.54)  30.531 ms  42.584 ms  41.989 ms
 9  ip4.gtt.net (154.14.67.30)  32.457 ms  33.302 ms  36.935 ms
10  163-6-244-46.a2b-internet.com (46.244.6.163)  37.593 ms  36.920 ms  38.905 ms
11  openbsd.amsterdam (46.23.88.15)  36.341 ms  39.303 ms  39.218 ms

I also pinged the IPs 81.20.69.70 and 46.244.4.219 (with -s 8192), 0% loss.

Yamagi · 30 August 2024

dettus schrieb:
So I tried pinging: (Telekom)

No need to read further: Deutsche Telekom and it's broken peering (policy).

-Nuke- · 31 August 2024

Yamagi schrieb:
No need to read further: Deutsche Telekom and it's broken peering (policy).

Correct. If you want to have a datacenter / server that has a good connection to Telekom customers you need to pay them.

dettus · 31 August 2024

Strange, this morning, I treated myself to a new IP address, and it worked....

Code:

ping -c 10 -s 8192 openbsd.amsterdam
PING openbsd.amsterdam (46.23.88.15): 8192 data bytes
8200 bytes from 46.23.88.15: icmp_seq=0 ttl=246 time=13.054 ms
8200 bytes from 46.23.88.15: icmp_seq=1 ttl=246 time=12.885 ms
8200 bytes from 46.23.88.15: icmp_seq=2 ttl=246 time=12.878 ms
8200 bytes from 46.23.88.15: icmp_seq=3 ttl=246 time=13.051 ms
8200 bytes from 46.23.88.15: icmp_seq=4 ttl=246 time=13.082 ms
8200 bytes from 46.23.88.15: icmp_seq=5 ttl=246 time=13.067 ms
8200 bytes from 46.23.88.15: icmp_seq=6 ttl=246 time=13.017 ms
8200 bytes from 46.23.88.15: icmp_seq=7 ttl=246 time=13.030 ms
8200 bytes from 46.23.88.15: icmp_seq=8 ttl=246 time=13.006 ms
8200 bytes from 46.23.88.15: icmp_seq=9 ttl=246 time=13.033 ms

--- openbsd.amsterdam ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 12.878/13.010/13.082/0.068 ms

However, I disagree with your assesment, I do not think that Telekom is to blame. My money is on NTT.
Does not matter: It should not have happened. But I do not think that I am the person with enough power to change it.

-Nuke- · 31 August 2024

dettus schrieb:
However, I disagree with your assesment, I do not think that Telekom is to blame. My money is on NTT.

Depends on how you look at it. Telekom is saying: Pay us extra and our customers get the fast lane to your servers. If not it will be slow. Sure... you can blame the datacenter for not paying them.

See i.e. https://www.golem.de/news/hetzner-u...-anbindung-an-telekom-kunden-1511-117711.html

It is an old article. Some time ago Hetzner surrendered and made a deal with Telekom.

double-p · 31 August 2024

and not a new thing with -T- for sure. back in the days when Strato started growing,
-T- refused to peer that at DE-CIX but only announced in Hanover - at staggering 10Mbit/s (a typical peering was 100+ in DE-CIX at the time).
Every evening, T-users complaining that their websites at Strato are slow af. -T- doesn't care, they want ze monies -- even if they're the lower tier
at the CIX!

Yamagi · 31 August 2024

In the end it doesn't matter if the Telekom or the other carriers are to blame. Fact is that the Telekom hasn't got direct peering to several big carriers and connectivity providers. For example the Telekom doesn't directly peer with Cloudflare - https://bgp.he.net/AS3320#_asinfo - rendering Telekom <-> Cloudfare connections nearly unuseable during peek hours. They have direct peering with NTT, though.

This is NordischNet, which is a brand of GVG Glasfaser which in turn is a reseller of white label services provided by a third party. The service provider might be OpenXS, but I'm not really sure:

Code:

PING openbsd.amsterdam (2a03:6000:880::15) 56 Datenbytes
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=1 ttl=53 Zeit=11.4 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=2 ttl=53 Zeit=13.1 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=3 ttl=53 Zeit=14.2 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=4 ttl=53 Zeit=11.1 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=5 ttl=53 Zeit=14.1 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=6 ttl=53 Zeit=14.1 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=7 ttl=53 Zeit=12.6 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=8 ttl=53 Zeit=12.0 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=9 ttl=53 Zeit=12.6 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=10 ttl=53 Zeit=13.1 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=11 ttl=53 Zeit=13.4 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=12 ttl=53 Zeit=12.8 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=13 ttl=53 Zeit=13.3 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=14 ttl=53 Zeit=13.6 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=15 ttl=53 Zeit=14.6 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=16 ttl=53 Zeit=10.7 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=17 ttl=53 Zeit=13.4 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=18 ttl=53 Zeit=11.5 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=19 ttl=53 Zeit=15.2 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=20 ttl=53 Zeit=12.8 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=21 ttl=53 Zeit=12.7 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=22 ttl=53 Zeit=12.9 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=23 ttl=53 Zeit=13.8 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=24 ttl=53 Zeit=12.2 ms
64 Bytes von obsdams.openbsd.amsterdam (2a03:6000:880::15): icmp_seq=25 ttl=53 Zeit=12.3 ms

--- openbsd.amsterdam ping-Statistik ---
25 Pakete übertragen, 25 empfangen, 0% packet loss, time 24037ms
rtt min/avg/max/mdev = 10.677/12.936/15.188/1.069 ms

Code:

traceroute to openbsd.amsterdam (46.23.88.15), 30 hops max, 60 byte packets
 1  _gateway (192.168.178.1)  1.765 ms  1.630 ms  1.539 ms
 2  100.83.142.45 (100.83.142.45)  7.499 ms  7.412 ms  7.327 ms
 3  100.83.140.18 (100.83.140.18)  7.239 ms  7.147 ms  7.059 ms
 4  et-1-0-19.edge4.hamburg1.level3.net (62.67.25.37)  6.970 ms  9.508 ms  9.403 ms
 5  ae2.3204.edge7.ams1.neo.colt.net (171.75.9.210)  13.981 ms  15.247 ms  15.159 ms
 6  ntt-level3-200g.amsterdam1.level3.net (4.68.37.174)  13.742 ms  13.764 ms  13.630 ms
 7  ae-3.r21.amstnl07.nl.bb.gin.ntt.net (129.250.7.88)  13.531 ms  13.341 ms ae-2.r22.amstnl07.nl.bb.gin.ntt.net (129.250.2.92)  13.223 ms
 8  ae-0.a00.amstnl09.nl.bb.gin.ntt.net (129.250.2.163)  14.250 ms ae-1.a00.amstnl09.nl.bb.gin.ntt.net (129.250.2.233)  13.107 ms ae-0.a00.amstnl09.nl.bb.gin.ntt.net (129.250.2.163)  14.140 ms
 9  ntt-100g.a2b-internet.com (81.20.69.70)  13.001 ms  14.033 ms  16.134 ms
10  219-4-244-46.a2b-internet.com (46.244.4.219)  14.783 ms  14.759 ms  14.737 ms
11  openbsd.amsterdam (46.23.88.15)  14.715 ms  14.693 ms  14.672 ms

However, about 10:45 on a saturday morning is the wrong time of the day to debug such problems. It's better to wait for the peek hours in the evening when the whole country wants to surf the web, download games and stream movies.

Yamagi · 31 August 2024

Gnaa, pinging IPv6 and tracing IPv4 is useless:

Code:

traceroute to openbsd.amsterdam (2a03:6000:880::15), 30 hops max, 80 byte packets
 1  fritz.box (2a01:41e1:6312:2c00:3e37:12ff:fe07:92fc)  1.877 ms  1.845 ms  1.826 ms
 2  2a01:41e1:f000::3 (2a01:41e1:f000::3)  7.524 ms  7.506 ms  7.488 ms
 3  * * *
 4  2a01:41e1:f000::5 (2a01:41e1:f000::5)  7.415 ms  7.397 ms  7.380 ms
 5  et-0-0-59.edge1.hamburg1.level3.net (2001:1900:5:2:2::8d91)  11.825 ms  11.808 ms  11.790 ms
 6  2001:1900:2::3:17 (2001:1900:2::3:17)  15.893 ms  12.640 ms  12.605 ms
 7  ntt-level3-200g.amsterdam1.level3.net (2001:1900:5:3::4b6)  23.440 ms  12.526 ms  12.467 ms
 8  ae-3.r21.amstnl07.nl.bb.gin.ntt.net (2001:728:0:2000::211)  15.737 ms  13.414 ms ae-2.r22.amstnl07.nl.bb.gin.ntt.net (2001:728:0:2000::1c9)  11.190 ms
 9  ae-1.a00.amstnl09.nl.bb.gin.ntt.net (2001:728:0:2000::2a6)  36.143 ms  12.321 ms ae-0.a00.amstnl09.nl.bb.gin.ntt.net (2001:728:0:2000::2a2)  16.668 ms
10  ntt-100g-v6.a2b-internet.com (2001:728:0:5000::182)  15.568 ms  15.486 ms  15.411 ms
11  2a02:1668:a2b:1350::3 (2a02:1668:a2b:1350::3)  15.380 ms  15.349 ms  11.802 ms
12  obsdams.openbsd.amsterdam (2a03:6000:880::15)  14.908 ms  14.806 ms  14.745 ms

Nevertheless, the general route taken is the same.

double-p · 31 August 2024

within NL/amsterdam - via NTT

Code:

 Host                                                                            Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. AS20857  l9.ams4.transip.net                                                  0.0%    20   15.1  21.0   5.0  98.1  25.1
 2. AS20857  l9.f1.ams4.transip.net                                               0.0%    20   21.8  19.0  11.9  60.0  10.2
 3. AS20857  f1.r1.ams0.transip.net                                               0.0%    20    0.4   0.6   0.3   2.3   0.5
 4. AS20857  r1-a0.e1.ams7.transip.net                                            0.0%    20    0.6   0.7   0.5   3.0   0.6
 5. AS2914   213.198.92.21                                                        0.0%    20    1.0   1.4   0.9   5.3   1.1
 6. AS2914   ae-2.r22.amstnl07.nl.bb.gin.ntt.net                                  0.0%    20    0.9   0.9   0.8   1.0   0.1
 7. AS2914   ae-0.a00.amstnl09.nl.bb.gin.ntt.net                                  0.0%    20    1.7   2.7   1.5  10.0   2.6
 8. AS2914   ntt-100G.a2b-internet.com                                            0.0%    20    1.4   1.5   1.2   3.2   0.4
 9. AS51088  219-4-244-46.a2b-internet.com                                        0.0%    20    1.3   1.4   1.3   1.4   0.0
10. AS60131  openbsd.amsterdam                                                    0.0%    20    1.3   1.4   1.3   2.2   0.2

mark05 · 2 September 2024

hi

try ping -c 10 -s 8192 -D openbsd.amsterdam

i think there is an Fragmentation issue in the path.

Holger

turrican · 2 September 2024

Globalping - maybe a useful tool in such situations:

globalping

globalping cli

Helft mir doch mal eben bitte, OpenBSD.amsterdam zu debuggen.

dettus

Bicycle User

CommanderZed

OpenBSD User

medV2

Well-Known Member

dettus

Bicycle User

medV2

Well-Known Member

Yamagi

Possessed With Psi Powers

-Nuke-

Well-Known Member

dettus

Bicycle User

-Nuke-

Well-Known Member

double-p

BOFH

Yamagi

Possessed With Psi Powers

Yamagi

Possessed With Psi Powers

double-p

BOFH

mark05

Well-Known Member

turrican

Well-Known Member

Wir schützen deine Privatsphäre