Lightfoot incident

Performance Degradation: Tracking Delays

Minor Resolved View vendor source →

Lightfoot experienced a minor incident on November 18, 2025 affecting Fleet Management Portal (my.lightfoot.co.uk) and Fleet Management API (data.lightfoot.co.uk) and 1 more component, lasting 5d 21h. The incident has been resolved; the full update timeline is below.

Started
Nov 18, 2025, 11:21 AM UTC
Resolved
Nov 24, 2025, 08:50 AM UTC
Duration
5d 21h
Detected by Pingoru
Nov 18, 2025, 11:21 AM UTC

Affected components

Fleet Management Portal (my.lightfoot.co.uk)Fleet Management API (data.lightfoot.co.uk)Driver Mobile App

Update timeline

  1. investigating Nov 18, 2025, 12:52 PM UTC

    We are currently experiencing a drop in traffic from in-cab Lightfoot devices to our servers. As a result, some vehicle tracking information may be temporarily unavailable via the Fleet Management portal and other interfaces. Lightfoot devices will retain their data and transmit this to our servers as soon as possible and no data will be lost.

  2. investigating Nov 18, 2025, 02:13 PM UTC

    We are experiencing a drop in device traffic due to network provider intermittency (EE). As a result, some vehicle tracking information may be showing a delay of up to 20 minutes via the Fleet Management portal and other interfaces. Lightfoot devices will retain their data and transmit this to our servers as soon as possible and no data will be lost.

  3. investigating Nov 20, 2025, 03:18 PM UTC

    We are investigating further network provider intermittency, which is resulting in an increase in "Signal Lost" vehicles on Tracking.

  4. identified Nov 20, 2025, 04:58 PM UTC

    One of our mobile network providers has an undiagnosed network connectivity issue. As a result, some Lightfoot devices are unable to send data to the Lightfoot servers. The result of this is that some vehicles may show as 'Signal Lost' or have delayed tracking data. Lightfoot devices will continue to work in-vehicle, will retain their data, and will transmit this to our servers once network connectivity is restored. We apologise for any inconvenience this may cause.

  5. identified Nov 21, 2025, 06:49 AM UTC

    The affected device population continues to experience degraded connectivity, unfortunately. We are working with the network provider to resolve this issue. Devices will continue to store data throughout this period. In-cab driver behaviour feedback is unaffected.

  6. identified Nov 21, 2025, 11:13 AM UTC

    We are continuing to work closely with our network provider to address the connectivity issue affecting some devices. The network provider's engineers are working on the problem with the highest priority.

  7. identified Nov 24, 2025, 08:47 AM UTC

    Our network service provider has identified the issue and implemented a successful fix, fully resolving the underlying fault. As devices reconnect, we are now receiving a high volume of previously delayed data. This is temporarily exceeding normal real-time processing levels, which may cause some disruption for customers as the backlog works its way through the system. While it’s too early to give a precise recovery time, we are not expecting full normal service today. However, we anticipate that the platform will stabilise overnight and into Saturday when traffic levels naturally reduce.

  8. monitoring Nov 24, 2025, 08:50 AM UTC

    The data backlog has cleared, leading to normal operation from all devices. This situation continues to be monitored.

  9. resolved Nov 24, 2025, 08:50 AM UTC

    This incident has been resolved.