1276906 - Intermittent slowdown on IPv4 versus IPv6

Status: RESOLVED WORKSFORME

(Infrastructure & Operations Graveyard :: NetOps: Office Other, task)

Description

[Frederik Braun [:freddy]]

I am connected using Ethernet.
Downloading via IPv4 is slower than v6, but bearable.
It was really  *bad* on IPv4 (and only IPv4) about two hours ago.

Here's what I did to test just now:
> $ LANG=CC wget -6 -O /dev/null http://mirror.leaseweb.com/speedtest/100mb.bin
> --2016-05-31 14:29:02--  http://mirror.leaseweb.com/speedtest/100mb.bin
> Resolving mirror.leaseweb.com (mirror.leaseweb.com)... 2a00:c98:2030:a034::21
> Connecting to mirror.leaseweb.com (mirror.leaseweb.com)|2a00:c98:2030:a034::21|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 100000000 (95M) [application/octet-stream]
> Saving to: '/dev/null'
> 
> /dev/null               100%[===============================>]  95.37M  7.32MB/s   in 12s    
> 
> 2016-05-31 14:29:14 (7.94 MB/s) - '/dev/null' saved [100000000/100000000]
Then v4:
>$ LANG=CC wget -4 -O /dev/null http://mirror.leaseweb.com/speedtest/100mb.bin
> --2016-05-31 14:29:17--  http://mirror.leaseweb.com/speedtest/100mb.bin
> Resolving mirror.leaseweb.com (mirror.leaseweb.com)... 37.58.58.140
> Connecting to mirror.leaseweb.com (mirror.leaseweb.com)|37.58.58.140|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 100000000 (95M) [application/octet-stream]
> Saving to: '/dev/null'
> 
> /dev/null                56%[================>               ]  53.62M   914KB/s   eta 27s   
> ^C


Two hours ago:
> $ wget -4 -O /dev/null http://mirror.leaseweb.com/speedtest/100mb.bin--
> /dev/null                34%[=========>                      ]  32,71M   979KB/s   eta 46s   
> ^C
> $ wget -6 -O /dev/null http://mirror.leaseweb.com/speedtest/100mb.bin
> /dev/null               100%[===============================>]  95,37M  8,84MB/s   in 10s    
> 2016-05-31 12:39:50 (9,30 MB/s) - »/dev/null« gespeichert [100000000/100000000]

Comment 1

[Peter Radcliffe [:pir]]

The output of mtr or traceroute would likely be very useful here.

Comment 2

[Frederik Braun [:freddy]]

Thank you for taking a look.

Both IPv4 and IPv6 seem to be in Frankfurt, which is where DECIX is:
Here's ping and traceroute for v6:
> $ LANG=CC tracepath6 mirror.leaseweb.com
>  1?: [LOCALHOST]                        0.015ms pmtu 1500
>  1:  2a04:a40:1000:e0::1                                   0.629ms asymm  2 
>  1:  2a04:a40:1000:e0::1                                   0.577ms asymm  2 
>  2:  2a04:a40::100:1:1                                     1.963ms 
>  3:  2a04:a40::1:920:20                                    2.681ms 
>  4:  2a04:a40::3:21:1                                      2.321ms 
>  5:  peering.evo.leaseweb.net                             18.789ms 
>  6:  2a03:2280::31:9                                      20.353ms 
>  7:  2a00:c98::6                                          29.266ms asymm 11 
>  8:  2a00:c98::59                                         29.523ms asymm 12 
>  9:  2a00:c98::178:162:223:195                            51.213ms asymm 13 
> 10:  no reply
> 11:  no reply
> 12:  no reply
> 13:  no reply
> ^C
> $ LANG=CC ping6 -c2 mirror.leaseweb.com
> PING mirror.leaseweb.com(mirror.fra1.de.leaseweb.net) 56 data bytes
> 64 bytes from mirror.fra1.de.leaseweb.net: icmp_seq=1 ttl=51 time=28.7 ms
> 64 bytes from mirror.fra1.de.leaseweb.net: icmp_seq=2 ttl=51 time=28.6 ms
> 
> --- mirror.leaseweb.com ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 1000ms
> rtt min/avg/max/mdev = 28.631/28.677/28.723/0.046 ms


Here's v6:
> $ LANG=CC tracepath mirror.leaseweb.com
>  1?: [LOCALHOST]                                         pmtu 1500
>  1:  gateway                                               2.280ms asymm  2 
>  1:  gateway                                               2.061ms asymm  2 
>  2:  178.19.212.225                                        5.179ms 
>  3:  178.19.208.25                                         3.156ms 
>  4:  178.19.223.32                                         3.977ms 
>  5:  peering.evo.leaseweb.net                             19.604ms 
>  6:  no reply
>  7:  46.165.255.149                                       22.507ms asymm  9 
>  8:  178.162.223.189                                      20.972ms asymm 10 
>  9:  no reply
> 10:  no reply
> 11:  no reply
> ^C
> freddy@x250:~$ LANG=CC ping -c2 mirror.leaseweb.com
> PING mirror.fra10.de.leaseweb.net (37.58.58.140) 56(84) bytes of data.
> 64 bytes from mirror.fra10.de.leaseweb.net (37.58.58.140): icmp_seq=1 ttl=54 time=21.4 ms
> 64 bytes from mirror.fra10.de.leaseweb.net (37.58.58.140): icmp_seq=2 ttl=54 time=21.5 ms
> 
> --- mirror.fra10.de.leaseweb.net ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 1000ms
> rtt min/avg/max/mdev = 21.434/21.507/21.580/0.073 ms
>

Comment 3

[Dave Curado :dcurado]

Is this still an issue, or was this a temporary condition?
Thank you.

Comment 4

[Dave Curado :dcurado]

This appears to have been a temporary issue, so I am going to close the bug.
If there is some action we should be taking, please re-open.
Thank you!