What happens when a depot loses its internet connection?

Movements stop, unless the site was designed for it. A depot without connectivity cannot reach the operational system, cannot look up consignments and often cannot use its phones. Three things prevent that: a second connection path, tools that work offline, and a documented fallback for dispatching without systems.

This matters more in logistics than in most industries because of what an outage interrupts. In an office, an hour without systems delays work that can be caught up. At a depot, an hour without systems means vehicles waiting, drivers idle, windows missed and customers ringing. The freight does not pause politely, and the consequences compound through the day rather than resolving when the connection returns.

The first answer is a second path, and it has become inexpensive enough that the argument is largely settled. Mobile broadband failover on a router that switches automatically covers most outages, and the two requirements are that it switches without a human deciding and that it has been tested. Manual failover during a busy morning does not happen, and untested failover reveals a lapsed SIM or an expired data plan at exactly the wrong moment.

For operators where a site being isolated genuinely stops movements, SD-WAN goes further by using multiple links simultaneously rather than treating one as a spare, sending traffic down whichever path is healthy and prioritising what matters. Energy Logistix runs 24/7 across five sites at 99.99% AWS uptime with SD-WAN connecting them, which is what allows a continuous operation to treat a link failure as a non-event rather than an incident.

The second answer is offline capability in the tools people use, which is a procurement question rather than an infrastructure one. Systems that require a live connection to display a run sheet or record a delivery will stop dead; systems that hold the day's work locally and sync when they can will keep going. This should be tested before adoption rather than taken on trust, because plenty of platforms advertise mobile support and quietly need a signal for anything useful.

The third answer is the one that costs nothing and gets skipped: a documented fallback for operating without systems. Who has the day's movements available on paper or on a phone. Which numbers are called and by whom. How drivers are contacted if dispatch software is unavailable. How the records get reconciled once systems return. One page, written in advance, kept somewhere reachable when the network is down, and known to the people who would need it at four in the morning.

That plan needs to account for the phone system too, which is easily forgotten because it is invisible until it fails. Once telephony is hosted, an internet outage takes the phones with it, so the fallback must include how dispatch and drivers reach each other. Mobile applications on staff phones running over the cellular network are the practical answer, and they only work if they were installed and signed into before the outage rather than during it.

Power deserves a mention alongside connectivity, because in depots the two often fail together and the second is easier to overlook. Network equipment and phones draw power, so a blackout stops communications even where the connection itself is fine. A modest uninterruptible power supply on the network equipment buys enough time to move deliberately to mobile arrangements rather than discovering the problem when a driver cannot get through.

Test the arrangement rather than documenting it and hoping. Twice a year, at a quiet hour, disconnect the primary link at a site and watch what happens: does failover engage, do the phones survive, can dispatch continue, does anyone notice. That exercise reliably finds something, usually a device that was never moved onto the failover path or a person who did not know the plan existed.

The honest caveats. Some regional sites have genuinely limited options and the honest answer there is a better fallback plan rather than better connectivity. Redundancy reduces outages rather than eliminating them, since a carrier problem can affect multiple paths. And resilience is worth buying in proportion to what a site's downtime actually costs, which varies enormously between a major depot and a small branch. If you want that costed and designed, call 1800 456 567.