iDNET speed test — is your broadband delivering what you pay for?

Published 11 April 2026 · Last updated 11 April 2026 · Written by UKSpeedTest Editorial Team · Reviewed by Dr Alex J Martin-Smith · Sources checked 11 April 2026

Who this page is for

This guide is for iDNET households who're already paying for a package — or weighing one up — and want honest interpretation, not a brand brochure. Maybe you're new and trying to validate install performance, or you've lived with iDNET for years and evening slowdowns have started to bite. You'll leave with a repeatable test method using Pulse, a clearer idea of what "good" looks like on Openreach access (iDNET retail), and a practical escalation path if speeds stay poor after fair testing. We're not here to dunk on iDNET; we're here to help you separate Wi-Fi mess from line mess, then decide what to do next.

iDNET in context — speeds, hardware, and how the network behaves

Network type and what it means day to day

iDNET delivers broadband using iDNET typically sells over Openreach FTTP where available — differentiation is service ethos and networking policies more than bespoke last-mile construction.. In practical terms, that shapes whether your speed tests reflect a dedicated fibre path to the cabinet/premises, a shared medium, or wireless backhaul. Latency and jitter behave differently on each: FTTP latency is usually stable — your firewall might not be.. For everyday use, you'll notice this most when several people stack video calls, gaming, and 4K streaming — not when you're only reading email. If you're comparing iDNET with a friend on another ISP, match technology first; otherwise you're comparing apples with oranges.

Typical real-world speeds (with a named source)

Premium pricing demands premium testing methodology — fair Ethernet first. Ofcom's Home Broadband Performance reporting and the Opensignal Fixed Broadband Experience Report (July–September 2025) are useful directional benchmarks, but your postcode and package tier still dominate. Compare against guarantees and real usage — not bragging rights. Treat marketing "up to" figures as ceilings, not promises on every device in every room.

Peak-time behaviour and contention

iDNET customers often report the sharpest dips between 7pm–10pm, when neighbourhoods light up with streaming and downloads. Peak issues still happen — physics doesn’t recognise “premium”. If your Pulse results collapse only on Wi-Fi at the far end of the house but stay steady on Ethernet near iDNET-supplied router or BYOR depending on product, you're likely seeing home wireless limits, not necessarily iDNET core congestion. Keep a three-day log before you claim it's "the network".

Router and hardware specifics

iDNET typically supplies iDNET-supplied router or BYOR depending on product — static IP users should avoid double NAT mistakes. Log into the admin UI (often 192.168.1.1) to check firmware status, rename bands if you're debugging steering, and confirm nothing odd is throttling Ethernet. Advanced users add complexity — measure simply first. For fair testing, disable VPNs on the test laptop, close heavy tabs, and use a decent Cat5e/Cat6 cable if you're chasing high headline speeds.

Pricing context and speed-for-money

iDNET competes on experience — still compare renewal pricing honestly. If you're trying to judge value, compare what you pay per month against the speeds you actually measure on Ethernet during busy hours — that's the speed-for-money line that matters, not a billboard on the motorway.

How to run a fair iDNET speed test (step by step)

1. Step 1. Pause the heaviest household traffic first — big game downloads, cloud photo uploads, and smart-TV updates — then connect a laptop directly to iDNET-supplied router or BYOR depending on product with Ethernet. You're not trying to impress anyone with a Wi-Fi number; you're isolating iDNET's delivered performance from airtime contention. If someone starts a 4K stream mid-test, you'll waste everyone's time and blame the wrong layer.

2. Step 2. Open iDNET's router admin at 192.168.1.1 in a fresh browser window and confirm you're on the latest firmware channel shown in the settings panel. Note whether "smart Wi-Fi" or band steering is enabled: it can push a phone to 2.4 GHz right before you test, which won't reflect your fibre capability. If you're debugging odd Wi-Fi scores, temporarily split SSIDs only if you know how — don't strand IoT devices without a plan.

3. Step 3. On mobile, open iDNET customer portal if iDNET publishes live service status or line tests — run any built-in diagnostics before Pulse so support can't wave away your ticket as "unknown line state". Screenshot the results with timestamps; you'll want them beside Pulse outputs. If the app shows an outage banner but your wired Pulse looks fine, capture both — contradictions happen when DNS or routing paths differ.

4. Step 4. Run Pulse from the Oxford household's wired laptop with only that tab active. Record download, latency, and jitter, then immediately run a second test two minutes later — if both are stable within a sensible margin, you've got a credible pair. Keep the laptop on mains power; battery saver modes can throttle radios and confuse you.

5. Step 5. Repeat the same pair between 7pm–10pm on a weekday — that's when iDNET customers most often notice contention on Openreach access (iDNET retail). If daytime and evening wired results diverge massively while your home load is stable, you've got evidence worth sending upstream. If only Wi-Fi diverges, fix placement before you open a network fault.

6. Step 6. If results look wrong, swap DNS temporarily on the test device (not the whole LAN if you're unsure) to rule out sluggish resolver paths . Then reboot iDNET-supplied router or BYOR depending on product once, cold-start, retest wired, and log everything in one note: date, time, weather if wireless sneaks in, and which port you used. One clean story beats five angry paragraphs.

Real UK household scenario

In Oxford, iDNET’s line was pristine; the customer’s pfSense clone was not. A clean baseline test ended the saga.

Common iDNET-specific speed issues

• Power users can overwhelm support with lab configs — simplify tickets.
• “No traffic management” doesn’t fix bad Wi-Fi — test fairly.
• Static IP routing errors masquerade as slow DNS.
• Don’t expect consumer-style “free mesh” — buy infrastructure.
• Premium means higher expectations — bring evidence.

What to do if iDNET speeds stay consistently low

Start inside iDNET's own support channels: iDNET phone and ticket support. Keep a calm fault narrative with dates, postcode, package name, and whether tests were on Wi-Fi or Ethernet — support teams respond better when you sound organised, not angry. iDNET is not listed on Ofcom's Automatic Compensation Scheme membership list in the same way as several larger national ISPs. That doesn't remove your statutory rights, but it does mean you shouldn't assume automatic payouts for missed appointments or delayed repairs unless your contract explicitly says so. You'll still escalate through iDNET phone and ticket support first, then CISAS or Ombudsman Services: Communications if you remain stuck. Keep dated evidence from fair Pulse tests on Ethernet, screenshots, and any fault reference numbers. For rights context, read our slow broadband rights guide before you threaten to leave.

If you're still stuck after eight weeks or hit a deadlock letter, Ofcom-approved Alternative Dispute Resolution routes such as CISAS or Ombudsman Services: Communications can look at eligible complaints. Our slow broadband rights in the UK page walks through realistic expectations. If repeated fair tests show iDNET can't deliver what you need at your address, compare options on BroadbandSwitch.uk — switching isn't always the answer, but it's sometimes the honest one.

FAQ

Related guides

• How to run an accurate broadband speed test — wire-first checks and fair repeat testing.
• UK broadband rights when speeds stay low — what you can ask for before you switch.
• UK broadband speed by provider — compare all ISPs — hub page with typical speeds and links.
• UK speed test comparison — Pulse vs Ookla vs Fast.com — how tools differ.
• How network congestion affects home broadband
• Pulse methodology — what we measure and what we do not.
• Run the Pulse speed test on the homepage tool.

References

1. Ofcom: broadband speeds code of practice (consumer guide)
2. Opensignal — UK Fixed Broadband Experience Report (methodology hub)
3. iDNET — provider help or speeds (verify current URL)