Community Fibre broadband checker
Community Fibre broadband checker for London full fibre
Use this Community Fibre broadband checker guide to understand whether Community Fibre is available at your London address, then jump into ONT, router, multi-gig and Wi-Fi checks if performance feels poor.
Compare London full-fibre alternatives
Before renewing, check whether Hyperoptic, Virgin Media, Openreach FTTP or another altnet competes at your specific London property.
Community Fibre broadband checker
Start with the Community Fibre address check, then validate real performance with capable wired devices, upload tests and latency checks. This keeps availability and full-fibre troubleshooting together.
- Check Community Fibre availability: Confirm whether Community Fibre serves the exact London address or building before comparing packages.
- Interpret multi-gig packages: Check device interfaces, cables and router ports before assuming the service is underperforming.
- Separate package from performance: Very fast symmetrical service can still be limited by old hardware, Wi-Fi or local router queueing.
Community Fibre ONT, router and device-capability isolation path
Begin with the ONT/router handoff and a wired test on a capable device, then compare Wi‑Fi and room-level results. Multi-gigabit packages require stronger hardware than basic broadband.
For Community Fibre speed that looks impressive at the router but poor on devices, run the speed checker, then test latency under load with the Loaded Latency Test and Bufferbloat Test.
Diagnosing Community Fibre hardware bottlenecks
- Router-side speed is high: check device network cards, Wi‑Fi generation and cables.
- Upload is lower than expected: verify wired capability before blaming the line.
- All devices unstable: check ONT lights, the Linksys node state, packet loss and the ONT-to-router cable before assuming Wi‑Fi.
Community Fibre Adtran ONT and Linksys Velop status lights
Community Fibre runs pure fibre-to-the-home, so check the wall-mounted Adtran ONT and the Linksys Velop or Velop Pro 6E master node before changing Wi‑Fi settings. The lights separate an external fibre fault from a local router or mesh issue.
| Hardware light status | What it usually means | Most useful action |
|---|---|---|
| ONT power and PON steady green | The Adtran ONT has power and the fibre path is registered with Community Fibre's central node. | The incoming fibre signal is likely healthy. Move on to the ONT-to-router Ethernet cable, router port and local Wi‑Fi checks. |
| ONT LOS blinking or solid red | Loss of signal. The optical feed is not reaching the ONT correctly, often because of an external fibre, micro-duct, splice or terminal-box fault. | Do not keep rebooting the Linksys node. Photograph the LOS light and report a line fault to Community Fibre support. |
| Linksys Velop solid blue | The master node has completed its WAN DHCP handshake and is broadcasting normally. | If rooms feel slow, check device network cards, Ethernet port speed, Wi‑Fi channel conditions and mesh placement. |
| Linksys Velop solid red | The node is powered but cannot obtain an IP allocation from the Adtran ONT. | Power down both devices for 60 seconds. Start the ONT first, wait two full minutes for stable green lights, then power the Linksys node and check the ONT-to-router cable. |
| Linksys mesh node solid yellow | A satellite node has weak or marginal wireless backhaul to the master router. | Move it closer to the master node or use Cat6 wired Ethernet backhaul where walls or apartment layouts weaken the wireless hop. |
Optimising Community Fibre full-fibre performance
- Network card check: Gigabit and multi-gig services need a device interface capable of receiving the speed. Standard 1Gbps ports will normally top out around 940Mbps.
- Cable path: Use known good Cat6a or Cat7 cabling for multi-gig paths, especially between the ONT, Velop Pro 6E router, multi-gig switch and test device.
- Router location: Place the router centrally or use wired backhaul for large London properties.
- Upload testing: Symmetrical service value is best judged with upload as well as download results.
- Correct port path: On multi-gig tiers, make sure the high-speed device or switch is connected to the multi-gig WAN/LAN port on the Velop Pro 6E, not a standard 1Gbps LAN port.
Break the 940Mbps multi-gig port trap
A 3Gbps or 5Gbps Community Fibre package can still test at roughly 940Mbps if the PC, switch, cable path or router port is limited to ordinary gigabit Ethernet. This is a hardware bottleneck, not automatically a provider fault.
- Find the multi-gig port: use the highlighted multi-gig WAN/LAN port on the Linksys Velop Pro 6E for the high-speed device or multi-gig switch. Standard LAN ports can cap the path at 1Gbps.
- Upgrade the client device: a normal motherboard Ethernet port is often 1Gbps only. For multi-gig testing, use a 2.5G or 10G PCIe card, a multi-gig USB adapter, or a Thunderbolt 3/4 to 10Gb Ethernet adapter.
- Use the right cabling: use certified Cat6a or Cat7 pure copper patch leads for the ONT-to-router, router-to-switch and switch-to-device path. Replace suspect patch leads before reporting a speed fault.
- Remove hidden 1Gbps devices: old switches, wall plates, docking stations and mesh nodes can silently downrate the path even when the package and router are multi-gig capable.
Community Fibre CGNAT, IPv6 and strict NAT errors
Community Fibre may place residential connections behind carrier-grade NAT, or CGNAT, depending on package and account status. CGNAT lets multiple homes share public IPv4 space, but it also means normal inbound IPv4 port forwarding will not work unless the connection has a public IPv4 address.
- Spot CGNAT quickly: compare the WAN IPv4 address shown in the Linksys or router dashboard with a public “what is my IP” result. If they differ, the router is probably behind CGNAT.
- Gaming strict NAT symptoms: PlayStation, Xbox, game lobbies, local server hosting, smart-home hubs and security camera access can show strict NAT, double NAT or unreachable-service errors when they rely on inbound IPv4 ports.
- Enable IPv6 first: in the Linksys app or router dashboard, enable IPv6 using Automatic, DHCPv6 or passthrough/prefix-delegation settings where available. If the console or device supports IPv6, this can bypass many IPv4 NAT limitations.
- Check the device result: after enabling IPv6, restart the console, PC or smart-home hub and re-run the network test. Look for an IPv6 address and an open/working IPv6 path rather than only the IPv4 NAT type.
- When IPv4 port mapping is essential: legacy CCTV, self-hosted servers, older VPN concentrators and some game-hosting setups still need a routable IPv4 address. In that case, contact Community Fibre and ask for the public IPv4 add-on so port forwarding can work normally.
Community Fibre multi‑gig evidence checklist
Record whether hardware, cabling or Wi‑Fi is limiting the service before changing package or router.
- Record ONT power, PON and LOS lights, plus the Linksys Velop blue/red/yellow state before rebooting.
- Run a wired test on the fastest available device.
- Check cable, router port and network-adapter capability if results cap around 940Mbps or below the package speed.
- Run upload and download tests separately.
- Run packet-loss tests if calls or games fail despite high speed.
- Record whether Community Fibre Safe or any account-level security profile is enabled if only one app, VPN or game launcher fails.
- Check whether the router is behind CGNAT and whether IPv6 is enabled if consoles, VPNs, security cameras or self-hosted services report strict NAT or unreachable ports.
Community Fibre fault pattern table
| Community Fibre symptom | Most useful next check | Likely fault layer |
|---|---|---|
| Multi‑gig package tests below expectation | Check Ethernet and device limits. | NIC, cable or switch |
| Upload poor on one device | Run another wired speed check. | Device or adapter |
| Latency spikes during uploads | Run the Bufferbloat Test. | Router queueing |
| Random drops | Run the Packet Loss Test. | Stability or hardware path |
| Adtran ONT LOS light is red | Use the ONT light diagnostic key and photograph the LEDs before contacting support. | External fibre, splice, terminal-box or ONT fault |
| Linksys Velop node is solid red | Restart the ONT first, wait two full minutes, then restart the Linksys node and replace the Ethernet lead if needed. | WAN DHCP, ONT-to-router cable or router state |
| 3Gbps or 5Gbps package caps around 940Mbps | Use the multi-gig port trap checklist. | 1Gbps NIC, switch, port or cable bottleneck |
| Console shows strict NAT or port forwarding will not work | Use the CGNAT and IPv6 checks, then ask for a public IPv4 add-on if legacy port mapping is essential. | CGNAT, IPv6 configuration or public IPv4 availability |
| VPN, payment page or anti-cheat launcher loops | Run the Community Fibre Safe isolation test. | Account-level filtering or security profile |
Community Fibre broadband issues and checks
Use this anchor when a visitor lands from a Community Fibre checker query but actually needs help with speed caps, upload issues, ONT/router checks or Wi-Fi problems.
Check wider Community Fibre service issues first
Before changing router, ONT or Wi‑Fi settings, check Community Fibre’s official service-status page for current network issues affecting multiple customers or addresses.
Open Community Fibre official service status ↗Community Fibre Safe app and VPN filtering checks
If wired speed tests are strong but one corporate VPN, secure payment page, strict game anti-cheat launcher or console lobby loops indefinitely, test account-level filtering before treating it as a line fault.
- Open My Account: sign in to the online Community Fibre account dashboard for the broadband plan.
- Check plan features: look for Community Fibre Safe, security filtering, parental controls or safe-browsing options applied to the connection.
- Run a short isolation test: toggle the safety filtering profile off, confirm the change and allow around 10 minutes for the profile update to apply.
- Restart the affected device: relaunch the VPN client, payment flow, console, game launcher or streaming app and repeat the exact failing action.
- Restore deliberately: if the filter was responsible, keep a note of the affected service before deciding whether to re-enable protection or manage security locally.
- Slow Community Fibre speeds: Run a wired test on the fastest available device with a known good cable.
- Community Fibre upload issues: Compare wired upload with Wi-Fi upload so adapter or device limits are not misread as a line fault.
- Community Fibre multi-gig bottlenecks: Check NIC, switch, cable and router-port capability if results cap below the package speed.
- Community Fibre Wi-Fi problems: Compare same-room Wi-Fi with wired results before changing plan or router.
- Community Fibre ONT lights: Record Adtran power, PON and red LOS states before repeatedly rebooting the Linksys node.
- Linksys Velop faults: Solid blue usually points to a working router session; solid red points to the ONT-to-router WAN path; yellow satellite nodes suggest weak mesh backhaul.
- Multi-gig speed caps: Check for 1Gbps NICs, switches, LAN ports and old cables if a 3Gbps or 5Gbps package tops out around 940Mbps.
- Community Fibre CGNAT / IPv6: Enable IPv6 and check for CGNAT if consoles show strict NAT, inbound port forwarding fails, or smart-home access cannot reach the home network remotely.
- Community Fibre Safe blocks: Disable the account-level safety profile briefly if a VPN, payment page or game launcher fails while ordinary browsing works.
When Community Fibre troubleshooting is no longer enough
If Community Fibre is fast over Ethernet, focus on device interfaces, cabling, router ports, CGNAT/IPv6 settings, Community Fibre Safe filtering and Wi‑Fi hardware first. If the ONT shows a red LOS light, the Linksys node cannot pull a WAN address after an ONT-first restart, IPv4 port forwarding requires a public address add-on, or the direct multi-gig wired path remains unstable with known-good hardware, preserve the evidence and compare support or alternatives available at the exact London address.