How to Track Down Packet Loss on a South African Connection

Packet loss is easier to prove with a timeline than a single red icon in one match. To track packet loss in South Africa, test the local router, ISP path and game destination separately while recording when the drops begin.

Quick Answer

Track packet loss from near to far. Start with a continuous, rate-limited ping to your router, then test the ISP path and an approved stable external destination. Use Ethernet first. Loss to the router points inside the home. A clean router test with loss to later destinations points towards access or ISP routing. Intermediate traceroute hops can ignore probes, so only treat loss as transit trouble when it continues to later hops and the destination.

Capture the game symptom

Record the game, server region, time and network warning. Rubber-banding, disconnects and delayed actions can come from loss, but frame stutter can look similar.

Turn on the game's packet-loss display when available. Note whether loss appears during a household upload or at a fixed evening hour.

Check the publisher service status before testing the home for a widespread outage.

Test the first hop

Plug the test machine into a LAN port on the primary router with a known-good cable. Find the router's local address through the supported network status page.

Run a continuous ping at the operating system's normal rate for a controlled period. Stop it and save sent, received and lost counts. Do not use flood options.

Any repeatable loss to the router on Ethernet deserves a cable, port, network-adaptor or router check. Try another known cable and LAN port, then another device.

Compare Wi-Fi with Ethernet

Repeat from the normal wireless position. Loss that appears only on Wi-Fi points to interference, weak signal, driver trouble or access-point load.

Move beside the router and test the supported 5GHz or 6GHz band. If the result improves, placement or coverage is the lead.

Keep smart-home 2.4GHz traffic and gaming tests separate. A mesh system should be tested at the main router and satellite to expose backhaul loss.

Move beyond the router

Ping an ISP gateway or approved provider target when the ISP exposes one. Then test a reputable stable external hostname and the game publisher's diagnostic endpoint when available.

Loss to one public host can belong to that host's reply policy. Compare two relevant destinations. Real transit loss tends to affect later traffic, not one silent device.

Save the date and exact target. Do not post public addresses or account details in an open forum.

Run a longer peak-hour sample

An hour-long normal-rate test can capture intermittent evening loss, but it should be purposeful. Run one quiet-hour and one peak-hour sample to the same approved target.

Keep household traffic normal for the first run, then label any large upload that occurs. Run a second controlled test with the house quiet.

The comparison separates access or provider timing from a family backup job. It also gives the ISP a repeatable window.

Read traceroute loss correctly

Routers can deprioritise diagnostic responses. A hop showing loss while every later hop responds cleanly did not drop the forwarded packets in the way the table suggests.

Look for loss that begins at one hop and continues to the destination. Pair it with game loss at the same time.

Pathping on Windows can collect hop statistics, though it still relies on diagnostic handling. Use it as evidence, never as a verdict on one intermediate router.

Check the physical access link

On fibre, inspect user-accessible cable seating and the network terminal indicators without bending or unplugging optical fibre. Report warning lights to the ISP.

On LTE or 5G, record signal quality and tower-time patterns through the supported interface. On fixed wireless, ask the provider to check alignment and radio errors.

Avoid factory resets until configuration and credentials are backed up. A reset rarely repairs an external line fault and can remove useful logs.

Prepare an ISP case

Include source city, access type, Ethernet confirmation, test targets, times, sent packets, loss percentage and game symptom. Attach a good and bad comparison.

State where loss first persists to the destination. Ask the ISP to check the access link and route during that window.

Keep the case reference and add later samples to it. Several disconnected tickets make the pattern harder to see.

Know when router replacement fits

Replace hardware when first-hop Ethernet loss follows the router across cables and devices, firmware is unsupported or another known router removes the fault.

Do not replace a clean router for loss that begins outside the home. Compare current routers and networking equipment only when the local evidence supports it. Source a known-good lead or desk connector from popular accessories after checking the required length and sockets.

FAQ

How long should you ping for evidence?

Start with a short controlled test, then use a labelled peak-hour sample when the problem is intermittent. Normal rate is enough.

Does one traceroute hop with loss prove the fault?

No. The loss must continue through later hops and the destination to suggest transit loss.

When is the router the likely cause?

Repeatable Ethernet loss to the first hop across cables and devices is strong local evidence.