Time: July 31, 2024, 5:09 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: July 31, 2024, 4:35 p.m.

Status: Monitoring

Update: A fix is in place and data is flowing again. It may take a couple of hours for the queued data to be processed.

Time: July 31, 2024, 4:19 p.m.

Status: Investigating

Update: The Global Stream connection from ONE i3 to Iris is currently down. M-series data is not updating in Iris / Manager. We have identified the problem and are working to resolve it as soon as possible.

Time: July 31, 2024, 6:17 a.m.

Status: Resolved

Update: We've seen our data pipeline catch up to real time. We do await any sleeping devices to check in to get all their queued data, but this will complete within the hour.

Time: July 31, 2024, 5:38 a.m.

Status: Identified

Update: AWS has restored service and we are observing traffic resuming. We are now monitoring the catching up of data queued during the outage. As such, we expect data to continue to be delayed with a gradual catchup to real time. We expect this to take a few hours. An update will be provided in 60min or earlier.

Time: July 31, 2024, 2:11 a.m.

Status: Identified

Update: AWS is still working on restoring services in us-east-1.

Time: July 30, 2024, 11:53 p.m.

Status: Identified

Update: Multiple AWS Service Outages

Time: July 30, 2024, 11:10 p.m.

Status: Investigating

Update: We are currently seeing multiple Onei3 services being impacted due to an ongoing outage reported by AWS.

Time: July 29, 2024, 2:42 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: July 29, 2024, 2:35 p.m.

Status: Identified

Update: We are continuing to work on a fix for this issue.

Time: July 29, 2024, 2:34 p.m.

Status: Identified

Update: We see delays in processing of data for Skyjack assets. The delay is currently around 30 minutes.

Time: July 19, 2024, 7:18 p.m.

Status: Resolved

Update: We have fully recovered all systems. A full root cause analysis will be performed off the incident both in conjunction with our 3rd party provider, as well as internal to Trackunit to determine any necessary actions to reduce impact in the future.

Time: July 19, 2024, 5:39 p.m.

Status: Monitoring

Update: All Trackunit systems have been recovered. There is a small queue left in IRIS that we are currently parsing through and estimate to be completely caught up in 1 hour and 30 minutes. We will close this incident once we are fully recovered and all systems are operational.

Time: July 19, 2024, 3:30 p.m.

Status: Identified

Update: Currently all platforms are online and receiving telematics data. Some features in Trackunit manager (IRIS) might not be functioning correctly, or with a delay which we are working to resolve.

Time: July 19, 2024, 1:45 p.m.

Status: Identified

Update: We continue to work to recover all systems to operational state. Application status: Currently trackunit IRIS and Trackunit mobile apps such as Go and ON are operational but some features and actions within the application is being delayed. This means that for example user activations and others is queued in the system, but are not being completed right now. Trackunit Classic is operational. Trackunit Onei3 is operational. Telematics data: OneI3 (m7) telematics data are currently being processed, delays can occour, we do not expect there to be telematics data lost. Trackunit IRIS devices (TUXXX) data are being processed, delays can occour, and we do not expect telematics data to be lost. Trackunit Classic devices telematics data are being processed, but we are investigating a potential data loss lasting roughly 2 hours between 06.00 - 08.00 CET. We will update this statuspage once new information arises.

Time: July 19, 2024, 11:05 a.m.

Status: Identified

Update: We continue to work to recover all systems to operational state. Application status: Currently trackunit IRIS and Trackunit mobile apps such as Go and ON are operational but some actions within the application is being delayed. This means that for example user activations and others is queued in the system, but are not being completed right now. Classic is operational. Onei3 is operational. Telematics data: OneI3 (m7) telematics data are currently being processed, delays can occour, we do not expect there to be telematics data lost. Trackunit IRIS devices (TUXXX) data are being processed, delays can occour, and we do not expect telematics data to be lost. Trackunit Classic devices telematics data are being processed, but we have encourred roughly 2 hours of data lost between 06.00 - 08.00 CET.

Time: July 19, 2024, 9:50 a.m.

Status: Identified

Update: SCOM view has recovered. We are continuing to work on recovering systems.

Time: July 19, 2024, 9:24 a.m.

Status: Identified

Update: We are still working to recover the platforms impacted. Currently we estimate that this work will continue until 13.00 CET. Once this is done, platforms will be available, but minor issues such as smaller data delays or issues with changing user accounts (creation, deletion or updating might still be present)

Time: July 19, 2024, 8:21 a.m.

Status: Identified

Update: Our phone provider has recovered and support should be reachable via phone again. Current status: We are working to recover the remaining platforms, and estimate to have recovered most functionality within 2 hours. Once this is done there will be a back log of data that has to be parsed, which can take up to 6 hours.

Time: July 19, 2024, 8:09 a.m.

Status: Identified

Update: Some customers are reporting issues contacting our support via phone. We are aware of this issue, which is caused by the phone provider also having an outage. Current status: We are working to recover the remaining platforms, and estimate to have recovered most functionality within 2 hours. Once this is done there will be a back log of data that has to be parsed, which can take up to 6 hours.

Time: July 19, 2024, 8:06 a.m.

Status: Identified

Update: Some customers are reporting issues contacting our support via phone. We are aware of this issue, which is caused by the phone provider also having an outage. Current status: We are working to recover the remaining platforms, and estimate to have recovered most functionality within 2 hours. Once this is done there will be a back log of data that has to be parsed, which can take up to 6 hours.

Time: July 19, 2024, 7:18 a.m.

Status: Identified

Update: Access control has recovered

Time: July 19, 2024, 7:04 a.m.

Status: Identified

Update: We have identified the cause, and are currently working to restore functionality across all platforms. Some features currently works but there can be general unstability in the systems. We are aware that this is also impacting access control and are currently working to restore functionality.

Time: July 19, 2024, 5:49 a.m.

Status: Identified

Update: We have identifed the issue, and are currently working to restore availability to the platform. Currently we are having impact on multiple products, such as Onei3, Trackunit Manager, Trackunit mobile apps and classic. We do currently not have an estimated time for when we are back online. We will update this page again 09.00 CET or when new information arises.

Time: July 19, 2024, 4:56 a.m.

Status: Investigating

Update: Due to an infrastructure issue, some users can experience problems with access to our systems. Classic access control might also be affected and delays may occur

Time: July 10, 2024, 8:16 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: July 10, 2024, 8:16 p.m.

Status: Monitoring

Update: This incident has been resolved.

Time: July 10, 2024, 5:13 p.m.

Status: Monitoring

Update: During a release of one of our services we experienced issues causing M series alerts to be delayed (shortly after 12pm EST). Delays of up to 50m were observed. We've resolved the issue and are seeing alerts gradually catch back up. We will update once all alerts are back up to current.