How to Trace Telematics Outages in Your Fleet
Learn how to trace telematics outages across your fleet, isolate power, coverage, SIM and platform faults, then restore reporting with clear evidence.
A driver calls to say the vehicle has been working all morning, yet it has disappeared from the tracking map halfway through a delivery round. The device may still be fitted, the vehicle may still be moving, and nobody knows whether the problem is the tracker, its power supply, mobile coverage, the SIM or the tracking platform. This is exactly why knowing how to trace telematics outages matters: a vague ‘no signal’ report is rarely enough to fix the right problem.
For fleet managers, the aim is not to diagnose every technical detail at the roadside. It is to narrow the fault quickly, preserve useful evidence and give the installer, platform provider or connectivity team a clear place to start.
Start by defining the outage
An outage can mean several different things. A tracker may have stopped sending location data entirely. It may be reporting, but with a delay. It may show as offline in the platform while the vehicle is parked in a place with poor indoor coverage. Or the device may be connected but failing to send a particular item, such as driver behaviour, temperature or mileage data.
Begin with three facts: the last known report time, the vehicle’s location at that time, and whether the vehicle was moving, parked or switched off. Check whether the issue affects one vehicle, a group of vehicles, or the whole estate.
That distinction changes the likely cause. One vehicle dropping out is usually a local issue: device power, antenna, installation, vehicle environment or SIM status. A group of vehicles going quiet at the same time may point to a platform setting, a shared configuration change or a wider coverage issue in one area. If every tracker is offline, look first at the platform and account-level settings before sending anyone to inspect vehicles.
How to trace telematics outages step by step
Work from the simplest checks towards the more specific ones. Avoid rebooting the tracker or removing the SIM before you have recorded what the platform can tell you. A reset can bring a device back online, but it can also erase the clues needed to explain why it stopped reporting.
Check whether the vehicle and tracker have power
Many hard-wired telematics units are designed to sleep when the ignition is off, then wake at set intervals or when the vehicle moves. That can look like an outage if the reporting rules are not understood. Compare the vehicle’s expected behaviour with the device’s last report.

If the unit should be active, ask practical questions. Has the vehicle battery been changed or run flat? Has there been electrical work, a new dashcam installation or a repair near the tracker wiring? Has a fuse blown? If the device has an internal backup battery, has it reported low battery warnings before going offline?
A tracker that loses power at the same time as the ignition is switched off may be wired to the wrong feed. A device that stays offline after a normal journey may have a damaged connection, a fuse issue or a unit that needs inspection. Do not assume the SIM is at fault until the tracker has power and is expected to be awake.
Check the last connection and data use
Your SIM management platform should show whether the SIM has used data recently and, where available, when it last connected to a mobile service. This separates a connectivity question from a reporting question.
Recent data use suggests the SIM may still be communicating, even if the tracking platform is not displaying fresh positions. In that case, review the tracker’s server address, port and reporting configuration with the device supplier or installer. A configuration change, expired platform setting or server-side issue can stop location updates while the mobile connection remains active.
No recent usage does not automatically mean a dead SIM. The tracker may have no power, be out of coverage, be asleep or have a device fault. Still, it gives you a useful timestamp to compare with the last vehicle movement and the last platform update.
Check the SIM’s operational status too. Confirm it is active, assigned to the correct device and not subject to a data limit or account restriction. If the SIM was recently moved from another unit, make sure the tracker has been restarted only after you have checked its required access settings.
Look at the location, not just the signal reading
A low signal reading is useful, but it is not a complete explanation. Vehicles spend time in places that make mobile connections difficult: underground car parks, loading bays, depots with metal cladding, rural valleys, ferry crossings and workshops. A tracker can also lose a satellite position temporarily where its view of the sky is blocked.

