Fibre and internet troubleshooting

Find out why your business internet keeps letting you down

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 problem

Or call 021 125 1395.

Help with the connection and the provider conversation

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.

Slow speeds

Compare wired and Wi-Fi results, router behaviour and the connection setup before deciding the fibre service is at fault.

Intermittent dropouts

Look for patterns in outage times, affected devices and router or fibre-box indicators.

Provider escalation

Prepare a concise record of tests, symptoms and service impact for the provider that needs to investigate.

Relevant professional experience

A structured check, with useful notes at the end

  1. Capture the symptoms. Record when the fault happens, what stops working and whether wired devices fail as well as Wi-Fi.
  2. Agree and test. We agree the work and charging basis, then check local equipment and the available connection evidence.
  3. Resolve or escalate. I explain the findings and document changes. If the provider must act, you have a clearer fault report and next step.

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.

How the cost is agreed

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.

Start with the problem you need solved

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 need

Prefer email? john@johnfinnerty.co.nz

Technical notes

Fibre, router and provider-escalation checks

How fibre faults are separated from local network faults

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.

Before contacting the ISP

  • Record the time, duration, affected devices and whether wired and Wi-Fi devices behaved differently.
  • Capture the router and ONT light state before rebooting anything.
  • Run one comparable speed test on Ethernet where possible, then compare it with Wi-Fi from the normal work area.
  • Note recent changes such as a new router, moved ONT cable, power cut, firmware update or changed fibre plan.
  • Keep the summary short enough that support can see what has already been ruled out.

Fibre fault isolation order

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.

1. Device check

Use a known-good laptop or desktop before assuming the fibre service is failing. One bad device can make the whole connection look broken.

2. Wired check

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.

3. Router and ONT check

Record router WAN status, uptime, firmware or config changes and ONT light state before power-cycling equipment.

4. Provider escalation

Escalate with timestamps, wired results, outage duration, affected services and what changed after one controlled restart.

ONT and router evidence to capture

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.

  • Photograph or write down ONT and router lights before unplugging anything.
  • Check whether the router is connected to the expected ONT port and whether the Ethernet lead is seated properly.
  • Record whether phones, EFTPOS, VPN, cloud apps or video calls failed at the same time as general browsing.
  • Capture one controlled restart order if needed: ONT, router, switches/access points, then end devices.
  • Keep provider ticket numbers, promised callbacks and any replacement-router or line-test notes in one place.

Slow, patchy or intermittent fibre

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.

Comparable tests

Use the same device, same connection type and similar time windows when comparing results. Screenshots are better than memory.

Peak-time pattern

Record whether the issue happens at the same time of day, during uploads, during video calls or when several people are online.

Wi-Fi drop-off

Commerce Commission RealSpeed reporting is a useful reminder that router-to-device Wi-Fi performance can be the bottleneck.

Complaint evidence

If the issue becomes a provider complaint, keep dates, screenshots, call notes, ticket numbers and the requested resolution.

Escalation note template

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.

  • Issue: slow speeds / dropouts / no connection / voice failure / VPN failure.
  • Scope: one device, one room, all Wi-Fi, all wired, all services or only one provider/application.
  • Evidence: screenshots, timestamps, speed tests, ping/traceroute if available and ONT/router light notes.
  • Actions already taken: cable swap, wired test, one controlled restart, router check, provider outage check.
  • Requested outcome: line test, plan check, router replacement, technician visit, ticket escalation or written next step.

Official and primary references

NZ fibre and broadband references worth checking

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

Fibre troubleshooting FAQs

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.

Wi-Fi problem or fibre problem?

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.

What evidence is useful to an ISP?

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.

Should I keep rebooting the router and ONT?

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.

Related help