Slow speeds
Compare wired and Wi-Fi results, router behaviour and the connection setup before deciding the fibre service is at fault.
Fibre and internet troubleshooting
Slow fibre or repeated dropouts can interrupt calls, payments and everyday work. I help separate equipment and Wi-Fi problems from provider faults, then turn the findings into a clear fix or a useful support ticket.
Tell me about your connection problemOr call 021 125 1395.
All support is remote across New Zealand. I can review connection evidence and help prepare a clear provider fault report. You, your internet provider or a local technician handles physical cabling and equipment checks.
Compare wired and Wi-Fi results, router behaviour and the connection setup before deciding the fibre service is at fault.
Look for patterns in outage times, affected devices and router or fibre-box indicators.
Prepare a concise record of tests, symptoms and service impact for the provider that needs to investigate.
I can troubleshoot customer equipment and help with the provider handover. Work on the fibre network itself remains with the responsible provider or network operator.
The scope and charging basis are agreed before work starts. If the likely next step needs replacement equipment or another provider, I will explain that so you can decide how to proceed.
Include your location, internet provider, router model if known and a short description of the dropouts or slow speeds. Please leave account passwords out of your message.
Tell me what you needPrefer email? john@johnfinnerty.co.nz
Test fibre problems one layer at a time. A slow laptop on Wi-Fi can look like a fibre problem, but the real issue might be wireless coverage, an overloaded router, a damaged Ethernet lead, a single device or a plan-speed mismatch. The first pass is to compare a wired test, a Wi-Fi test, the router status and the timing of the issue before making assumptions.
If wired tests are also unstable, the focus shifts to the ONT handoff, router WAN settings, service-provider status, physical cabling and whether the problem is constant or intermittent. That distinction matters because intermittent faults need timestamps and repeatable evidence, while constant faults can usually be narrowed down with a smaller set of checks.
A useful fibre fault note separates the local network from the provider path. Start with one known-good device, one known-good Ethernet cable and one test close to the router. Then compare that result with Wi-Fi in the normal work area. If Ethernet is stable and Wi-Fi is not, the next page to use is Wi-Fi support Christchurch. If Ethernet is unstable too, the focus shifts to the ONT, router WAN state, cabling, outage pattern, provider ticket and plan details.
Use a known-good laptop or desktop before assuming the fibre service is failing. One bad device can make the whole connection look broken.
Compare a wired test with Wi-Fi. Wired evidence is more useful for provider escalation because it removes coverage and roaming from the first pass.
Record router WAN status, uptime, firmware or config changes and ONT light state before power-cycling equipment.
Escalate with timestamps, wired results, outage duration, affected services and what changed after one controlled restart.
The ONT is the fibre handoff point. It is separate from the Wi-Fi router, even when they sit beside each other. A support note should say which ONT/router lights were visible, whether the router showed an active WAN connection, whether all devices were affected and whether the issue recovered without a restart.
Slow fibre can be an upstream service issue, but it can also be peak-time congestion, router limits, Wi-Fi performance, overloaded upload, a damaged cable or a plan that does not match the real device setup. For intermittent issues, repeated evidence is more useful than one perfect test.
Use the same device, same connection type and similar time windows when comparing results. Screenshots are better than memory.
Record whether the issue happens at the same time of day, during uploads, during video calls or when several people are online.
Commerce Commission RealSpeed reporting is a useful reminder that router-to-device Wi-Fi performance can be the bottleneck.
If the issue becomes a provider complaint, keep dates, screenshots, call notes, ticket numbers and the requested resolution.
A short evidence note can make provider support more productive. Keep it factual: date and time, affected devices, wired result, Wi-Fi result, ONT/router lights, service impact, restart result and the outcome you are asking for.
Official and primary references
These references support the same approach: test the local network first, capture useful evidence and escalate to the provider or dispute path with a dated record rather than a vague fault report.
Common questions
Quick answers to the things that usually slow troubleshooting down: how to isolate Wi-Fi from fibre, what evidence to capture and when reboots help or hurt.
If wired devices are fine but Wi-Fi is poor, it is usually coverage, interference or router placement. If wired tests fail too, the fault is more likely fibre, routing or upstream provider issues.
Timestamps, whether all devices were affected, whether wired tests failed too and any ONT/router light notes. A small set of comparable speed tests and a short summary of what was ruled out reduces back-and-forth.
One controlled reboot is useful. Repeated rebooting can remove evidence. Capture the failure times and symptoms first, then record what changes after a single restart.