Delay in Nomad session information

Incident Report for Velos IoT Service Update

Resolved

The issue is now resolved and the backlog of Nomad session information has now been completed.
If you are still experiencing problems related to this issue please raise to support@velosiot.com
Posted Mar 26, 2026 - 09:31 UTC

Update

Session information continues to populate in Nomad as the backlog of records is processed.

We will continue to monitor progress.

Next update: 26th March @ 10:00 UTC
Posted Mar 25, 2026 - 12:05 UTC

Update

Session information continues to populate in Nomad as the backlog of records is processed.

We will continue to monitor progress.

Next update: 25th March @ 10:00 UTC
Posted Mar 24, 2026 - 10:06 UTC

Update

Session information continues to populate in Nomad as the backlog of records is processed.

We will continue to monitor progress.

Next update: 24th March @ 10:00 UTC
Posted Mar 23, 2026 - 17:59 UTC

Monitoring

The issue has been identified and a fix has been applied.

We will continue to monitor to ensure that the session information is populated into Nomad through out the day.

Next update 18:00 UTC
Posted Mar 23, 2026 - 14:28 UTC

Update

The team are still investigating the issue regarding the delay in the session information in Nomad.

Next update will be 14:00 UTC
Posted Mar 23, 2026 - 12:10 UTC

Investigating

We are currently investigating a delay affecting how data session information is displayed in Nomad. At present, last activity is only being recorded up to 21st March.

As a result, users may see:

Devices with active sessions not showing the usual green status, and instead appearing as purple or orange
Delays in live session history, with recent sessions not yet visible
Delays in data usage reporting, with recent session activity not yet shown
CDR files appearing empty

Device connectivity itself is not affected. Registration and data sessions are continuing as normal. The issue is limited to the recording and display of session information within Nomad.
Posted Mar 23, 2026 - 09:40 UTC
This incident affected: SIM Management & Control (Nomad Self-Service Portal, Billing CDR, Nomad Backend).