Infrastructure
Network Optimisation & Troubleshooting
The intermittent problem nobody has been able to pin down: the connection that drops at the same time each day, the floor that is slow only in the afternoon, the call quality that fails on one side of the office. We measure rather than replace — traceroutes, packet loss, error counters, wireless surveys, duplex and cabling faults — and we tell you which of the things you were about to buy would not have helped.
- Scopes it runs at
- 3
- Steps in a job
- 4
- Deliverables
- 5
- Estimate
- $0
Scope
What this looks like at your scale
Intermittent network problems are expensive because they get guessed at. New access points get bought for a problem that was a duplex mismatch; the circuit gets upgraded for congestion that was a failing patch lead; someone replaces a switch because it is the newest thing they can think of. Each guess costs money and none of them is a diagnosis, and the problem is still there afterwards — now with less budget to fix it.
- 01
One reported fault
A specific problem with a specific symptom. Measured, identified, and either fixed on the visit or quoted properly.
- 02
A floor that is generally slow
Where nobody can say what is wrong, only that it is worse than it was. This wants measurement across the day rather than a single test.
- 03
A full assessment
Switching, cabling, wireless and the path out to the internet, with a written finding and a prioritised list of what to do about it.
How it runs
In the order the work happens
The sequence matters more than the list. Most of what goes wrong on these jobs traces back to a step skipped early rather than to the work itself.
- 01
Get the symptom described precisely
When it happens, who it happens to, what it looks like from their side, and what changed before it started. Half of these are solved here, because the pattern in the description is the diagnosis.
- 02
Measure, at the layer the symptom points at
Loss and latency along the path, interface error and discard counters on the switch, cable certification where the physical layer is suspect, spectrum and channel usage where wireless is. Counters that have been incrementing for a year are the most underused evidence in this work.
- 03
Separate what is real from what is cosmetic
A router that does not answer a traceroute is not a fault; a hop that loses packets which every hop after it also loses is. Telling those apart is most of what makes a report worth reading, and it is why so much money gets spent on the wrong leg.
- 04
Fix it, or state plainly what would
Where the fix is a cable, a port configuration or a channel plan, it happens on the visit. Where it is a circuit or a hardware replacement, you get the evidence for that rather than an opinion — including when the honest answer is that the problem is your provider's.
What you get
What is actually delivered
- Measured evidence rather than a replacement recommendation
- Interface error and discard counters read and interpreted
- Cable certification where the physical layer is implicated
- Wireless channel and interference survey where relevant
- A written finding with a prioritised list of what to change
Not this
What we do not do here
Stating this is what makes the rest of the page worth believing, and it saves you a call that was never going to end in work.
- Application performance inside software we did not build. We can prove the network is or is not the cause, which is usually the argument that needs settling.
- Carrier-side faults beyond the demarcation point, though the evidence we produce is what gets a carrier to act.
- Ongoing monitoring and alerting as a managed service.
Questions
Before you call
- It only happens sometimes. Can you still find it?
- That is the normal case, and it is why measurement beats guesswork. Intermittent faults leave traces — error counters, retransmissions, a pattern in the time of day — and those are still there when the symptom is not.
- Will you just tell us to buy new equipment?
- Only if that is genuinely the answer, and we will show you the evidence. A good share of these turn out to be a bad patch lead, a duplex mismatch, or a wireless channel plan that has more access points fighting each other than it needs.
- Can we do some of this ourselves first?
- Yes, and we publish the tools free with no sign-up — a traceroute reader, a switch config auditor, and the guides behind them. If they solve it, you have not needed us, and that is a fine outcome.
Related
Usually bought alongside
- Infrastructure
Network & Telecom Infrastructure
Switching, structured cabling, and closets that a stranger can read at a glance.
- Infrastructure
Disaster Recovery & Business Continuity
Get trading again first, then get everything back — and know which is which beforehand.
Next step
Need Network Optimisation & Troubleshooting?
Free diagnostics and a written estimate before anyone is dispatched. Tell us the site and the deadline and we will tell you what it takes.
- Free diagnostics
- Same-day across most of the metro
- Named technicians
- No fix, no labour charge