freitasm: @nickmack something for you to follohhow up when back from the roadtrip please.

Hi All,

This is similar behaviour to what we have seen before while testing with @MichaelMurfy. The team have had a good look into the issue (again today), we can see that the variable speed issue doesn’t appear to be inside the 2degrees network or on the Megaport handovers, but within the content provider that is hosting these various Microsoft libraries and files.

We have reached out to the content provider (logged a ticket) and we are awaiting feedback from them.  We have also requested to be pointed in the right direction if the servers/services are administered by a third party. It’s a case of reaching out to providers in the path step by step until we reach whoever is best positioned to help (if they so choose to). When I know more I'll provide an update.

Nick.

Thanks. For the record I ended up downloading Windows 10 1903 and Windows Server 1903 at work (in under five minutes) and uploaded to Google Drive (in a couple of minutes) where I will download from when at home (no USB here with me otherwise would use sneakernet)... 

Update 24/04/19

Hi All,

The team have done some more research and it looks like Microsoft may use Edgecast/Verizon for their CDN (Microsoft used to use Akamai). This appears to be hosting all these downloads based on the trace routes provided from Geekzone. We have reached out to Verizon directly yesterday and have we an active ticket with them.

We have seen similar issues on another Geekzone thread last year where users were seeing variable speeds to Edgecast CDN resources. This thread does well to explain - https://www.geekzone.co.nz/forums.asp?forumid=85&topicid=230411.

Nick.

Thanks for the update @NickMack...

Does @NickMack ever sleep? (Great help always, even if something isn't 2Degrees fault.)

Hi All,

Further to this - Customers who are attempting to reach the same resources via providers like Spark and Vodafone will likely be peering with Edgecast in another location, probably Sydney. According to peeringdb, these providers aren’t present in Megaport Auckland which is where Edgecast peer in New Zealand. We have a trace route from a Spark connection (@Michaelmurfy) that shows the latency and hop count difference, which seems to back this up.

This would explain the variance between results taken across different providers since they will peer with different CDN nodes according to their best path.

Nick.

msukiwi:

 

Does @NickMack ever sleep? (Great help always, even if something isn't 2Degrees fault.)

 

:-)

Did murfy just say something is actually better over sparks peering than openly peering at an IX(megaport)? ;)

hio77:

 

Did murfy just say something is actually better over sparks peering than openly peering at an IX(megaport)? ;)

 

I'll let him answer that... :-) Peering can be awesome.... and not awesome .... ;-)

Nick.

hio77:

 

Did murfy just say something is actually better over sparks peering than openly peering at an IX(megaport)? ;)

 

Didn't Nick just said it was not a Megaport problem? 

Stop the trolling, it doesn't help and it's off topic.

freitasm:

 

hio77:

 

Did murfy just say something is actually better over sparks peering than openly peering at an IX(megaport)? ;)

 

 

Didn't Nick just said it was not a Megaport problem? 

 

Stop the trolling, it doesn't help and it's off topic.

 

this whole thread is off topic since it's not a 2degrees issue.