Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › Low Upload Speed On Hetzner Dedicated Server
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Low Upload Speed On Hetzner Dedicated Server

umityaylaumityayla Member
in Help

Hello, any reason why I have low upload speed on my server? I tried stopping the haproxy to prevent uploading requests and rerunning the speedtest, still nothing has changed.

Retrieving speedtest.net configuration...
Testing from Hetzner Online GmbH (###.###.##.##)...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by GameAddicted (Lauterbach) [74.17 km]: 0.788 ms
Testing download speed................................................................................
Download: 872.16 Mbit/s
Testing upload speed......................................................................................................
Upload: 4.17 Mbit/s

Comments

  • LeviLevi Member

    Please provide traceroute and iperf tests to the target.

  • hyperblasthyperblast Member

    4.17 mbit/s is the speedtest.net problem. the script is broken.

  • exception0x876exception0x876 Member, Host Rep, LIR

    It is very likely an issue with speedtest on some Linux kernels. Try iperf as suggested above.

  • CConnerCConner Member, Host Rep

    Is it the case for just this host, or are you having the same issue when testing others as well?

  • umityaylaumityayla Member

    `iperf -c ping.online.net

    Client connecting to ping.online.net, TCP port 5001

    TCP window size: 85.3 KByte (default)

    [ 3] local ###.###.##.## port 42810 connected with 62.210.18.40 port 5001
    [ ID] Interval Transfer Bandwidth
    [ 3] 0.0-10.0 sec 42.0 MBytes 35.2 Mbits/sec
    `

    traceroute bouygues.iperf.fr traceroute to bouygues.iperf.fr (89.84.1.222), 30 hops max, 60 byte packets 1 static.129.115.130.94.clients.your-server.de (94.130.115.129) 0.249 ms 0.232 ms 0.266 ms 2 core23.fsn1.hetzner.com (213.239.203.229) 0.182 ms core24.fsn1.hetzner.com (213.239.203.233) 0.264 ms 0.270 ms 3 core11.nbg1.hetzner.com (213.239.203.125) 2.656 ms core12.nbg1.hetzner.com (213.239.203.121) 3.487 ms 3.487 ms 4 core6.par.hetzner.com (213.239.252.174) 16.136 ms core6.par.hetzner.com (213.239.252.254) 16.117 ms core6.par.hetzner.com (213.239.252.174) 16.132 ms 5 bouyguestelecom.par.franceix.net (37.49.236.63) 16.126 ms 16.101 ms 16.134 ms 6 62.34.2.57 (62.34.2.57) 18.752 ms 18.997 ms 18.979 ms 7 212.194.171.68 (212.194.171.68) 16.608 ms 16.602 ms 16.558 ms 8 89.89.101.141 (89.89.101.141) 16.738 ms 16.839 ms 16.951 ms 9 89.84.1.222 (89.84.1.222) 16.492 ms 16.491 ms 16.460 ms

    `iperf -c bouygues.iperf.fr

    Client connecting to bouygues.iperf.fr, TCP port 5001

    TCP window size: 85.3 KByte (default)

    [ 3] local ###.###.##.## port 39986 connected with 89.84.1.222 port 5001
    write failed: Broken pipe
    [ ID] Interval Transfer Bandwidth
    [ 3] 0.0- 0.0 sec 36.8 KBytes 17.7 Mbits/sec`

    traceroute bouygues.iperf.fr traceroute to bouygues.iperf.fr (89.84.1.222), 30 hops max, 60 byte packets 1 static.129.115.130.94.clients.your-server.de (94.130.115.129) 0.293 ms 0.280 ms 0.316 ms 2 core24.fsn1.hetzner.com (213.239.203.233) 1.464 ms core23.fsn1.hetzner.com (213.239.203.229) 0.276 ms core24.fsn1.hetzner.com (213.239.203.233) 1.458 ms 3 core11.nbg1.hetzner.com (213.239.245.225) 2.602 ms core12.nbg1.hetzner.com (213.239.203.121) 2.783 ms core11.nbg1.hetzner.com (213.239.203.125) 2.591 ms 4 core6.par.hetzner.com (213.239.252.174) 15.981 ms 15.982 ms 15.975 ms 5 bouyguestelecom.par.franceix.net (37.49.236.63) 16.125 ms 16.082 ms 16.051 ms 6 62.34.2.57 (62.34.2.57) 18.462 ms 17.932 ms 17.910 ms 7 212.194.171.68 (212.194.171.68) 16.597 ms 16.596 ms 16.486 ms 8 89.89.101.141 (89.89.101.141) 16.776 ms 16.699 ms 16.964 ms 9 89.84.1.222 (89.84.1.222) 16.362 ms 16.368 ms *

    iperf -c iperf.volia.net

    Client connecting to iperf.volia.net, TCP port 5001

    TCP window size: 85.3 KByte (default)

    [ 3] local ###.###.##.## port 42138 connected with 77.120.3.236 port 5001
    [ ID] Interval Transfer Bandwidth
    [ 3] 0.0-10.0 sec 41.8 MBytes 35.0 Mbits/sec

    traceroute iperf.volia.net traceroute to iperf.volia.net (77.120.3.236), 30 hops max, 60 byte packets 1 static.129.115.130.94.clients.your-server.de (94.130.115.129) 0.265 ms 0.250 ms 0.291 ms 2 core24.fsn1.hetzner.com (213.239.203.233) 0.230 ms 0.238 ms 0.288 ms 3 juniper4.nbg1.hetzner.com (213.239.252.233) 3.217 ms 3.223 ms juniper5.nbg1.hetzner.com (213.239.252.245) 2.619 ms 4 nug-b1-link.telia.net (62.115.183.232) 3.752 ms nug-b1-link.telia.net (213.248.70.0) 3.745 ms 3.860 ms 5 ffm-bb3-link.telia.net (62.115.113.146) 6.024 ms 6.016 ms 6.008 ms 6 ffm-b5-link.telia.net (62.115.114.89) 5.420 ms 5.385 ms 5.392 ms 7 be3031.agr41.fra03.atlas.cogentco.com (130.117.14.197) 5.581 ms 5.516 ms 5.884 ms 8 be3187.ccr42.fra03.atlas.cogentco.com (130.117.1.118) 5.530 ms 5.783 ms be3186.ccr41.fra03.atlas.cogentco.com (130.117.0.1) 5.534 ms 9 be2959.ccr21.muc03.atlas.cogentco.com (154.54.36.54) 10.973 ms 11.358 ms be2960.ccr22.muc03.atlas.cogentco.com (154.54.36.254) 11.179 ms 10 be2974.ccr51.vie01.atlas.cogentco.com (154.54.58.6) 16.903 ms be3462.ccr52.vie01.atlas.cogentco.com (154.54.59.181) 17.221 ms be2974.ccr51.vie01.atlas.cogentco.com (154.54.58.6) 17.071 ms 11 be2988.ccr21.bts01.atlas.cogentco.com (154.54.59.85) 18.653 ms 18.692 ms be3463.ccr22.bts01.atlas.cogentco.com (154.54.59.186) 18.140 ms 12 be2046.rcr21.kbp01.atlas.cogentco.com (154.54.58.246) 34.730 ms 34.690 ms 34.694 ms 13 volia.demarc.cogentco.com (149.6.190.250) 34.681 ms volia.demarc.cogentco.com (149.6.190.26) 34.727 ms volia.demarc.cogentco.com (149.6.190.250) 34.610 ms 14 v193.po2.agg-1.r27.kiev.volia.net (77.120.1.30) 34.729 ms lag45-40g.agg-1.r27.kiev.volia.net (77.120.1.34) 34.713 ms 34.806 ms 15 speedtest.volia.com (77.120.3.236) 34.631 ms 34.667 ms 34.621 ms

  • umityaylaumityayla Member

    @CConner said:
    Is it the case for just this host, or are you having the same issue when testing others as well?

    when I tested with another machine of mine (who is in hetzner); it shows me a good upload connection speed

  • LeviLevi Member

    Send iperf test results to herzner support. they are fast to respond to such issue.

    Thanked by 1Hetzner_OL
  • dragon1993dragon1993 Member

    Do you use BBR?

  • FoxelVoxFoxelVox Member

    Try this:
    wget -O speedtest-cli https://raw.githubusercontent.com/sivel/speedtest-cli/master/speedtest.py ; chmod +x speedtest-cli ; ./speedtest-cli --share

    Or alternatively, try:
    apt install iperf -y && iperf -c cloudflare.com -p 443 -P 10

  • SpeedBusSpeedBus Member, Host Rep

    It's a bug in the speedtest-cli script when you use it with BBR, another user reported the same issue on Github with the very same speed (4.17 Mbit/s)

    https://github.com/sivel/speedtest-cli/issues/605

  • dragon1993dragon1993 Member

    @SpeedBus said:
    It's a bug in the speedtest-cli script when you use it with BBR, another user reported the same issue on Github with the very same speed (4.17 Mbit/s)

    https://github.com/sivel/speedtest-cli/issues/605

    I think it's BBR and not speedtest bug

  • JordJord Moderator, Host Rep

    Just use the official one, it works great.

    https://www.speedtest.net/apps/cli

  • DrMythnickDrMythnick Member

    @Jord said:
    Just use the official one, it works great.

    https://www.speedtest.net/apps/cli

    BINGO !

  • JordJord Moderator, Host Rep

    @DrMythnick said:

    @Jord said:
    Just use the official one, it works great.

    https://www.speedtest.net/apps/cli

    BINGO !

    Was His Name-O

Sign In or Register to comment.