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.
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
- 1Current regulator or government cyber advisory
- 2Current official ISP or router-vendor support / PSIRT bulletin
- 3Standards body or primary technical research
- 4Reputable industry publication
- 5Mainstream newspaper report
- 6Moderated vendor community
- 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
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.
Working with technology vendors
WiFiXpert may receive technical information, documentation, product access, equipment, vendor briefings or sponsorship.
- Commercial relationships do not determine editorial conclusions. Reviews, recommendations, rankings, comparisons and AI answers stay ours.
- "Vendor Verified" means factual technical verification only. It does not mean WiFiXpert endorses the product.
- Sponsored content is always clearly identified.
- We label information as Vendor Verified, Independent WiFiXpert Research or Community Reported so you can see where it came from.
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
| Reference | Publisher | Authority |
|---|---|---|
| eero24 ↗ | eero | Official/current unless labelled community |
| eeroBridge ↗ | eero | Official/current unless labelled community |
| eeroSpeed ↗ | eero | Official/current unless labelled community |
| eeroRadio ↗ | eero | Official/current unless labelled community |
| eeroAdv ↗ | eero | Official/current unless labelled community |
| eeroEncrypt ↗ | eero | Official/current unless labelled community |
| eeroDevice ↗ | eero | Official/current unless labelled community |
| plume24 ↗ | Plume | Official/current unless labelled community |
| sonos ↗ | Sonos | Official/current unless labelled community |
| sonosChan ↗ | Sonos | Official/current unless labelled community |
| ring ↗ | Ring | Official/current unless labelled community |
| hp ↗ | HP | Official/current unless labelled community |
| skyQ ↗ | Sky | Official/current unless labelled community |
| skyBoost ↗ | Sky | Official/current unless labelled community |
| btWifi ↗ | BT | Official/current unless labelled community |
| btSplit ↗ | BT | Official/current unless labelled community |
| btPlace ↗ | BT | Official/current unless labelled community |
| btChannel ↗ | BT | Official/current unless labelled community |
| plusSignal ↗ | Plusnet | Official/current unless labelled community |
| virgin ↗ | Virgin Media | Official/current unless labelled community |
| ofcom ↗ | Ofcom | Official/current unless labelled community |
| cisco ↗ | Cisco | Official/current unless labelled community |
| ripe ↗ | RIPE community | Official/current unless labelled community |
| redditSonos ↗ | Official/current unless labelled community |
This page was last reviewed 17 August 2026.