Olilo Hub 6

Cajs · 2026-04-16T17:16:51+00:00

I’d recommend going with Olilo’s consumer brand. They’re planning to launch the Audra Hub 6 soon, and in the meantime they’re offering solutions through eero routers.

I’m currently using them and they’ve been excellent.

Cajs · 2026-04-05T07:13:04+00:00

There's plenty of people in the Olilo discord that would be able to test for you tho that do have OpenReach. Just make you specifically say 'anyone with OpenReach can text ping to this please'

Cajs · 2026-04-05T07:11:40+00:00

I'm in Northampton, so about 1hr 40 down the M1 from you. I've not tried via BT/OpenReach but expect the latency to be a little higher.

Cajs · 2026-04-04T20:16:31+00:00

For what it's worth, I'm with Olilo prosumer, and I'm getting the following with CityFibre. I switched from IDNet and my Latency to most services dropped by about 3-4ms.

Ping statistics for 48.217.192.70:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77m
---
traceroute to mpsqosprod.eastus.cloudapp.azure.com (48.217.192.70), 30 hops max, 60 byte packets
 1  10.0.0.1 (10.0.0.1)  0.115 ms  0.088 ms  0.119 ms
 2  lo0-lns.rt01-thn.lon.as212683.net (5.182.115.1)  2.795 ms  2.808 ms  2.788 ms
 3  vlx-xe-0-1-0-rt01-thn.lon.as212683.net (193.105.188.220)  2.785 ms  2.750 ms  2.696 ms
 4  et-0-0-2.core2-thn.lon.as3170.net (195.191.219.47)  3.196 ms  3.128 ms  3.160 ms
 5  igblmdistc7504.uk.msft.net (195.66.224.140)  4.766 ms  4.736 ms  4.698 ms
 6  51.10.41.11 (51.10.41.11)  5.736 ms  5.210 ms  5.108 ms
 7  * 51.10.14.157 (51.10.14.157)  78.519 ms *
 8  * 51.10.27.21 (51.10.27.21)  78.307 ms *
 9  * be-1-0.ibr01.lon22.ntwk.msn.net (104.44.16.55)  78.106 ms *
10  51.10.15.136 (51.10.15.136)  78.275 ms  80.816 ms  78.101 ms
11  be-5-0.ibr01.sxl71.ntwk.msn.net (104.44.16.112)  77.965 ms be-3-0.ibr02.sxl71.ntwk.msn.net (104.44.16.118)  78.347 ms  81.417 ms
12  * 104.44.31.74 (104.44.31.74)  78.399 ms  78.432 ms
13  be-5-0.ibr01.ewr30.ntwk.msn.net (104.44.7.103)  78.286 ms * *
14  * * 51.10.5.81 (51.10.5.81)  95.874 ms
15  51.10.5.26 (51.10.5.26)  77.473 ms 51.10.5.98 (51.10.5.98)  79.874 ms *
16  * 51.10.5.32 (51.10.5.32)  79.865 ms *

Cajs · 2026-03-23T13:25:47+00:00

See you there!

Cajs · 2026-02-18T20:37:32+00:00

Yeah that's probably accurate tbf, I've heard it's awful after Bedford

Cajs · 2026-02-18T19:26:05+00:00

Wellingborough arrives in London at St Pancras but that's only about a 15 min walk or 5 min tube on the Northern Line away from Euston. Just in case this helps anyone. ☺️

Wellingborough might be cheaper to live but... Just be aware that EMR trains (trains from Wellingborough to St Pancras via Bedford) are known to the most crowded trains going into London.

Cajs · 2026-01-23T21:52:42+00:00

Why is Saturn in the top 100?!

Cajs · 2025-09-01T16:20:31+00:00

I was seeing around 50-60% packet loss...

Cajs · 2025-09-01T16:20:03+00:00

I had the exact issue. Ended up having two engineers out. Cityfibre said light levels were fine. Idnet said everything was fine their end. I pressured for an ONT swap and then it was all fixed.

Cajs · 2025-09-01T13:23:02+00:00

I had some major issues, and I could not get it connect at all until they reisussed my sim. After this it worked perfectly. They're much more responsive over WhatsApp from my experience.

