Slow iCloud photo syncing with IPv6 on 2degrees?

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › Slow iCloud photo syncing with IPv6 on 2degrees?

1 | 2 | 3

1512 posts

Uber Geek

Lifetime subscriber

#2105370 10-Oct-2018 10:52

Thanks @NickMack

I only bring it up because last night I noticed about 7 videos missing from my Mac, when I looked at my phone they had basically stalled uploading

I'll take some photos and videos and see what happens traffic wise with the sync

You'd think @yitz, but ipv4 traffic ended up not being that much better routing wise

Joelfreak

6 posts

Wannabe Geek

Trusted

Hurricane Electric

#2105373 10-Oct-2018 10:53

As far as we know there are no tickets open for any problems. If there is a problem please contact our NOC and we will be more than happy to look at it.

dfnt

1512 posts

Uber Geek

Lifetime subscriber

#2105629 10-Oct-2018 14:43

Not seeing any difference:

nsurlsessiond.262 295 MiB 120 KiB 0 B 51 KiB 1846 B
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49642<->2403:300:a41:400::a.443 en0 Established 21 MiB 2030 B 0 B 0 B 0 B 255.44 ms 354 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49643<->2403:300:a41:400::a.443 en0 Established 27 MiB 1955 B 0 B 2856 B 0 B 276.59 ms 672 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49649<->2403:300:a41:407::5.443 en0 Established 17 MiB 2030 B 0 B 0 B 0 B 278.06 ms 64 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49692<->2403:300:a41:400::a.443 en0 Established 9122 KiB 2030 B 0 B 0 B 0 B 263.25 ms 64 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49697<->2403:300:a41:400::a.443 en0 Established 7527 KiB 1955 B 0 B 0 B 0 B 284.03 ms 64 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49701<->2403:300:a41:407::d.443 en0 Established 2943 KiB 2030 B 0 B 0 B 0 B 273.91 ms 64 KiB 32 KiB

Still seeing high latency to ipv6 destinations when syncing to icloud photos.

Tracing route to 2403:300:a41:400::a over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 2406:e001:2:6700::1
2 1 ms 1 ms 1 ms 2406:e000:2801:c::1
3 34 ms 35 ms 34 ms 2403:300:0:8810::92
4 37 ms 34 ms 34 ms 2403:300:0:8810::91
5 306 ms 306 ms 306 ms 2403:300:0:80f::62
6 316 ms 318 ms 315 ms 2403:300:0:10f::82
7 313 ms 313 ms 313 ms 2403:300:0:710::142
8 306 ms 305 ms 305 ms 2403:300:220:1::52
9 303 ms 303 ms 304 ms 2403:300:a07:1::572
10 * * * Request timed out.
11 * * ^C

NickMack

962 posts

Ultimate Geek

Trusted

Lifetime subscriber

#2105637 10-Oct-2018 14:49

dfnt:

Not seeing any difference:

nsurlsessiond.262 295 MiB 120 KiB 0 B 51 KiB 1846 B
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49642<->2403:300:a41:400::a.443 en0 Established 21 MiB 2030 B 0 B 0 B 0 B 255.44 ms 354 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49643<->2403:300:a41:400::a.443 en0 Established 27 MiB 1955 B 0 B 2856 B 0 B 276.59 ms 672 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49649<->2403:300:a41:407::5.443 en0 Established 17 MiB 2030 B 0 B 0 B 0 B 278.06 ms 64 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49692<->2403:300:a41:400::a.443 en0 Established 9122 KiB 2030 B 0 B 0 B 0 B 263.25 ms 64 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49697<->2403:300:a41:400::a.443 en0 Established 7527 KiB 1955 B 0 B 0 B 0 B 284.03 ms 64 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49701<->2403:300:a41:407::d.443 en0 Established 2943 KiB 2030 B 0 B 0 B 0 B 273.91 ms 64 KiB 32 KiB

Still seeing high latency to ipv6 destinations when syncing to icloud photos.

Tracing route to 2403:300:a41:400::a over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 2406:e001:2:6700::1
2 1 ms 1 ms 1 ms 2406:e000:2801:c::1
3 34 ms 35 ms 34 ms 2403:300:0:8810::92
4 37 ms 34 ms 34 ms 2403:300:0:8810::91
5 306 ms 306 ms 306 ms 2403:300:0:80f::62
6 316 ms 318 ms 315 ms 2403:300:0:10f::82
7 313 ms 313 ms 313 ms 2403:300:0:710::142
8 306 ms 305 ms 305 ms 2403:300:220:1::52
9 303 ms 303 ms 304 ms 2403:300:a07:1::572
10 * * * Request timed out.
11 * * ^C

