Hyperoptic broadband checker
Hyperoptic broadband checker for building-level full fibre
Use this Hyperoptic broadband checker guide to understand whether the service is available in your building or flat, then jump into router, upload, Wi-Fi and building-network checks if performance feels poor.
Checking alternatives in your building?
Some apartment blocks now have several fibre options. Compare Hyperoptic against other networks serving the exact building, not just the postcode.
Hyperoptic broadband checker
Start with the Hyperoptic building/address check, then validate real performance with wired upload, download, latency and Wi-Fi tests. This keeps building availability and existing-connection troubleshooting together.
- Check Hyperoptic availability: Confirm whether Hyperoptic serves the exact building, not just the surrounding postcode or street.
- Interpret flat-level results: Apartment blocks can have building-specific availability, internal cabling and neighbouring Wi-Fi congestion that affect real performance.
- Separate package from performance: A fast full-fibre estimate can still be limited by router placement, older devices or dense flat Wi-Fi.
Hyperoptic building-switch and router isolation path
Separate the building feed from the flat network. Test Ethernet at the router, then repeat near the router and in rooms behind walls or corridors where 5GHz Wi‑Fi can collapse quickly.
FTTB versus FTTP clue: Hyperoptic can be delivered as fibre-to-the-building, where fibre terminates at a building switch and the final run into the flat uses an internal Cat5e or Cat6 wall faceplate, or as fibre-to-the-premises, where an optical wall terminal or CPE/ONT sits inside the flat. If a faceplate-fed service is unstable, check the wall socket and Ethernet lead first; if a powered optical terminal is present, confirm the LAN1-to-WAN cable runs directly into the HyperHub before replacing the router.
For Hyperoptic upload issues or video-call drops, run the upload speed test, then use the Loaded Latency Test and Packet Loss Test during calls or cloud backup.
Diagnosing Hyperoptic flat and upload-speed symptoms
- Ethernet upload is strong: focus on Wi‑Fi channel congestion or device limits.
- Only one room is poor: test hallway/wall effects and router placement.
- Upload is low over Ethernet: record repeated wired results before raising a service issue.
Hyperoptic HyperHub status lights
Hyperoptic flats may use a ZTE HyperHub, Nokia HyperHub or similar router connected to a building switch, wall faceplate or optical terminal. Check the WAN/Internet light state before changing Wi‑Fi settings.
| Hub light status | What it usually means | Most useful action |
|---|---|---|
| Solid green Internet / WAN | The HyperHub has established a usable IP session with the building switch, wall terminal or upstream Hyperoptic network. | The incoming feed is likely healthy. Move on to Wi‑Fi congestion, room placement or device capability checks. |
| Flashing amber / green WAN | The router is looking for an upstream link or waiting for a DHCP/authentication handshake. | Normal during reboot. If it persists, check the flat wall socket, Ethernet lead and any optical terminal or CPE power state. |
| Solid red Internet / WAN | The cable may be connected but the upstream switch or account session is not authenticating. | Power-cycle the hub for 30 seconds, then check Hyperoptic network status. If it returns, report the light state and wall/terminal setup. |
| Flashing purple / red | The hub may be applying firmware, recovering configuration or entering a managed update state. | Do not pull the power during an update window. Wait up to 15 minutes before restarting or replacing cables. |
HyperHub admin panel: while connected to the router, try http://192.168.1.1 for many ZTE models or http://192.168.1.254 for some Nokia/alternate hub setups. Use the admin password printed on the hub label if it has not been changed.
Optimising Hyperoptic in flats and apartment blocks
- Upload baseline: Symmetrical packages make upload testing as important as download testing.
- Dense Wi‑Fi environment: Neighbouring networks in flats can reduce Wi‑Fi reliability even on a strong line.
- Router placement: Avoid hiding the router in cupboards or behind TV units near building-entry points.
- Wired workstations: Use Ethernet for home-office desks or cloud-backup devices if Wi‑Fi congestion is high.
- FTTB/FTTP cabling: Identify whether the HyperHub connects to an internal Cat5e/Cat6 wall faceplate or a powered optical terminal so support can separate a flat socket issue from a wider building feed fault.
High-density apartment Wi‑Fi channel congestion
If Hyperoptic is fast over Ethernet but unstable over Wi‑Fi, the issue is often channel overlap from neighbouring flats rather than a bad fibre line. Automated channel selection can place many routers on the same 5GHz block.
- Open the HyperHub manager: sign in at the hub admin page and look for WLAN or Advanced Wireless settings.
- Reduce channel width: if 5GHz is using 80MHz or 160MHz in a dense block, test a narrower 40MHz profile to reduce overlap and improve consistency.
- Try DFS channels carefully: where the router allows it, test a higher 5GHz DFS channel such as 52, 60 or 100. These can be quieter in apartment blocks, but the router may move channel if radar detection requires it.
- Keep wired for critical devices: use Ethernet for workstations, consoles or cloud-backup devices when neighbouring Wi‑Fi makes latency unpredictable.
Hyperoptic upload and building-network checklist
Collect evidence that distinguishes the building feed from flat-level Wi‑Fi and device constraints.
- Run wired download and upload tests from the router.
- Repeat over Wi‑Fi in the rooms where calls or backups fail.
- Run loaded latency during a cloud upload or video call.
- Identify whether the flat uses an FTTB Cat5e/Cat6 wall faceplate or an FTTP optical terminal/CPE and photograph the cabling path.
- Record the HyperHub WAN/Internet light state before rebooting.
- Note 5GHz channel width and channel number if neighbouring apartment Wi‑Fi appears to be the bottleneck.
- Record whether neighbours or building-wide notices suggest local maintenance.
Hyperoptic fault pattern table
| Hyperoptic symptom | Most useful next check | Likely fault layer |
|---|---|---|
| Upload poor over Wi‑Fi only | Run a wired upload speed test. | Wi‑Fi or device limit |
| One room is slow | Use Wi‑Fi isolation. | Walls or congestion |
| Calls fail during backup | Run the Loaded Latency Test. | Loaded latency |
| Ethernet speed is low | Keep repeated wired results and contact support. | Building or service issue |
| HyperHub WAN light stays solid red or amber | Use the HyperHub status light key and check the flat wall faceplate or optical terminal link. | Building switch authentication or physical socket fault |
| Erratic Wi‑Fi drops during busy evening hours | Use the apartment Wi‑Fi congestion checks and test 40MHz or DFS 5GHz channels. | High-density urban channel overlap |
Hyperoptic broadband issues and checks
Use this anchor when a visitor lands from a Hyperoptic checker query but actually needs help with upload speed, flat Wi-Fi, building-network issues or connection stability.
Check wider Hyperoptic service issues first
Before changing router placement or Wi‑Fi settings in a flat, check Hyperoptic’s official network-status page for local disruption or planned maintenance.
Open Hyperoptic official network status ↗- Slow Hyperoptic speeds: Run a wired download and upload test at the router before judging Wi-Fi in a flat.
- Hyperoptic upload issues: Compare wired upload with Wi-Fi upload to identify device, adapter or congestion limits.
- Hyperoptic Wi-Fi problems: Test same-room Wi-Fi and the weakest room to separate building feed from flat-level coverage.
- Hyperoptic dropouts: Keep packet-loss results and timestamps so a building or service issue is not confused with ordinary Wi-Fi range loss.
- HyperHub light states: Record solid green, amber/green, solid red or purple/red WAN states before replacing cables or changing channels.
- Apartment Wi‑Fi congestion: Test 40MHz 5GHz width or a quieter DFS channel if Ethernet is strong but evening Wi‑Fi becomes erratic.
- FTTB versus FTTP cabling: Check whether the flat uses a Cat5e/Cat6 faceplate or a powered optical terminal before reporting a building fault.
When Hyperoptic troubleshooting is no longer enough
If Hyperoptic is strong over Ethernet, fix router placement, Wi‑Fi channel congestion, FTTB/FTTP cabling and device limits first. If the HyperHub stays red, the wall faceplate or optical terminal path is suspect, or wired upload/download remains poor across repeated tests, preserve the evidence and compare building-specific alternatives before renewal.