Trusted
I just enabled IPv6 on my AWS EC2 instances, located in Oregon USA. In the process I noticed that IPv6 latency is higher than IPv4. This seems to be generally true for all USA IPv6 pings from NZ to the USA.
- Ping to EC2 Oregon IP6 is 238ms, IP4 is 166ms.
- Ping to he.net (USA) IP6 is 241ms, IP4 166ms
- Ping to tunnelbroker.net IP6 244ms, IP4 164ms
- Ping to ipv6.unh.edu IP6 is 293ms, ip4 is 215ms
Interestingly local and international pings don't seem so bad (random websites I found)
- heise.de IP6 298ms, IP4 297ms
- campaya.co.uk IP6 308ms, IP4 297ms
- ziggoforum.nl IP6 286ms, IP4 329ms
- facebook.com IP6 36ms, IP4 37ms
- Google.co.nz both 37ms
Do others find similar results? I have my server firewalled off from ICMP, but if anyone wants to test it I could add you to my firewall. PM me your IP. Best just use a public address though.
I wonder if the routing isn't quite right yet. I don't think it's particularly concerning, but maybe it's something for 2degrees to either query with their upstream provider or put on a "to do" list.
Here's an ip6 trace to my EC2 server, with a little obfuscation start and finish
3 * * * Request timed out.
4 137 ms 138 ms 138 ms NEUSTAR-INC.car4.SanJose1.Level3.net [2001:1900:2100::ec6]
5 140 ms 138 ms 138 ms ge-7-3.car4.SanJose1.Level3.net [2001:1900:2100::ec5]
6 * * * Request timed out.
7 159 ms 158 ms 158 ms 2001:1900:2100::3982
8 * * * Request timed out.
9 171 ms 170 ms 171 ms 2600:9000:eee::84
10 * * * Request timed out.
11 177 ms 168 ms 168 ms 2620:107:4000:3::16
12 196 ms 205 ms 190 ms 2620:107:4000:3::8
13 168 ms 170 ms 170 ms 2620:107:4000:3::23
14 * * * Request timed out.
15 238 ms 238 ms 238 ms 2620:108:7000::13
16 239 ms 239 ms 238 ms 2620:108:7000::14
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 239 ms 238 ms 238 ms 2600:1f14:37f:1300:ba83:6964:acd9:xxxx
Here's an ip4 trace to EC2
3 * * * Request timed out.
4 138 ms 138 ms 138 ms TWO-DEGREES.bar1.SanFrancisco1.Level3.net [4.16.192.146]
5 137 ms 138 ms 138 ms xe-4-2-0.bar1.SanFrancisco1.Level3.net [4.16.192.145]
6 158 ms 158 ms * ae-1-51.ear2.Seattle1.Level3.net [4.69.203.173]
7 157 ms 158 ms 158 ms 4.16.146.90
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 164 ms 167 ms 165 ms 205.251.230.127
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 168 ms 166 ms 166 ms hrtest.com [52.88.xx.xx]
Here's ip6 trace to another USA site, I think it was ipv6.unh.edu
3 14 ms 14 ms 15 ms 2406:e000:c00:18::1
4 35 ms 38 ms 38 ms 2406:e000:c00:18::2
5 37 ms 38 ms 38 ms ae7-2.akbr7.global-gateway.net.nz [2403:9800:0:10::1a1]
6 193 ms 190 ms 190 ms xe3-1-0.sjbr2.global-gateway.net.nz [2403:9800:0:10::14a]
7 192 ms 194 ms 194 ms 2403:9800:0:10::11e
8 * * * Request timed out.
9 249 ms 250 ms 250 ms ae-1.80.rtsw.sunn.net.internet2.edu [2001:468:f000:f53::2]
10 251 ms 250 ms 250 ms et-2-1-0.4074.rtsw.losa.net.internet2.edu [2001:468:f000:f52::2]
11 263 ms 262 ms 262 ms ae-2.80.rtsw.salt.net.internet2.edu [2001:468:f000:f31::2]
12 293 ms 290 ms 293 ms ae-2.80.rtsw.kans.net.internet2.edu [2001:468:f000:f32::2]
13 288 ms 290 ms 290 ms et-11-1-0.4072.rtsw.chic.net.internet2.edu [2001:468:f000:f33::2]
14 287 ms 290 ms 291 ms ae-4.80.rtr.eqch.net.internet2.edu [2001:468:f000:f34::2]
15 317 ms 314 ms 314 ms 2001:468:f000:2108::2
16 317 ms 314 ms 314 ms 2001:468:601:1::17
17 319 ms 319 ms 318 ms 2001:504:2e:6029::2
18 317 ms 318 ms 323 ms lan-wan.unh.edu [2606:4100:3fff:a0::3]
19 321 ms 322 ms 323 ms gw-iol.ipv6.unh.edu [2606:4100:3fff:8132::3880]
20 322 ms 322 ms 318 ms 2606:4100:3880:1250::100
Here is ipv6.unh.edu over IPv4
3 * * * Request timed out.
4 139 ms 139 ms 138 ms ip4.gtt.net [173.205.51.174]
5 139 ms 138 ms 138 ms ae7-200.cr0-sjc2.ip4.gtt.net [173.205.51.173]
6 141 ms 140 ms 138 ms xe-10-3-3.cr0-sjc1.ip4.gtt.net [141.136.110.13]
7 138 ms 138 ms 138 ms be3257.ccr41.sjc03.atlas.cogentco.com [154.54.9.13]
8 141 ms 139 ms 142 ms be3142.ccr21.sjc01.atlas.cogentco.com [154.54.1.193]
9 140 ms 142 ms 142 ms be3178.ccr21.sfo01.atlas.cogentco.com [154.54.43.69]
10 158 ms 158 ms 158 ms be3109.ccr21.slc01.atlas.cogentco.com [154.54.44.138]
11 190 ms 190 ms 190 ms be3037.ccr21.den01.atlas.cogentco.com [154.54.41.146]
12 193 ms 190 ms 190 ms be3035.ccr21.mci01.atlas.cogentco.com [154.54.5.90]
13 188 ms 190 ms 190 ms be2831.ccr41.ord01.atlas.cogentco.com [154.54.42.166]
14 204 ms 202 ms 202 ms be2717.ccr21.cle04.atlas.cogentco.com [154.54.6.222]
15 208 ms 210 ms 210 ms be2878.ccr21.alb02.atlas.cogentco.com [154.54.26.130]
16 213 ms 214 ms 214 ms be2299.ccr31.bos01.atlas.cogentco.com [154.54.43.9]
17 214 ms 214 ms 210 ms te0-4-1-6.agr22.bos01.atlas.cogentco.com [154.54.80.10]
18 214 ms 214 ms 214 ms te0-0-2-0.nr11.b002250-1.bos01.atlas.cogentco.com [154.24.14.206]
19 215 ms 220 ms 217 ms 38.104.187.154
20 215 ms 215 ms 213 ms tccat3-inet.unh.edu [132.177.100.8]
21 215 ms 215 ms 218 ms netscreen.iol.unh.edu [132.177.123.2]
22 220 ms 217 ms 219 ms ipv6ready-live.iol.unh.edu [132.177.125.100]
For comparison and to show it's not a server problem I ping'd my server IP4 and IP6 using a couple of online tools, presumably in the USA, which show similar IP4/6 performance
http://www.subnetonline.com/pages/ipv6-network-tools/online-ipv6-ping.php
40 bytes from 2600:1f14:37f:1300:ba83:6964:xxxx:xxxx: icmp_seq=0 ttl=42 time=149 ms
40 bytes from 2600:1f14:37f:1300:ba83:6964:xxxx:xxxx: icmp_seq=1 ttl=42 time=149 ms
40 bytes from 2600:1f14:37f:1300:ba83:6964:xxxx:xxxx: icmp_seq=2 ttl=42 time=148 ms
40 bytes from 2600:1f14:37f:1300:ba83:6964:xxxx:xxxx: icmp_seq=3 ttl=42 time=149 ms
http://www.subnetonline.com/pages/network-tools/online-ping-ipv4.php
40 bytes from 52.88.x.x: icmp_seq=1 ttl=233 time=154 ms
40 bytes from 52.88.x.x: icmp_seq=2 ttl=233 time=150 ms
40 bytes from 52.88.x.x: icmp_seq=3 ttl=233 time=150 ms
40 bytes from 52.88.x.x: icmp_seq=4 ttl=233 time=150 ms
http://www.ipv6now.com.au/pingme.php
64 bytes from 2600:1f14:37f:1300:ba83:6964:xxxx:xxxx: icmp_seq=1 ttl=41 time=202 ms
64 bytes from 2600:1f14:37f:1300:ba83:6964:xxxx:xxxx: icmp_seq=2 ttl=41 time=196 ms
64 bytes from 2600:1f14:37f:1300:ba83:6964:xxxx:xxxx: icmp_seq=3 ttl=41 time=196 ms
64 bytes from 2600:1f14:37f:1300:ba83:6964:xxxx:xxxx: icmp_seq=4 ttl=41 time=197 ms
64 bytes from 2600:1f14:37f:1300:ba83:6964:xxxx:xxxx: icmp_seq=5 ttl=41 time=196 ms
64 bytes from 52.88.xx.xx: icmp_seq=1 ttl=232 time=191 ms
64 bytes from 52.88.xx.xx: icmp_seq=2 ttl=232 time=191 ms
64 bytes from 52.88.xx.xx: icmp_seq=3 ttl=232 time=192 ms
64 bytes from 52.88.xx.xx: icmp_seq=4 ttl=232 time=189 ms
64 bytes from 52.88.xx.xx: icmp_seq=5 ttl=232 time=190 ms