Thanks - The Team are talking and working on a plan and options, I'll update once I have something a bit more concrete.

https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz

dfnt

1512 posts

Uber Geek

Lifetime subscriber

#2105641 10-Oct-2018 14:51

NickMack:

dfnt:

Not seeing any difference:

nsurlsessiond.262 295 MiB 120 KiB 0 B 51 KiB 1846 B
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49642<->2403:300:a41:400::a.443 en0 Established 21 MiB 2030 B 0 B 0 B 0 B 255.44 ms 354 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49643<->2403:300:a41:400::a.443 en0 Established 27 MiB 1955 B 0 B 2856 B 0 B 276.59 ms 672 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49649<->2403:300:a41:407::5.443 en0 Established 17 MiB 2030 B 0 B 0 B 0 B 278.06 ms 64 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49692<->2403:300:a41:400::a.443 en0 Established 9122 KiB 2030 B 0 B 0 B 0 B 263.25 ms 64 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49697<->2403:300:a41:400::a.443 en0 Established 7527 KiB 1955 B 0 B 0 B 0 B 284.03 ms 64 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49701<->2403:300:a41:407::d.443 en0 Established 2943 KiB 2030 B 0 B 0 B 0 B 273.91 ms 64 KiB 32 KiB

Still seeing high latency to ipv6 destinations when syncing to icloud photos.

Tracing route to 2403:300:a41:400::a over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 2406:e001:2:6700::1
2 1 ms 1 ms 1 ms 2406:e000:2801:c::1
3 34 ms 35 ms 34 ms 2403:300:0:8810::92
4 37 ms 34 ms 34 ms 2403:300:0:8810::91
5 306 ms 306 ms 306 ms 2403:300:0:80f::62
6 316 ms 318 ms 315 ms 2403:300:0:10f::82
7 313 ms 313 ms 313 ms 2403:300:0:710::142
8 306 ms 305 ms 305 ms 2403:300:220:1::52
9 303 ms 303 ms 304 ms 2403:300:a07:1::572
10 * * * Request timed out.
11 * * ^C

Thanks - The Team are talking and working on a plan and options, I'll update once I have something a bit more concrete.

Thanks Nick!

NickMack

962 posts

Ultimate Geek

Trusted

Lifetime subscriber

#2105680 10-Oct-2018 16:00

dfnt:

NickMack:

dfnt:

Not seeing any difference:

nsurlsessiond.262 295 MiB 120 KiB 0 B 51 KiB 1846 B
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49642<->2403:300:a41:400::a.443 en0 Established 21 MiB 2030 B 0 B 0 B 0 B 255.44 ms 354 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49643<->2403:300:a41:400::a.443 en0 Established 27 MiB 1955 B 0 B 2856 B 0 B 276.59 ms 672 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49649<->2403:300:a41:407::5.443 en0 Established 17 MiB 2030 B 0 B 0 B 0 B 278.06 ms 64 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49692<->2403:300:a41:400::a.443 en0 Established 9122 KiB 2030 B 0 B 0 B 0 B 263.25 ms 64 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49697<->2403:300:a41:400::a.443 en0 Established 7527 KiB 1955 B 0 B 0 B 0 B 284.03 ms 64 KiB 32 KiB
tcp6 2406:e001:2:6700:9c5d:d9ec:4445:7194.49701<->2403:300:a41:407::d.443 en0 Established 2943 KiB 2030 B 0 B 0 B 0 B 273.91 ms 64 KiB 32 KiB

Still seeing high latency to ipv6 destinations when syncing to icloud photos.

Tracing route to 2403:300:a41:400::a over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 2406:e001:2:6700::1
2 1 ms 1 ms 1 ms 2406:e000:2801:c::1
3 34 ms 35 ms 34 ms 2403:300:0:8810::92
4 37 ms 34 ms 34 ms 2403:300:0:8810::91
5 306 ms 306 ms 306 ms 2403:300:0:80f::62
6 316 ms 318 ms 315 ms 2403:300:0:10f::82
7 313 ms 313 ms 313 ms 2403:300:0:710::142
8 306 ms 305 ms 305 ms 2403:300:220:1::52
9 303 ms 303 ms 304 ms 2403:300:a07:1::572
10 * * * Request timed out.
11 * * ^C

