Define the scope
Identify whether one device, Wi-Fi, a particular application or the entire site is affected.
SUPPORT
Better information. Faster diagnosis.
A structured incident report helps separate a device issue, local network problem, access failure or wider service interruption.
DIRECT ANSWER
Which information makes telecom diagnosis faster?
Provide the location, start time, affected users, what still works and recent changes. Compare Ethernet, Wi-Fi and mobile where possible. Avoid a factory reset because it can erase configuration and evidence needed for diagnosis.
- Best suited when
- Total outage, unstable Wi-Fi, unavailable application or reduced performance.
- Check first
- Status lights, cables, power, exact messages, timeline and incident scope.
- Useful decision
- Provide timestamped observations without passwords or temporary codes.
Explore our expertise
Start with safe, observable facts.
Record what changed and what still works before restarting equipment or changing configuration.
Explore our expertise
Key capabilities
Record the timeline
Note the start time, recurrence, error messages and any recent installation or change.
Check power and cables
Inspect status lights and connections without performing a factory reset.
Compare access methods
If available, compare wired, Wi-Fi and mobile access to isolate the affected layer.
Protect sensitive data
Never submit passwords, authentication codes, full card details or confidential documents.
Send useful context
Include location, service reference, affected users, symptoms and troubleshooting already performed.
Learn more
Do not erase the evidence.
A factory reset can remove configuration and make diagnosis harder. Prefer reversible checks and keep a short record of every action and result.
Learn more
A practical approach, from first question to everyday use.
Telecommunications can look complicated because several networks, devices and suppliers may be involved in a single connection. Our role is to put those elements in the right order. We start with the situation on the ground, explain the realistic options and identify the points that deserve a specific check. This gives individuals and organisations a clearer view before they decide.
A good solution is not necessarily the most elaborate one. It is the one that provides enough capacity, sensible resilience and manageable costs for the actual use. The recommendation therefore takes account of daily habits, busy periods, essential applications, future changes and the level of assistance expected after activation.
No coverage map or technical estimate can replace final eligibility and installation checks. For that reason, performance assumptions, local limitations and commercial conditions remain visible throughout the discussion. The aim is to create confidence through useful information, not through promises that cannot be supported.
- Observe before changingWe begin with the address, the building, the number of users and the applications that genuinely matter.
- Capture exact symptomsAvailable options are compared using the same criteria, including capacity, stability, delay, installation and total cost.
- Avoid destructive resetsThe preferred design is checked against security, continuity and support expectations before any commitment is made.
- Use the secure contact formScope, assumptions, responsibilities and next steps are written down so that activation can proceed on a clear basis.
PROCUREMENT AND ACCEPTANCE
What a study should let you verify
Request these details before ordering and keep the acceptance results. Applicable commitments remain those in the quote and contract.
| Area | Document | Validate |
|---|---|---|
| Incident record | Impact, time, devices and comparable measurements. | Reproducible symptom and documented scope. |
| Commitment | Hours, response/restoration terms and escalation. | Deadline understood and reporting available. |
| Closure | Correction, new measurements and business validation. | Complete user task confirmed. |
| Correlating logs | Time, time zone, clock offset and test identifier on each device. | Place events on one timeline; identical displayed times do not prove that devices are synchronised. |
A practical point to check
A green light or successful ping does not prove DNS, VPN or application recovery. Close the incident with a real user task.
Make an acceptance test reproducible
| Situation | Observation to keep | Interpretation |
|---|---|---|
| The connection responds but the application is slow | Compare a real task and round trips to the same destination. Separate DNS resolution, connection and transfer, keeping the context of each test. | A fast ping rules out neither slow DNS nor server processing. Closure should validate the action that was blocked. |
Read a series of latency measurements, beyond the average
Compare round trips to the same destination, at idle and during normal use. This tool summarises your observations; it performs no network measurement.
- Device
- Local network
- Provider access
- Destination
A round trip includes outward and return paths, which may differ. A single measurement cannot separate these stages.
Observation summary
Fictional example, unrelated to any provider or location.
| At idle (ms) | During use (ms, optional) | |
|---|---|---|
| Replies / probes | 5 / 6 | 5 / 6 |
| No reply | 16.67 % | 16.67 % |
| Median | 20.00 ms | 42.00 ms |
| 95th percentile (P95) | 22.00 ms | 95.00 ms |
| Maximum received | 22.00 ms | 95.00 ms |
Median difference (use − idle): 22.00 ms
Method and references
The median splits the sorted replies in two; for an even count it averages the two middle values. P95 uses the value at the rank rounded up from 0.95 × reply count. Probes without a reply are counted separately and never treated as zero milliseconds.
A small sample describes this test only. P95 is not a jitter measurement, and a timeout does not locate a fault. Keep destination, tool, protocol, duration and device comparable; also record Ethernet or Wi-Fi. A rise under load invites a review of queues without proving where the problem lies.
IETF · RFC 2681 · NIST · Percentiles · Arcep · Method and references
Learn more
Turning an incident into useful evidence
A good report helps distinguish an access failure, Wi-Fi issue, unavailable application or local incident without losing diagnostic evidence.
Wide or limited impact
State whether all users are affected, whether Ethernet works, whether mobile works and whether one application is involved. This comparison significantly reduces isolation time.
Before restarting
Photograph status lights, note the start time, error messages and recent changes. Avoid a factory reset because it can remove configuration required for analysis.
Collect useful observations
Provide the address, connection type, observed results and times. Do not send passwords, temporary codes, banking details or confidential documents.
Close the incident
After recovery, note what resolved the issue, its impact and possible preventive action. A short lessons-learned record can reduce the effect of the next interruption.
DECISION QUESTIONS
Essential answers before you choose
Short answers, including the limits to understand before ordering.
Should the router be restarted immediately?
First record status lights, time, messages and what still works. A simple restart may then help if authorised, but avoid a factory reset.
Why test Ethernet and Wi-Fi separately?
The comparison helps determine whether the issue is Internet access, wireless networking, a device or one application.
Which data should never be sent to support?
Never send passwords, one-time codes, full card numbers, private keys or confidential documents without an explicitly requested secure channel.
Contact us
Let us map the right connection for your location.
Tell us where, how many users and which critical applications you need to connect.