AdvancedLow risk

Data connection slow, dropping, or unreliable

A data point links but is slow, drops out, or negotiates a low speed — pointing at cabling quality, a marginal termination, interference, or the run length, rather than a hard break.

Safety first

Extra-low-voltage. Keep data separated from mains to limit interference and for safety.

Isolate, lock out / tag out, and prove dead before working unless a live test is specifically required, authorised, and carried out under proper supervision. Always follow local regulations, your site procedures, and the equipment manufacturer's documentation.

Full detail — causes, the why, and common mistakes.

Likely causes

Ranked from most to least likely.

Premium fault tree

The full ranked causes, test sequence and flowchart for this fault are part of Sparkie Sidekick Pro.

Coming soon — no payment required during preview.

Testing sequence

Work through one test at a time. Expected reading and what each result means.

Full test sequence

The step-by-step test flow with expected readings for this fault is part of Sparkie Sidekick Pro.

Coming soon — no payment required during preview.

Fault-finding flowchart

The same logic as a decision tree.

  1. 1
    start

    Data slow/intermittent

    → step 2
  2. 2
    decision

    Does swapping the patch lead restore full speed?

    Yes→ step 3No→ step 4
  3. 3
    result

    It was the lead — done.

  4. 4
    decision

    Does the run test good with proper separation?

    Yes→ step 5No→ step 6
  5. 5
    result

    Run good — check switch-port speed/duplex config.

  6. 6
    result

    Marginal run / poor separation — rectify cabling/routing.

Common mistakes apprentices make

  • Only checking for a link, not the actual speed/errors.
  • Running data hard against mains and getting interference.
  • Ignoring a marginal termination that 'works'.
  • Overlooking a duplex/speed mismatch in config.

When to stop & escalate

Performance/certification and switch config sit between the cabling installer and the network team — share the test results so it's resolved at the right layer.

If you're past your competence, authorisation, or the safe limits of the job — stop and hand it on. There's no fault worth getting hurt over.

Related faults