Thanks - The Team are talking and working on a plan and options, I'll update once I have something a bit more concrete.

Thanks Nick!

Hi All,

Plan confirmed - It appears to be an issue due to the Apple CDN returning paths for the google compute address rather than their own. Configuration, QA and application of the change should be done today, I'll let you know once this is done.

Nick.

https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz

BarTender

3606 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#2105767 10-Oct-2018 17:22

yitz:
dfnt:

Any update on this?

I'm actually considering moving back to Spark as the icloud speeds are so slow on 2degrees.

Turning off IPv6 might have the same effect lol

I love this thread so much as I was being berated yesterday by @michaelmurfy about why Spark hadn't deployed IPv6 yet as a hangover from when I was a staffer and they are so behind the ball.

This is yet another example of deploying IPv6 more than doubles the complexity of your network for what value? Sure it means that the NSA can now fingerprint you more effectively based on your MAC address when you roam between networks as that is typically the first half of your IPv6 Address unless you randomise it.

But I do appreciate the support Nick has been giving with trying to resolve the issue.

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

dfnt

1512 posts

Uber Geek

Lifetime subscriber

#2105799 10-Oct-2018 17:28

BarTender:

yitz:
dfnt:

Any update on this?

I'm actually considering moving back to Spark as the icloud speeds are so slow on 2degrees.

Turning off IPv6 might have the same effect lol

I love this thread so much as I was being berated yesterday by @michaelmurfy about why Spark hadn't deployed IPv6 yet as a hangover from when I was a staffer and they are so behind the ball.

This is yet another example of deploying IPv6 more than doubles the complexity of your network for what value? Sure it means that the NSA can now fingerprint you more effectively based on your MAC address when you roam between networks as that is typically the first half of your IPv6 Address unless you randomise it.

But I do appreciate the support Nick has been giving with trying to resolve the issue.

Yeah, I can't imagine the complexity involved with ipv6, even though I'm running it I still don't fully understand it. Definitely appreciate that they're even looking into it, really is great service.

Similar behaviour exists with ipv4 as well, I assume for the same reasons Nick described above

dfnt

1512 posts

Uber Geek

Lifetime subscriber

#2105800 10-Oct-2018 17:29

NickMack:

Hi All,

Plan confirmed - It appears to be an issue due to the Apple CDN returning paths for the google compute address rather than their own. Configuration, QA and application of the change should be done today, I'll let you know once this is done.

Nick.

Thanks for that, it's greatly appreciated.

I do believe Apple started shifting a lot of their cloud services from their own to GCP so makes sense.

michaelmurfy

meow
13242 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#2105806 10-Oct-2018 17:38

Don't mind @BarTender - he is just sour because he can't join in the fun with us cool kids.

Still though - as per his point of adding complexity there are much larger ISP's than Spark that have enabled IPv6 for their customers worldwide and almost every ISP here in NZ has too. There are benefits to having it for the customer (each device gets a publicly routed address) and once ISP's stop dragging their feet on the subject then there will be more use for people to go IPv6 only.

Which reminds me - I manage the servers for a very large website of which 63% of traffic is over IPv6. The servers themselves only talk over IPv6 to Cloudflare and Cloudflare handles the IPv6 to IPv4 transition for people who don't have IPv6 support.

This isn't really the subject of this topic but there is in-fact viable use for IPv6. Companies need to really stop making excuses to not deploy it.

Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.

NickMack

962 posts

Ultimate Geek

Trusted

Lifetime subscriber

#2105820 10-Oct-2018 18:20

dfnt:

BarTender:

yitz:
dfnt:

Any update on this?

I'm actually considering moving back to Spark as the icloud speeds are so slow on 2degrees.

Turning off IPv6 might have the same effect lol

I love this thread so much as I was being berated yesterday by @michaelmurfy about why Spark hadn't deployed IPv6 yet as a hangover from when I was a staffer and they are so behind the ball.

This is yet another example of deploying IPv6 more than doubles the complexity of your network for what value? Sure it means that the NSA can now fingerprint you more effectively based on your MAC address when you roam between networks as that is typically the first half of your IPv6 Address unless you randomise it.

