Trust

How we check our facts

Every answer on this site is dated, comes from a real source, and can be double-checked. We publish our rules here so you can hold us to them — and tell us if we get something wrong.

Where our information comes from, in order of trust

  1. 1Current regulator or government cyber advisory
  2. 2Current official ISP or router-vendor support / PSIRT bulletin
  3. 3Standards body or primary technical research
  4. 4Reputable industry publication
  5. 5Mainstream newspaper report
  6. 6Moderated vendor community
  7. 7Reddit or social post — investigation lead only

A less reliable source can raise a question, but it never settles one on its own. News reports are checked against the original manufacturer or official notice before we publish anything.

The rules we answer by

1. Identify platform

We always: Resolve ISP, router/mesh family and exact model before giving menu paths.

We never: Do not blend eero, Plume, Calix, BT, Sky or Virgin instructions.

2. Isolate fault domain

We always: Separate access/WAN, gateway, Wi‑Fi radio, LAN and third-party app/device.

We never: Do not label every symptom a broadband or Wi‑Fi fault.

3. Evidence first

We always: Use telemetry, wired/gateway comparison, timestamps and affected-device scope.

We never: Do not claim causation from one speed test, RSSI value or forum post.

4. Least disruption

We always: Use targeted reconnect/restart/config check before gateway reboot or reset.

We never: No factory reset, blanket port opening or security downgrade as an early step.

5. Security/privacy

We always: Verify account authority; minimise data; preserve safeguarding and network segmentation.

We never: Never expose credentials/IPs, bypass parental controls, or reveal another user’s activity.

6. Safety/voice

We always: Warn that reboot/power loss can interrupt VoIP, alarms and monitoring; follow vulnerable-customer policy.

We never: Never provide generic reassurance about 999 availability in a power cut.

7. Third-party boundary

We always: Diagnose and hand off with evidence when Wi‑Fi is healthy but app/device fails.

We never: Do not request third-party passwords or guarantee third-party services.

8. Source hierarchy

We always: Official current vendor/ISP/regulator source > standards/technical vendor > moderated community > forum anecdote.

We never: Do not present Reddit/Facebook advice as authoritative.

9. Change control

We always: Explain feature loss/rollback before bridge, WPA, DNS, channel, VLAN or NAT changes.

We never: No high-impact remote change without consent and supported procedure.

10. Human escalation

We always: Escalate optical/WAN faults, safety-critical cases, security incidents and advanced network design.

We never: Do not improvise beyond documented capability.

Why you can trust us to be independent

No one can pay for a better score

A provider's ranking and score cannot be bought, and no provider gets to see or change a score before it's published.

We show our working

We publish exactly how we score things, so anyone can check or challenge a result.

Safety warnings name the exact model

A safety warning always names the specific model, version and software range — never just a brand.

Mistakes get corrected

Anyone — a reader, a provider, a manufacturer — can challenge something we've written if they can show us a reliable source. We date and publish the outcome.

Full list of our sources

24 sources back up everything in our knowledge base. Every answer links to the source it relies on.

Show the full source list
ReferencePublisherAuthority
eero24eeroOfficial/current unless labelled community
eeroBridgeeeroOfficial/current unless labelled community
eeroSpeedeeroOfficial/current unless labelled community
eeroRadioeeroOfficial/current unless labelled community
eeroAdveeroOfficial/current unless labelled community
eeroEncrypteeroOfficial/current unless labelled community
eeroDeviceeeroOfficial/current unless labelled community
plume24PlumeOfficial/current unless labelled community
sonosSonosOfficial/current unless labelled community
sonosChanSonosOfficial/current unless labelled community
ringRingOfficial/current unless labelled community
hpHPOfficial/current unless labelled community
skyQSkyOfficial/current unless labelled community
skyBoostSkyOfficial/current unless labelled community
btWifiBTOfficial/current unless labelled community
btSplitBTOfficial/current unless labelled community
btPlaceBTOfficial/current unless labelled community
btChannelBTOfficial/current unless labelled community
plusSignalPlusnetOfficial/current unless labelled community
virginVirgin MediaOfficial/current unless labelled community
ofcomOfcomOfficial/current unless labelled community
ciscoCiscoOfficial/current unless labelled community
ripeRIPE communityOfficial/current unless labelled community
redditSonosRedditOfficial/current unless labelled community

This page was last reviewed 17 August 2026.