Latency on IDNet

Aside from the odd intermittent issues which have been reported previously here regarding latency, what are people's experience of 'normal' latency on IDNet?

I have just moved from a Plusnet FTTC product to an IDNet FTTP connection, and latency to London has jumped from 16ms to 22ms - see BQM graphs in my signature (Plusnet line is still active).

What would be the factors influencing this increase?

Is there anyone else from N.Ireland on IDNet who'd care to post their latencies to London for comparison?

Can you post a traceroute to bbc.co.uk out of interest?

I have noticed a difference at times and just want to confirm you are seeing what I am.

Post deleted by beefcakechipz

Sogea 80/20 15ms.

Here's both IPv6 and IPv4 traces:


C:\Users\###>tracert bbc.co.uk

Tracing route to bbc.co.uk [2a04:4e42:200::81]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ###
2 20 ms 31 ms 21 ms 2a02:390:ffff:ffff:ffff:ffff:ffff:fff6
3 20 ms 21 ms 20 ms 2a02:390:0:ff18::
4 21 ms 21 ms 20 ms fastly-gw1.no-dns-yet.lonap.net [2001:7f8:17::d361:1]
5 21 ms 21 ms 21 ms 2a04:4e42:200::81

Trace complete.


C:\Users\###>tracert -4 bbc.co.uk

Tracing route to bbc.co.uk [151.101.128.81]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ###
2 21 ms 20 ms 21 ms redbus-gw11-10G.idnet.net [212.69.63.36]
3 20 ms 20 ms 21 ms 212.69.63.140
4 21 ms 21 ms 22 ms telehouse-gw7-10G.idnet.net [212.69.63.142]
5 21 ms 22 ms 21 ms ip81-59.fastly-gw1.lonap.net [5.57.81.59]
6 21 ms 21 ms 20 ms 151.101.128.81

Okay so you are seeing the same as me. redbus-gw11-10G.idnet.net is around 5-10ms slower for me (am in very north Scotland so the difference will be higher for me) when I am on it.

Reboot your router/reconnect pppoe or leave it off for 5 minutes and see if you get a different node on telehouse.

Edited by Derpy (Fri 02-Sep-22 16:49:42)

Hmm, perhaps I'm wrong but doesn't IDNet use Zen's backhaul?

Zen Internet being the ISP with a common complaint from some customers occasionally ending up on a gateway that results in a higher than expected latency because of Zen's 'load balancing' between gateways instead of choosing the most optimal one (for latency).

I preferred a reboot yesterday evening just after 6pm, unfortunately no improvement:
IPv4
IPv6

I will try again today, perhaps it's luck of the draw!

Edited by uniquorn (Sat 03-Sep-22 14:46:40)

2nd time's a charm!
IPv4
IPv6

I have also re-ran the trace routes:


C:\Users\###>tracert bbc.co.uk

Tracing route to bbc.co.uk [2a04:4e42:600::81]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ###
2 14 ms 13 ms 13 ms 2a02:390:ffff:ffff:ffff:ffff:ffff:fff7
3 14 ms 13 ms 13 ms 2a02:390:0:ff17::
4 13 ms 13 ms 13 ms fastly-gw1.no-dns-yet.lonap.net [2001:7f8:17::d361:1]
5 13 ms 14 ms 13 ms 2a04:4e42:600::81

Trace complete.


C:\Users\###>tracert -4 bbc.co.uk

Tracing route to bbc.co.uk [151.101.0.81]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ###
2 13 ms 13 ms 12 ms telehouse-gw10-10G.idnet.net [212.69.63.54]
3 13 ms 14 ms 13 ms telehouse-gw7-10G.idnet.net [212.69.63.126]
4 12 ms 12 ms 13 ms ip81-59.fastly-gw1.lonap.net [5.57.81.59]
5 12 ms 13 ms 13 ms 151.101.0.81

Trace complete.


IPv6 observations:
* 2nd hop seems to be where the latency was induced. When latency was 20-31ms this hop was 2a02:390:ffff:ffff:ffff:ffff:ffff:fff6, now at 13-14ms, second hop is 2a02:390:ffff:ffff:ffff:ffff:ffff:fff7

IPv4 observations:
* Again, 2nd hop seems to be where the latency was induced. When latency was 20-21ms this hop was redbus-gw11-10G.idnet.net, now at 12-13ms, second hop is telehouse-gw10-10G.idnet.net
* Also, there was an additional hop before telehouse-gw7-10G.idnet.net when things were slower: 212.69.63.140


I'll contact IDNet to see if they have any solutions on their end. Failing that I may look into some of the posts which people have made about automating WAN reconnection based on ping response.

I've found that with IDNet if your latency is high (in my case anything above 8ms) then you need to force a PPPoE reconnect. I'm on the 550/75 package using BT Wholesale backhaul (according to IDNet).

If my latency climbs up after a router update or some other reason I just keep reconnecting the PPP session by removing the 't' from the username, save the settings, then add it back and save settings again whilst running a ping directly from the router (UDM Pro).

I'm in Kent and here is a ping and trace route (directly from router) and my BQM for info:

# sudo ping -c 6 pingbox1.thinkbroadband.com
PING pingbox1.thinkbroadband.com (80.249.99.164): 56 data bytes
64 bytes from 80.249.99.164: seq=0 ttl=60 time=4.745 ms
64 bytes from 80.249.99.164: seq=1 ttl=60 time=4.817 ms
64 bytes from 80.249.99.164: seq=2 ttl=60 time=4.863 ms
64 bytes from 80.249.99.164: seq=3 ttl=60 time=4.927 ms
64 bytes from 80.249.99.164: seq=4 ttl=60 time=4.900 ms
64 bytes from 80.249.99.164: seq=5 ttl=60 time=4.780 ms

--- pingbox1.thinkbroadband.com ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 4.745/4.838/4.927 ms
# traceroute pingbox1.thinkbroadband.com
traceroute to pingbox1.thinkbroadband.com (80.249.99.164), 30 hops max, 46 byte packets
1 telehouse-gw10-10G.idnet.net (212.69.63.54) 4.449 ms 4.635 ms 4.488 ms
2 telehouse-gw7-10G.idnet.net (212.69.63.126) 4.689 ms 4.575 ms 4.667 ms
3 ae2-112.edge-rt5.thdo.ncuk.net (80.249.97.109) 4.689 ms 4.539 ms 4.541 ms
4 te1-51-36.core-rs3.thdo.ncuk.net (80.249.97.72) 4.816 ms 4.898 ms 4.890 ms
5 po5-32.core-rs4.thdo.ncuk.net (80.249.97.90) 4.808 ms 4.856 ms 4.819 ms
6 pingbox1.thinkbroadband.com (80.249.99.164) 4.658 ms 4.621 ms 4.621 ms

My Broadband Ping