But I do appreciate the support Nick has been giving with trying to resolve the issue.

Yeah, I can't imagine the complexity involved with ipv6, even though I'm running it I still don't fully understand it. Definitely appreciate that they're even looking into it, really is great service.

Similar behaviour exists with ipv4 as well, I assume for the same reasons Nick described above

Hiya, change made, let's see if that makes things better :-)

Nick.

https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz

dfnt

1512 posts

Uber Geek

Lifetime subscriber

#2105866 10-Oct-2018 19:59

NickMack:

dfnt:

BarTender:

yitz:
dfnt:

Any update on this?

I'm actually considering moving back to Spark as the icloud speeds are so slow on 2degrees.

Turning off IPv6 might have the same effect lol

I love this thread so much as I was being berated yesterday by @michaelmurfy about why Spark hadn't deployed IPv6 yet as a hangover from when I was a staffer and they are so behind the ball.

This is yet another example of deploying IPv6 more than doubles the complexity of your network for what value? Sure it means that the NSA can now fingerprint you more effectively based on your MAC address when you roam between networks as that is typically the first half of your IPv6 Address unless you randomise it.

But I do appreciate the support Nick has been giving with trying to resolve the issue.

Yeah, I can't imagine the complexity involved with ipv6, even though I'm running it I still don't fully understand it. Definitely appreciate that they're even looking into it, really is great service.

Similar behaviour exists with ipv4 as well, I assume for the same reasons Nick described above

Hiya, change made, let's see if that makes things better :-)

Nick.

That was quick!

So, I took a 20 second video and it uploaded pretty quickly at ~100mbit/s

Thinking that was too good to be true, I took another 20 second video at 7:38 and as at 7:58 I'd say its about 80% through the upload and seems to have stalled.

Did a quick packet cap to see where its going to and this is one of the ipv6 address:

2403:300:a41:405::b

traceroute6 to 2403:300:a41:405::b (2403:300:a41:405::b) from 2406:e001:2:6700:14da:7dea:8ef5:e9f0, 64 hops max, 12 byte packets
1 2406:e001:2:6700::1 6.474 ms 2.272 ms 3.268 ms
2 2406:e000:2801:c::1 3.282 ms 3.459 ms 3.352 ms
3 2403:300:0:8810::92 36.610 ms 38.619 ms 38.026 ms
4 2403:300:0:8810::91 36.595 ms 38.196 ms 37.397 ms
5 2403:300:0:80f::62 526.940 ms 370.519 ms 307.460 ms
6 2403:300:0:10f::82 310.140 ms 290.276 ms 384.999 ms
7 2403:300:0:710::132 309.278 ms
2403:300:0:710::152 362.703 ms
2403:300:0:710::122 298.593 ms
8 2403:300:220:1::c2 421.702 ms
2403:300:220:1::22 559.800 ms 367.382 ms
9 2403:300:a07:1::5e2 615.570 ms
2403:300:a07:1::532 365.920 ms
2403:300:a07:1::5a2 304.656 ms
10 2403:300:a07:2::2d2 416.510 ms 308.910 ms
2403:300:a07:2::452 319.154 ms
11 2403:300:a41:405::b 422.199 ms 300.421 ms 296.400 ms

I can't tell how fast or slow its going because the tx/rx rate aren't even registering on EdgeRouter's DPI so I imagine the file is being uploaded at kbps.

Edit: Finished uploading at 8:02, now the Mac is downloading the same video:

nsurlsessiond.262 304 MiB 69 KiB 1418 B 151 KiB 0 B
tcp6 2406:e001:2:6700:14da:7dea:8ef5:e9f0.53955<->2403:300:a41:405::c.443 en0 Established 6457 KiB 3985 B 0 B 0 B 0 B 270.72 ms 64 KiB 35 KiB
tcp6 2406:e001:2:6700:14da:7dea:8ef5:e9f0.53958<->2403:300:a41:405::c.443 en0 Established 6130 KiB 1955 B 0 B 0 B 0 B 286.25 ms 64 KiB 32 KiB
tcp6 2406:e001:2:6700:14da:7dea:8ef5:e9f0.53959<->2403:300:a41:405::c.443 en0 Established 6122 KiB 1955 B 0 B 0 B 0 B 287.84 ms 64 KiB 34 KiB
tcp6 2406:e001:2:6700:14da:7dea:8ef5:e9f0.53960<->2403:300:a41:405::c.443 en0 Established 7413 KiB 1955 B 0 B 0 B 0 B 271.03 ms 179 KiB 32 KiB
tcp6 2406:e001:2:6700:14da:7dea:8ef5:e9f0.53961<->2403:300:a41:405::c.443 en0 Established 6332 KiB 1955 B 0 B 0 B 0 B 273.00 ms 64 KiB 32 KiB
tcp6 2406:e001:2:6700:14da:7dea:8ef5:e9f0.53963<->2403:300:a41:405::c.443 en0 Established 5908 KiB 1955 B 0 B 0 B 0 B 286.44 ms 64 KiB 32 KiB

