Re: Virgin Akamai Cache Congestion
 

Going to test this with the 4K stream of the England match on iplayer tonight, using Google DNS

Re: Virgin Akamai Cache Congestion
 

I've just added google#s HTTPS settings, however if I browse to https://1.1.1.1/help it says that i'm not using DoH? It does recognise that I'm using google's service though...

Re: Virgin Akamai Cache Congestion
 

I think that only recognises it's own (cloudflare) DoH

Tried some Sky go / BT sport, using virgins cache and it seems ok, iplayer appears to be getting sent to a cache with an ntl hostname which i'm still having issues with...

If anyone else wants to test the hostnames are vod-progressive.akamaized.net / vod-uhd-uk-live.akamaized.net which resolve to m163-mp1.cvx2-c.lng.dial.ntli.net / m202-mp1.cvx2-c.lng.dial.ntli.net respectively

Re: Virgin Akamai Cache Congestion
 

How did it go?

Re: Virgin Akamai Cache Congestion
 

Perfect, not a single buffer :)

Re: Virgin Akamai Cache Congestion
 

Bit of an update re iplayer..

I may be wrong here, but going off the hostnames it looks like some strange routing on virgin's end, going via new york?

Would explain the huge latency to that server too!

traceroute to 23.206.169.90 (23.206.169.90), 30 hops max, 60 byte packets
1 x.x.x.x1 (x.x.x.x) 0.196 ms 0.120 ms 0.114 ms
2 10.53.34.249 (10.53.34.249) 10.519 ms 13.475 ms 13.712 ms
3 gate-core-2a-xe-7116-0.network.virginmedia.net (80.0.145.13) 13.917 ms 14. 178 ms 14.349 ms
4 * * *
5 * * *
6 86.85-254-62.static.virginmediabusiness.co.uk (62.254.85.86) 29.775 ms 27. 773 ms 30.721 ms
7 ldn-b3-link.ip.twelve99.net (213.248.84.25) 31.562 ms 23.300 ms 24.906 ms
8 ldn-bb1-link.ip.twelve99.net (62.115.120.74) 24.971 ms 22.969 ms ldn-bb4-l ink.ip.twelve99.net (62.115.122.180) 25.864 ms
9 nyk-bb2-link.ip.twelve99.net (62.115.113.20) 99.539 ms 98.796 ms *
10 rest-bb1-link.ip.twelve99.net (62.115.141.244) 132.137 ms 131.152 ms ash-b b2-link.ip.twelve99.net (62.115.112.242) 142.919 ms
11 nyk-bb2-link.ip.twelve99.net (62.115.136.200) 126.897 ms atl-b24-link.ip.tw elve99.net (62.115.125.128) 116.761 ms atl-b24-link.ip.twelve99.net (62.115.125 .191) 113.505 ms
12 ash-bb2-link.ip.twelve99.net (62.115.136.201) 113.644 ms dls-b23-link.ip.tw elve99.net (62.115.123.200) 133.330 ms ash-bb2-link.ip.twelve99.net (62.115.136 .201) 114.849 ms
13 akamai-ic345782-dls-b23.ip.twelve99-cust.net (62.115.176.103) 233.157 ms 2 23.642 ms 219.856 ms
14 dls-b23-link.ip.twelve99.net (80.91.246.75) 147.863 ms ve-uhd-push-uk-live. akamaized.net (23.206.169.90) 132.700 ms 131.578 ms

Does anyone else see the same strange routing / high latency on their VM connection?

--- 23.206.169.90 ping statistics ---
40 packets transmitted, 40 received, 0% packet loss, time 39051ms
rtt min/avg/max/mdev = 128.974/131.397/136.025/1.927 ms

EDIT:

These are examples of the hosts / IPs for the routes that seem to be broken on VM, not sure how we'd get anyone at VM to look into it though!

Live UHD - ve-uhd-push-uk-live.akamaized.net - 2.22.22.112
On demand HD - vod-dash-uk-live.akamaized.net (104.100.95.49)
Live HD - vs-cmaf-push-uk-live.akamaized.net 2.22.22.163

Re: Virgin Akamai Cache Congestion
 

Tracing route to a23-206-169-90.deploy.static.akamaitechnologies.com [23.206.169.90]
over a maximum of 30 hops:

1 4 ms <1 ms <1 ms 18.19.1.1
2 6 ms 10 ms 6 ms 10.53.39.129
3 20 ms 10 ms 13 ms nott-core-2b-xe-014-0.network.virginmedia.net [62.255.214.169]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 18 ms 15 ms 18 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
8 20 ms 18 ms 17 ms 213.46.174.118
9 18 ms 18 ms 17 ms ldn-bb1-link.ip.twelve99.net [62.115.122.188]
10 90 ms 88 ms 95 ms nyk-bb2-link.ip.twelve99.net [62.115.113.20]
11 95 ms * * ash-bb2-link.ip.twelve99.net [62.115.136.201]
12 108 ms 114 ms 107 ms atl-b24-link.ip.twelve99.net [62.115.125.128]
13 125 ms 125 ms 125 ms dls-b23-link.ip.twelve99.net [80.91.246.75]
14 129 ms 220 ms 125 ms akamai-ic345782-dls-b23.ip.twelve99-cust.net [62.115.176.103]
15 126 ms 125 ms 125 ms a23-206-169-90.deploy.static.akamaitechnologies.com [23.206.169.90]

Ping statistics for 23.206.169.90:
Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 122ms, Maximum = 132ms, Average = 126ms

Re: Virgin Akamai Cache Congestion
 

Cheers General, definitely looks like there's an issue with the routing there

Re: Virgin Akamai Cache Congestion
 

So bit of a follow up / conclusion if anyone is still following / comes across this from google.

tl;dr - akamai won't work properly when using cloudflare DNS with virgin (as of now), use Google's 8.8.8.8 resolver.

The reason for buffering with cloudflare is due to them not supporting ECS, basically this sends your subnet with the DNS packet so the resolver knows to send you to a local / ISP cache.

Google does support this, which is why issues are resolved using google DNS, and i assume virgin's DNS is set to send you to their own local cache anyway.

Re: Virgin Akamai Cache Congestion
 

So to sum up for everyone reading.................buy a proper router and use google's dns and you won't have to put up with any of this shit.

Re: Virgin Akamai Cache Congestion
 

Sort of, if you're not using virgin's DNS, use Google / Quad9 / OpenDNS, just be aware you might run into issues using cloudflare

Re: Virgin Akamai Cache Congestion
 

Finally sorted my issues with Adguard, I could set individual devices to my Synology box - but if I set my WAN DNS entried 1 and 2 so my NAS, I would lose internet connectivity. This same config with pihole worked.

What seems to fix it, is leave the DNS1/2 settings as either blank or normal Google resolver and change the "DNS Server" settings under the Asus LAN tab.

Now, rather than have just my router in the adguard device list, i pretty much have everything :p:

Re: Virgin Akamai Cache Congestion
 

So Synthetic, Cloudflare seems better now - have you tested at all?

Re: Virgin Akamai Cache Congestion
 

Yeah seems ok now, I can only guess virgin upgraded their links to akamai when nit using their caches.

I'm using nextdns without edns myself and I've had no issues :)

Re: Virgin Akamai Cache Congestion
 

Ah, not heart of next dns, is it better?