Map the outage against the vehicle’s route. If reports stop repeatedly at the same depot and resume after the vehicle leaves, coverage or the local environment is the stronger lead. If several vehicles from different routes lose service in the same area, record the times and postcodes before raising the issue.
This is where a multi-network SIM can be helpful for fleets travelling across mixed coverage areas. It gives the device more than one available mobile service to use, subject to local conditions and device compatibility. It cannot compensate for a tracker with no power, a damaged antenna or a vehicle parked where no usable signal reaches it.
Separate GPS position from mobile connection
Telematics devices rely on two separate jobs. They need a satellite position to know where the vehicle is, and a mobile data connection to send that position to the platform. A fault in either one can make the vehicle appear to vanish.
If the platform shows a current connection but an old or invalid location, investigate the GPS side. Look for an antenna obstructed by metal, incorrect placement, a damaged cable or a unit fitted deep inside the vehicle where it cannot receive a reliable satellite signal. If the device has a valid position internally but cannot send it, focus on its data connection and settings instead.
This distinction is particularly useful when a tracker reports from some places but not others. It may be receiving a position throughout the journey and simply storing records until it can reconnect. When it does reconnect, a batch of delayed locations may appear. That is different from an outage where the tracker has not collected any usable positions at all.
Compare one affected vehicle with one working vehicle
A like-for-like comparison often saves time. Choose a vehicle with the same tracker model, similar SIM set-up and a similar route. Compare its last update time, signal history, power readings and data use against the affected unit.
If both devices were in the same area but only one stopped reporting, a local vehicle or installation fault becomes more likely. If both lost connection in the same place and recovered at the same time, retain that evidence for a coverage investigation. If only older tracker models are affected, check whether they share firmware, configuration or a legacy setting.
Check for changes made shortly before the outage
Outages often follow a change that was considered unrelated. A vehicle may have been serviced, a tracker moved, a SIM replaced, a new tracking rule applied or an account setting amended. Even a simple switch from daily driving to long periods parked on site can expose a sleep-mode setting that was never a problem before.
Ask what changed in the 48 hours before the first missed report. This is more productive than asking every team whether they have ‘seen an issue’. Look for a pattern in installer work, vehicle handovers, software changes and routes.
Preserve evidence before escalating
A good fault report should let another person continue the investigation without starting from scratch. Record the vehicle registration, tracker ID, SIM reference, the exact last-seen time, the location, the vehicle state and any warning messages. Add screenshots of the tracking platform and the SIM management view where possible.
Also record what happened next. Did the tracker return after the vehicle moved? Did it reconnect after a power cycle? Did delayed journeys appear later? These details reveal whether the device was offline, asleep, unable to find a position or storing data for later transmission.
Avoid repeated resets while testing. One controlled restart may be appropriate after checks have been recorded, but several resets can turn an intermittent fault into an untraceable one. If an installer needs to inspect the vehicle, ask them to photograph wiring, fuse connections and antenna placement before changing anything.
Turn recurring outages into a maintenance task
One unexplained gap can be frustrating. Repeated gaps should become a maintenance item. Review outage reports monthly by vehicle model, depot, route and tracker type. A pattern may show that certain units lose power after servicing, a particular parking area has poor indoor coverage, or a device setting needs changing across part of the fleet.
Set a practical alert threshold rather than treating every short delay as a failure. The right threshold depends on the vehicle’s job. A refrigerated delivery van may need closer monitoring than a vehicle parked for several days between jobs, and the threshold should sit comfortably above the tracker’s normal reporting interval. Clear expectations prevent unnecessary call-outs while making genuine reporting failures easier to spot.
Keep the device, SIM and vehicle records tied together. When a vehicle changes hands or a tracker is replaced, update the assignment at the same time. Poor asset records can look remarkably like an outage when the platform is simply showing the wrong device against the wrong registration.
Tracing telematics outages from evidence, not guesswork
For fleets that need clearer visibility of SIM status and usage alongside their connected devices, Wave Connect provides prepaid data SIMs and a central platform for managing SIM estates. Check the evidence first, then contact the relevant support team with the last-known time, location and device details. That gives everyone the best chance of finding the real fault rather than guessing at the signal.