traceroute6 to 2403:300:a41:405::c (2403:300:a41:405::c) from 2406:e001:2:6700:14da:7dea:8ef5:e9f0, 64 hops max, 12 byte packets
1 2406:e001:2:6700::1 2.475 ms 1.599 ms 2.260 ms
2 2406:e000:2801:c::1 3.093 ms 2.879 ms 3.134 ms
3 2403:300:0:8810::92 36.319 ms 36.681 ms 37.161 ms
4 2403:300:0:8810::91 37.393 ms 36.815 ms 36.302 ms
5 2403:300:0:80f::62 291.603 ms 289.030 ms 293.580 ms
6 2403:300:0:10f::82 289.562 ms 297.587 ms 312.340 ms
7 2403:300:0:710::142 292.777 ms
2403:300:0:710::132 313.515 ms 307.651 ms
8 2403:300:220:1::2 306.559 ms
2403:300:220:1::f2 314.952 ms
2403:300:220:1::d2 295.615 ms
9 2403:300:a07:1::5a2 301.195 ms
2403:300:a07:1::592 296.067 ms
2403:300:a07:1::5e2 297.789 ms
10 2403:300:a07:2::452 301.775 ms
2403:300:a07:2::212 294.429 ms 293.381 ms
11 2403:300:a41:405::c 311.028 ms 304.781 ms 304.456 ms

And is downloading it at ~3.7 Mbit/s

NickMack

962 posts

Ultimate Geek

Trusted

Lifetime subscriber

#2105867 10-Oct-2018 20:03

Ok.. If you want to do a bit more testing and supply some captures that would be grand.

Nick.

https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz

dfnt

1512 posts

Uber Geek

Lifetime subscriber

#2105875 10-Oct-2018 20:18

NickMack: Ok.. If you want to do a bit more testing and supply some captures that would be grand.

Nick.

Yup, will do.

Will get onto it next week when I have the house to myself (wife starts at 2degrees next week! and 15 m/o will be at her nannies) :)

dfnt

1512 posts

Uber Geek

Lifetime subscriber

#2105892 10-Oct-2018 20:44

NickMack: Ok.. If you want to do a bit more testing and supply some captures that would be grand.

Nick.

Took another video, this time it uploaded at ~250 Mbit/s

2403:300:a50:100::c was the ipv6 address used for the upload this time

traceroute6 to 2403:300:a50:100::c (2403:300:a50:100::c) from 2406:e001:2:6700:14da:7dea:8ef5:e9f0, 64 hops max, 12 byte packets
1 2406:e001:2:6700::1 6.058 ms 3.353 ms 2.282 ms
2 2406:e000:2801:c::1 6.551 ms 4.413 ms 5.183 ms
3 2403:300:0:8810::92 39.294 ms 37.735 ms 37.201 ms
4 2403:300:0:8810::91 38.108 ms 37.111 ms 36.090 ms
5 2403:300:0:810::52 37.553 ms 38.386 ms 37.717 ms
6 2403:300:a09:2::2e2 36.585 ms 36.494 ms 37.152 ms
7 2403:300:a50:100::c 37.101 ms 37.290 ms 37.240 ms

I'd be happy if it was consistently that good :D

Then took another video, slow upload again.

2403:300:a41:407::a ipv6 address which has the same high latency as a previous post

