Услуга · Networks and telecom

Network infrastructure audit

People come for a review when the network behaves oddly and nobody can name the cause: the accounting database drags, connections drop, the wireless falls over. We measure and show exactly where the constriction is instead of swapping hardware at random.

Diagram
the real one, not from memory
Measurements
utilisation and errors
Weak nodes
we find
Report
with priorities

What the work includes

A review means measurements, not a look around. Every hypothesis is checked with instruments and the equipment's own statistics.

Discuss the scope

Diagram

The real picture of the connections rather than a five-year-old drawing from a folder.

Utilisation

How full the lines and ports are, where the peaks fall, what the error counters show.

Wireless

We walk the space with an instrument: where the signal is weak, where the channels overlap, which neighbour is interfering.

Segmentation

Whether the network is segmented or everything sits in one space where an infection spreads in minutes.

Single points of failure

The nodes whose failure stops the whole company or a significant part of it.

Report

The findings in order, each with an estimate of what fixing it costs.

How it goes

One site is reviewed in three to five days including measurements at peak times.

01

We gather

Device configurations, port statistics, what the administrators say and what the staff complain about.

02

We measure

Utilisation during working hours and a walk-round with signal measurements.

03

We compare

We overlay the complaints onto the measurements. The cause often turns out to be nowhere near where people look for it.

04

We write

The diagram, the findings and a prioritised plan of work.

Complaints about slow internet usually turn out not to be about the internet. Measurements pull out a mismatched port setting, or wireless points on overlapping channels, or a server bound by its disks. Switching provider in that situation changes nothing, though the company keeps paying the bill.

Questions and answers

It will not. Collecting configurations and statistics does not affect work, nor does walking the site measuring signal. Active scanning, if needed, is agreed separately and done outside working hours.

That happens too, and it is a valuable conclusion: the network is not at fault and the servers or the applications are what need attention. At the very least it stops the buying of new hardware in the hope that it will help.

As needed when problems appear, on a planned basis every two or three years, and always after major changes such as a relocation, growth in headcount or opening a new site. Network documentation goes out of date far faster than whoever wrote it imagines.

We will get to the bottom of your network

Tell us what is troubling you and how many sites you have. We will measure and show where the real cause lies.