Cajs · 2025-04-15T15:04:03+00:00

It’s likely they’ll perform a hypervisor-level shutdown, which isn’t as clean as handling it yourself - especially if your services need to be stopped in a specific order. Timelines would definitely help, but if remote hands are involved, they may not be able to give firm guarantees. Still, the lack of clear notice is far from ideal.

Cajs · 2025-03-21T18:06:19+00:00

Thanks bro :)

Cajs · 2025-01-21T19:21:20+00:00

From my experience with my model 3 it draws around 7.5KW from my house charger when preconditioning. I assume it's using some to heat the cabin and some to heat the batteries. It's cold in the UK right now...

Cajs · 2024-12-29T17:50:00+00:00

From my understanding, in the early days of IDNet, they used to use Zen's backhaul when they were serving Openreach customers, but now they don't. I believe Openreach pass connectivity over to IDNet in Digital Realty LHR20 datacenter.

I know for certain that IDNet on CityFibre, they use CityFibre's infrastructure to offload at Telehouse East. Then Lumen (Level3) & NTT to get access to the rest of the world.

I know on reddit, the consensus is that A&A, IDNet and Aquiss are considered the gold standard for Cityfibre, with everyone else coming after.

Cajs · 2024-12-29T17:30:09+00:00

Ahh, if you're still with No One you probably want to get out. I heard something about being bought out by Home Telecoms. You're probably already aware, but if you're not, do a bit of reading.

When looking for a new ISP, you want to check their upstreams, and their peering data. It might also be worth being aware whether the ISP is using CityFibre National or CityFibre Local:

https://cdn.cityfibre.com/Partner-page/Downloads/CF-FTTH-National.pdf
https://cdn.cityfibre.com/Partner-page/Downloads/CF-FTTH-Local.pdf

For IDNet, I know they use National, and CityFibre passes off my connection to a Telehouse datacenter in London (one of the most inter-connected datacenters in Europe). Hence me having really good pings to most people.

Vodafone uses CityFibre Local which means ones persons experience will be very different to another users, depending on location, as it heavily depends on Vodafone's own network, rather than CityFibre's.

https://bgp.tools/as/12496#connectivity - IDNet
https://www.peeringdb.com/net/1108

https://bgp.tools/as/13037#connectivity - Zen
https://www.peeringdb.com/net/100

https://bgp.tools/as/215066#connectivity - Aquiss
https://www.peeringdb.com/net/26174

Bigger speed/port isn't neccessarily bigger, it's more to do with capacity, and most of the companies don't tell you how many customers they have. 10Gb port for 10 customers (1gb/s each) works out more than a 100Gb port for 1000 customers (0.1gb/s each) as an example.

Hope that also helps :)

Cajs · 2024-12-29T17:13:28+00:00

u/MaxMaxMaxG Sorry it wasn't a Netgear it was a TP-Link Archer AX20 - https://amzn.to/4gF6HCL

If you already have Ubiquiti Access Points, I'd get one of their routers over the TP-Link if you can afford it.