traceroute6 to 2403:300:a41:407::a (2403:300:a41:407::a), 64 hops max, 12 byte packets
1 2406:e001:2:6700::1 2.411 ms 2.713 ms 2.531 ms
2 2406:e000:2801:c::1 3.164 ms 2.608 ms 3.191 ms
3 2403:300:0:8810::92 45.767 ms 39.693 ms 37.485 ms
4 2403:300:0:8810::91 38.294 ms 37.352 ms 37.692 ms
5 2403:300:0:80f::62 290.984 ms 289.525 ms 290.715 ms
6 2403:300:0:10f::82 299.137 ms 291.895 ms 302.176 ms
7 2403:300:0:710::142 294.544 ms
2403:300:0:710::152 299.743 ms 299.954 ms
8 2403:300:220:1::72 294.771 ms
2403:300:220:1::d2 298.158 ms
2403:300:220:1::2 313.959 ms
9 2403:300:a07:1::552 294.832 ms
2403:300:a07:1::532 304.708 ms
2403:300:a07:1::512 294.352 ms
10 2403:300:a07:2::3b2 293.656 ms
2403:300:a07:2::172 326.750 ms 330.150 ms
11 2403:300:a41:407::a 311.178 ms 311.296 ms 306.325 ms

I tried an ipv6 address in my OP, definitely improved:

[/code]traceroute6 to 2403:300:a50:105::8 (2403:300:a50:105::8), 64 hops max, 12 byte packets
1 2406:e001:2:6700::1 2.239 ms 1.505 ms 2.310 ms
2 2406:e000:2801:c::1 3.313 ms 2.563 ms 3.148 ms
3 2403:300:0:8810::92 37.133 ms 38.674 ms 39.356 ms
4 2403:300:0:8810::91 36.928 ms 39.389 ms 37.674 ms
5 2403:300:0:810::52 37.022 ms 36.752 ms 37.759 ms
6 2403:300:a09:2::302 40.476 ms 38.011 ms 40.615 ms
7 2403:300:a50:105::8 36.975 ms 36.926 ms 38.738 ms[/code]

Compared to how it was:

traceroute6 to 2403:300:a50:105::8 (2403:300:a50:105::8), 64 hops max, 12 byte packets
1 ::1 1.012 ms 2.253 ms 1.447 ms
2 2406:e000:2801:c::1 3.210 ms 4.061 ms 2.235 ms
3 as23655.auckland.megaport.com 15.115 ms 16.333 ms 15.505 ms
4 2001:7fa:11:6::1b1b:0:1 15.881 ms 14.635 ms 14.317 ms
5 10ge2-3.core1.syd1.he.net 39.391 ms 39.118 ms 48.607 ms
6 10ge3-5.core1.sjc1.he.net 181.170 ms 189.033 ms 180.653 ms
7 10ge7-2.core1.sjc2.he.net 180.222 ms
100ge1-1.core1.sjc2.he.net 180.409 ms
10ge7-2.core1.sjc2.he.net 181.625 ms
8 kddi-as2516.10gigabitethernet1-1-1.switch2.sjc2.he.net 181.098 ms 181.841 ms 182.752 ms
9 6sjegcs002.int-gw.kddi.ne.jp 162.361 ms
6sjegcs001.int-gw.kddi.ne.jp 162.325 ms
6sjegcs002.int-gw.kddi.ne.jp 163.800 ms
10 oteacs001.int-gw.kddi.ne.jp 264.717 ms
2001:268:fb81:72::1 268.788 ms
2001:268:fb81:6a::1 266.005 ms
11 2001:268:fa00:2fc::2 265.173 ms
2001:268:fa00:2f9::2 269.729 ms 262.656 ms
12 6kotjin204.int-gw.kddi.ne.jp 273.841 ms 268.750 ms
6kotjin204.int-gw.kddi.ne.jp 265.031 ms
13 2001:268:f702:100::2 282.773 ms 288.522 ms 288.598 ms
14 2403:300:0:80f::21 221.936 ms 223.108 ms 217.024 ms
15 2403:300:0:80f::1 220.787 ms 220.023 ms 217.712 ms
16 2403:300:0:810::52 221.658 ms 216.997 ms 222.670 ms
17 2403:300:a09:2::302 217.379 ms 223.525 ms 218.987 ms
18 2403:300:a50:105::8 220.699 ms 220.420 ms 217.889 ms

So the changes you guys made have definitely made a big improvement.

Can anything be done with the 2403:300:a41 subnet or is it pretty much out of your hands now? That seems to be the problematic ipv6 address range with similar routing to how 2403:300:a50 used to be.

1 | 2 | 3