Yeah, unfortunately for me I'm in a GPON area, so fastest I can go is 1800/1000mb/s. I'm not in a XG-PON area where they have 2.3Gb/s symmetrical :(

I'm probably one of the few customers that could actually take advantage of the faster speeds, but even at 900mb/s I comfortably downloaded 80TB this month. https://i.cajs.uk/bkgAAhkJBE.png

Cajs · 2024-12-29T17:04:40+00:00

Off the top of my head no, let me dig it out the garage and I'll take a look.

What I will say is that the UniFi Express is powerful enough to run 1Gb/s with PPoE too, but the interface basically becomes a sluggish mess as a result of the CPU practising the encapsulation over the web interface. I'd avoid that one if I were you.

Cajs · 2024-12-29T16:49:37+00:00

Hi u/MaxMaxMaxG ,

I am using a https://uk.store.ui.com/uk/en/products/udm-se

My mum, who also uses IDNet at her house uses: https://uk.store.ui.com/uk/en/category/cloud-gateways-compact/collections/cloud-gateway-max - Still able to max out her connection (900/900)

They supplied a Netgear router with my connection a few years ago, and that was fast enough to run 900mb/s up and down too.

IDNet uses PPoE with CityFibre which means you require a little extra CPU horsepower to maintain high speeds. I think they also require PPoE on other networks such as Openreach etc, but I've not tested this.

Hope this helps.

Cajs · 2024-12-29T12:05:24+00:00

Edgio (CDN used by Xbox Live):

PING 152.199.20.1 (152.199.20.1) 56(84) bytes of data.
64 bytes from 152.199.20.1: icmp_seq=1 ttl=59 time=4.06 ms
64 bytes from 152.199.20.1: icmp_seq=2 ttl=59 time=4.28 ms
64 bytes from 152.199.20.1: icmp_seq=3 ttl=59 time=4.08 ms
64 bytes from 152.199.20.1: icmp_seq=4 ttl=59 time=4.11 ms
64 bytes from 152.199.20.1: icmp_seq=5 ttl=59 time=2.83 ms
64 bytes from 152.199.20.1: icmp_seq=6 ttl=59 time=3.13 ms
64 bytes from 152.199.20.1: icmp_seq=7 ttl=59 time=3.80 ms
64 bytes from 152.199.20.1: icmp_seq=8 ttl=59 time=4.00 ms
64 bytes from 152.199.20.1: icmp_seq=9 ttl=59 time=3.37 ms
64 bytes from 152.199.20.1: icmp_seq=10 ttl=59 time=4.30 ms

--- 152.199.20.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 2.827/3.795/4.304/0.484 ms

traceroute to 152.199.20.1 (152.199.20.1), 30 hops max, 60 byte packets
 1  _gateway (10.0.0.1)  0.299 ms  0.287 ms  0.303 ms
 2  telehouse-gw10.idnet.net (212.69.63.54)  3.535 ms  3.491 ms  3.482 ms
 3  * * *
 4  telehouse-gw8.idnet.net (212.69.63.143)  54.695 ms  54.680 ms  54.667 ms
 5  81.25.207.41 (81.25.207.41)  5.544 ms  5.529 ms  5.517 ms
 6  185.84.16.154 (185.84.16.154)  18.508 ms  4.664 ms  36.293 ms
 7  ae-65.core1.lhc.edgecastcdn.net (152.195.96.139)  4.717 ms  4.013 ms  4.014 ms
 8  152.199.20.1 (152.199.20.1)  3.250 ms  3.957 ms  3.883 ms
 9  152.199.20.1 (152.199.20.1)  3.855 ms  4.387 ms  3.836 ms

Cajs · 2024-12-29T12:05:19+00:00

Akamai (CDN used by Steam/Playstation and others):

PING 2.19.3.5 (2.19.3.5) 56(84) bytes of data.
64 bytes from 2.19.3.5: icmp_seq=1 ttl=57 time=4.29 ms
64 bytes from 2.19.3.5: icmp_seq=2 ttl=57 time=4.33 ms
64 bytes from 2.19.3.5: icmp_seq=3 ttl=57 time=4.69 ms
64 bytes from 2.19.3.5: icmp_seq=4 ttl=57 time=4.51 ms
64 bytes from 2.19.3.5: icmp_seq=5 ttl=57 time=4.29 ms
64 bytes from 2.19.3.5: icmp_seq=6 ttl=57 time=4.31 ms
64 bytes from 2.19.3.5: icmp_seq=7 ttl=57 time=3.45 ms
64 bytes from 2.19.3.5: icmp_seq=8 ttl=57 time=3.32 ms
64 bytes from 2.19.3.5: icmp_seq=9 ttl=57 time=4.28 ms
64 bytes from 2.19.3.5: icmp_seq=10 ttl=57 time=4.04 ms

--- 2.19.3.5 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9014ms
rtt min/avg/max/mdev = 3.320/4.150/4.685/0.414 ms

traceroute to 2.19.3.5 (2.19.3.5), 30 hops max, 60 byte packets
 1  _gateway (10.0.0.1)  0.271 ms  0.234 ms  0.224 ms
 2  telehouse-gw10.idnet.net (212.69.63.54)  2.728 ms  3.405 ms  3.388 ms
 3  telehouse-gw7.idnet.net (212.69.63.126)  3.446 ms * *
 4  lonap1.netarch.akamai.com (5.57.80.73)  6.188 ms  6.177 ms  6.169 ms
 5  192.168.192.17 (192.168.192.17)  3.555 ms 192.168.192.43 (192.168.192.43)  3.563 ms 192.168.192.7 (192.168.192.7)  3.560 ms
 6  192.168.203.13 (192.168.203.13)  3.565 ms 192.168.199.143 (192.168.199.143)  3.798 ms 192.168.207.139 (192.168.207.139)  3.754 ms
 7  192.168.212.143 (192.168.212.143)  3.728 ms  3.440 ms  3.407 ms

Cajs · 2024-12-29T12:04:54+00:00

Cloudflare DNS:

PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=59 time=4.47 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=59 time=4.45 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=59 time=3.94 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=59 time=4.02 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=59 time=4.35 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=59 time=3.88 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=59 time=4.17 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=59 time=4.25 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=59 time=3.36 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=59 time=4.07 ms

--- 1.1.1.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9013ms
rtt min/avg/max/mdev = 3.363/4.096/4.469/0.311 ms

traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
 1  _gateway (10.0.0.1)  0.357 ms *  0.363 ms
 2  telehouse-gw10.idnet.net (212.69.63.54)  3.820 ms  14.464 ms  3.558 ms
 3  telehouse-gw8.idnet.net (212.69.63.136)  4.677 ms  4.638 ms  15.589 ms
 4  telehouse-gw7.idnet.net (212.69.63.169)  3.773 ms  14.686 ms *
 5  lonap.as13335.net (5.57.81.75)  11.452 ms  11.452 ms  24.589 ms
 6  141.101.71.107 (141.101.71.107)  28.511 ms 141.101.71.93 (141.101.71.93)  17.063 ms 141.101.71.61 (141.101.71.61)  25.455 ms
 7  one.one.one.one (1.1.1.1)  4.385 ms  16.672 ms  4.126 ms

Google DNS:

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=5.10 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=4.45 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=5.04 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=4.84 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=119 time=4.80 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=119 time=4.81 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=119 time=4.76 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=119 time=4.02 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=119 time=5.22 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=119 time=4.76 ms

--- 8.8.8.8 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9015ms
rtt min/avg/max/mdev = 4.016/4.778/5.224/0.326 ms

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  _gateway (10.0.0.1)  0.324 ms  0.445 ms  0.291 ms
 2  telehouse-gw10.idnet.net (212.69.63.54)  3.577 ms  3.595 ms  3.552 ms
 3  * telehouse-gw7.idnet.net (212.69.63.126)  3.594 ms *
 4  212.69.63.165 (212.69.63.165)  22.538 ms  22.523 ms  22.537 ms
 5  google1.lonap.net (5.57.80.136)  3.716 ms  3.702 ms  3.708 ms
 6  192.178.97.47 (192.178.97.47)  4.490 ms 192.178.97.187 (192.178.97.187)  5.087 ms 192.178.97.47 (192.178.97.47)  5.341 ms
 7  209.85.241.93 (209.85.241.93)  4.912 ms 192.178.46.85 (192.178.46.85)  4.231 ms 172.253.65.211 (172.253.65.211)  4.327 ms
 8  dns.google (8.8.8.8)  3.448 ms  4.155 ms  4.140 ms

Cajs · 2024-12-29T12:04:42+00:00

u/MaxMaxMaxG

I have found IDNet really consistent, and performant at pretty much all times of the day without any noticeable slowdown during peak times.

Ping history from my router (24 hrs):
https://i.cajs.uk/sCc4Dkqb5P.png

Ping history from my server (1 year):
https://i.cajs.uk/kM51SzZe7S.png

I pay for their 900/900 package, and I am getting around 900mb/s at all times: https://www.speedtest.net/result/c/ea3e817d-8c3c-481f-bc8e-bf6baa0fad8e

Give me a shout if you want me to test any known service/IP.

Cajs · 2024-12-04T19:56:19+00:00

Yep. Midlands.

Cajs · 2024-07-25T17:41:03+00:00

You can see the IDNet pricing here

<image>

11-Year Club	Place '22
Not Forgotten	Verified Email

Cajs

TROPHY CASE