Trackunit Outage History

Trackunit is up right now

Pingoru has recorded 52 incidents for Trackunit: 41 in the last 12 months and 4 in the last 90 days.

Source: status.trackunit.com

52incidents recorded
41last 12 months
4last 90 days
5 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Trackunit in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202610 of 720 (0%)
May 202649 of 744 (1%)
June 202611 of 720 (0%)
July 2026228 of 744 (4%)
August 202600 of 744 (0%)
September 2026211 of 720 (2%)
October 202620 of 744 (0%)
November 202600 of 34 (0%)

Incidents, newest first

Notice October 30, 2026 Manager is experiencing problems 30m Trackunit Manager

Started Oct 30, 2026, 07:54 AM UTC· resolved Oct 30, 2026, 08:25 AM UTC

  1. investigating Oct 30, 2026, 07:54 AM UTC

    We are currently investigating this issue.

  2. resolved Oct 30, 2026, 08:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 22, 2026 Critical PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619) – Trackunit Manager, Trackunit Verify, Trackunit Raw, Manager Classic and 4 more

Started Oct 22, 2026, 07:19 AM UTC· resolved Oct 22, 2026, 07:19 AM UTC

  1. resolved Oct 22, 2026, 07:19 AM UTC

    On October 21, 2026, two critical vulnerabilities were publicly disclosed in the PHP programming language (CVE-2026-109618 and CVE-2026-109619). They can allow unauthenticated remote code execution in affected PHP environments. Our security team began assessing our exposure. We have taken the necessary actions. No action is required from our customers. We will continue to monitor the situation. If anything changes, we will update this page.

Read the full incident report →

Minor September 29, 2026 Data delays for Trackunit assets 2h 22m Trackunit Manager, Trackunit Go, Trackunit On, Trackunit API and 2 more

Started Sep 29, 2026, 11:21 PM UTC· resolved Sep 30, 2026, 01:44 AM UTC

  1. identified Sep 29, 2026, 11:21 PM UTC

    Due to an Trackunit infrastructure issue, some customers can experience data delays in Trackunit Manager, APIs, Go, and On.

  2. resolved Sep 30, 2026, 01:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 22, 2026 Data delay in Manager 8h 26m Manager Classic

Started Sep 22, 2026, 11:10 AM UTC· resolved Sep 22, 2026, 07:36 PM UTC

  1. investigating Sep 22, 2026, 11:10 AM UTC

    We are currently investigating this issue.

  2. identified Sep 22, 2026, 11:10 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Sep 22, 2026, 07:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 22, 2026 Data delays for Trackunit assets 1d Trackunit Manager, Trackunit Go, Trackunit On, Trackunit API and 2 more

Started Jul 22, 2026, 05:58 AM UTC· resolved Jul 23, 2026, 06:15 AM UTC

  1. investigating Jul 22, 2026, 05:58 AM UTC

    Due to an Trackunit infrastructure issue, some customers can experience data delays in Trackunit Manager, APIs, Go, and On. Delay is around 1 hour.

  2. investigating Jul 22, 2026, 07:08 AM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 22, 2026, 07:36 AM UTC

    We are continuing to investigate this issue. Delay is around 1 hour 10 minutes.

  4. identified Jul 22, 2026, 07:58 AM UTC

    The issue has been identified. Work is in progress to fix the issue.

  5. monitoring Jul 22, 2026, 09:26 AM UTC

    A fix has been implemented and we are monitoring the results. Delay is around 1 hour 30 minutes.

  6. monitoring Jul 22, 2026, 11:01 AM UTC

    We are continuing to monitor for any further issues.

  7. monitoring Jul 22, 2026, 11:08 AM UTC

    We are still seeing several hours of delays for updating telematics data in Manager, apps and APIs. Streaming APIs are almost up-to-date.

  8. monitoring Jul 22, 2026, 12:44 PM UTC

    We are below 30 minutes of delays in the pipelines. We hope to be fully up-to-date within 15 minutes.

  9. identified Jul 22, 2026, 01:38 PM UTC

    We have identified another issue in the pipeline and we are working on a fix.

  10. monitoring Jul 22, 2026, 02:42 PM UTC

    We are monitoring a fix and making small adjustments.

  11. monitoring Jul 22, 2026, 04:21 PM UTC

    We are continuing to monitor the situation.

  12. monitoring Jul 22, 2026, 06:51 PM UTC

    The updates are progressing. In 30 minutes, we should have new updates.

  13. monitoring Jul 22, 2026, 08:01 PM UTC

    We are seeing improvements, still monitoring the situation.

  14. monitoring Jul 22, 2026, 10:07 PM UTC

    The fixes previously implemented are working as expected. Since our systems are working through a large backlog of data we still see delays in data ingestion. We will monitor through the night and update the status page tomorrow morning CEST.

  15. monitoring Jul 23, 2026, 06:15 AM UTC

    The infrastructure issue has been resolved, and Trackunit services should now be operating normally.

  16. resolved Jul 23, 2026, 06:15 AM UTC

    This incident has been resolved.

  17. postmortem Jul 29, 2026, 08:43 AM UTC

    # Incident post mortem: Delayed Data Processing, 22–23 July 2026 **Status:** Resolved **Impact:** Delayed data updates. No data was lost. **Duration of impact:** Approx. 22 July 05:40 UTC to 23 July 06:15 UTC. Data delays varied throughout this period. They were not constant, and not all data was delayed at all times. ## What happened For roughly a day, data arriving from machines and connected devices took longer than normal to appear in the platform. The size of the delay varied over the period: at times data was close to up to date, while during the worst periods information that would usually be visible within minutes was delayed by up to about 1.5 hours. The platform itself stayed online and available throughout. The effect was that the data users were looking at was not as current as it should have been. We apologise for the disruption this caused. No data was lost. All information sent to us during the incident was stored safely and processed once capacity was restored. Once the backlog cleared, every affected data point was available in the platform, including for the period of the delay. ## Timeline of events \(UTC\) | Time | Event | | --- | --- | | 22 July, ~00:00 | Processing capacity begins to degrade. | | 22 July, 05:39 | Monitoring triggers an alert to our on-call engineer, who begins investigating. An incident is declared. | | 22 July, 06:00–07:30 | Investigation works through several possible causes and narrows the problem to a capacity limitation in the systems that move data through the platform. First corrective measures are applied. | | 22 July, 07:37 | Delays persist after the first corrective measures. The incident is escalated to our highest severity level. | | 22 July, 09:00–12:00 | Capacity of the affected systems is increased. Delays begin to reduce and backlogs start clearing. | | 22 July, 12:00–20:00 | Further capacity and configuration changes are rolled out in stages. Some of these surface secondary issues that are also resolved. | | 22 July, 22:14 | Systems confirmed stable and delays reducing steadily. The remaining backlog continues to clear. | | 23 July, 05:18 | All data flows confirmed fully caught up. Delays back to normal levels across the platform. | | 23 July, 06:16 | Incident resolved after a period of monitoring with no recurrence. | ## What we did to resolve it Monitoring triggered an alert to our on-call engineer, who began investigating and declared an incident. The initial symptoms pointed in several directions, and the first corrective measures did not resolve the problem. The incident was escalated to our highest severity level mid-morning to bring in additional teams. Once the capacity constraint was identified, we increased the capacity of the affected systems by upgrading the underlying infrastructure and expanding the number of systems processing data in parallel. These changes were rolled out in stages and verified as we went. Some of them surfaced secondary issues that were resolved before throughput fully recovered. The accumulated backlog was then cleared in a controlled sequence, with checks at each step that the data was complete and correct. Total time from alert to full resolution was approximately 24 hours, without data loss, and with a varying delay that generally decreased over that period as capacity was added and data queues were processed. ## Root cause The data-handling layer of our platform reached the performance limit of the infrastructure it was running on. Two factors combined created the root cause for this incident: * The storage and compute capacity supporting this layer had less performance headroom than the current load required. Due to a spike in load over time, It had not been upgraded in line with load growth. * At the same time, an internal process generated a much larger volume of data traffic than expected, which consumed a significant share of the remaining capacity. The traffic spike was the trigger; the limited headroom was the underlying cause. Once the system fell behind, it could not recover without additional capacity being added. ## What we are doing to prevent recurrence | Area | Action | | --- | --- | | **Capacity** | The infrastructure supporting this part of the platform has been upgraded to higher performance levels with meaningfully more headroom than current load requires. This was completed during the incident and is permanent. | | **Detection** | Our monitoring alerted us once data was already delayed. We are adding monitoring of capacity headroom so that a developing constraint is detected before it causes data delays. | | **Safeguards** | We are adding controls to limit how much shared processing capacity any single internal process can consume, so an unexpected spike in one place cannot degrade the wider platform. | | **Capacity planning** | We are reviewing headroom across the platform's other data-processing components and establishing a regular review so capacity keeps pace with load growth. | | **Response** | We are reviewing our diagnostic tooling and runbooks for this part of the platform to reduce the time needed to identify this class of problem. | All of the above are tracked internally with named owners and due dates.

Read the full incident report →

Critical July 21, 2026 Access management is not available in manager 3h 36m Trackunit Manager, Trackunit Go, Trackunit API

Started Jul 21, 2026, 02:49 PM UTC· resolved Jul 21, 2026, 06:25 PM UTC

  1. investigating Jul 21, 2026, 02:49 PM UTC

    We are currently investigating the issue

  2. investigating Jul 21, 2026, 02:50 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 21, 2026, 02:53 PM UTC

    We are continuing to investigate this issue.

  4. investigating Jul 21, 2026, 02:59 PM UTC

    We identified the issue. The fix is in progress

  5. identified Jul 21, 2026, 03:02 PM UTC

    The issue has been identified and a fix is being implemented.

  6. identified Jul 21, 2026, 05:03 PM UTC

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

  7. monitoring Jul 21, 2026, 06:24 PM UTC

    A fix has been implemented and we are monitoring the results.

  8. resolved Jul 21, 2026, 06:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 9, 2026 Asset meta data update delays 1h 25m Trackunit Manager, Trackunit Go, Trackunit On

Started Jun 09, 2026, 12:25 PM UTC· resolved Jun 09, 2026, 01:50 PM UTC

  1. investigating Jun 09, 2026, 12:25 PM UTC

    Some select Customers may be impacted by this issue if they create / edit / modify asset information in a Trackunit application while this incident is active. No data has been lost, but there may be delays in seeing the changes

  2. identified Jun 09, 2026, 12:30 PM UTC

    The issue have been identified and we are working on a fix.

  3. resolved Jun 09, 2026, 01:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 29, 2026 Asset meta data update delays 58m Trackunit Manager, Trackunit Go, Trackunit On

Started May 29, 2026, 01:14 PM UTC· resolved May 29, 2026, 02:13 PM UTC

  1. investigating May 29, 2026, 01:14 PM UTC

    Some select Customers may be impacted by this issue if they create / edit / modify asset information in a Trackunit application while this incident is active. No data has been lost, but there may be delays in seeing the changes

  2. identified May 29, 2026, 01:37 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved May 29, 2026, 02:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 27, 2026 Data delay in Manager 37m Trackunit Manager

Started May 27, 2026, 02:23 PM UTC· resolved May 27, 2026, 03:01 PM UTC

  1. investigating May 27, 2026, 02:23 PM UTC

    We are currently investigating this issue.

  2. identified May 27, 2026, 02:24 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 27, 2026, 02:54 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 27, 2026, 03:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 15, 2026 ONE i3 M-Series Data Delay 3h 17m Onei3

Started May 15, 2026, 02:48 PM UTC· resolved May 15, 2026, 06:06 PM UTC

  1. investigating May 15, 2026, 02:48 PM UTC

    Currently we are facing some delays in M-series data. Investigating about what is impacting the performance.

  2. investigating May 15, 2026, 04:25 PM UTC

    We are continuing to investigate this issue.

  3. investigating May 15, 2026, 04:26 PM UTC

    A fix has been applied and the systems are stabilizing.

  4. investigating May 15, 2026, 05:20 PM UTC

    Issue has been resolved and systems are working normal.

  5. resolved May 15, 2026, 06:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 12, 2026 ONE i3 M-Series Data Delay 4h 22m Onei3

Started May 12, 2026, 03:33 PM UTC· resolved May 12, 2026, 07:56 PM UTC

  1. investigating May 12, 2026, 03:33 PM UTC

    Currently we are facing some delays in M-series data. Investigating about what is impacting the performance.

  2. monitoring May 12, 2026, 06:54 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 12, 2026, 07:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 23, 2026 Degraded performance in Manager and Verify 13m Trackunit Manager, Trackunit Verify

Started Apr 23, 2026, 10:18 AM UTC· resolved Apr 23, 2026, 10:32 AM UTC

  1. investigating Apr 23, 2026, 10:18 AM UTC

    We are currently experiencing degraded performance in Manager and Verify. We are investigating and will provide an update as soon as more information becomes available.

  2. resolved Apr 23, 2026, 10:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 29, 2026 Data delay in Trackunit Manager Classic 6h 13m Manager Classic

Started Mar 29, 2026, 10:34 AM UTC· resolved Mar 29, 2026, 04:47 PM UTC

  1. investigating Mar 29, 2026, 10:34 AM UTC

    We are experiencing data delays in Classic due to a database infrastructure issue.

  2. identified Mar 29, 2026, 10:45 AM UTC

    We have identified the issue, we continue to monitor it.

  3. resolved Mar 29, 2026, 04:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 21, 2026 Data delays for Trackunit assets 2h 46m Trackunit Manager, Trackunit Go, Trackunit On, Trackunit API and 2 more

Started Mar 21, 2026, 03:45 AM UTC· resolved Mar 21, 2026, 06:31 AM UTC

  1. investigating Mar 21, 2026, 03:45 AM UTC

    We are currently experiencing delays in our data pipeline, some customers can experience delays in Trackunit Manager, APIs, Go, and On.

  2. identified Mar 21, 2026, 05:10 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Mar 21, 2026, 05:14 AM UTC

    A fix has been implemented. We are monitoring the situation. There is a delay in data being shown in Manager - no data has been lost or impacted besides in terms of delay

  4. resolved Mar 21, 2026, 06:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 18, 2026 Potential unstability experienced in Verify 34m Trackunit Verify

Started Mar 18, 2026, 01:11 PM UTC· resolved Mar 18, 2026, 01:46 PM UTC

  1. investigating Mar 18, 2026, 01:11 PM UTC

    We are currently investigating an issue impacting general performance of Verify

  2. monitoring Mar 18, 2026, 01:22 PM UTC

    We have identified and resolved the issue. We will continue to monitor the situation.

  3. monitoring Mar 18, 2026, 01:22 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Mar 18, 2026, 01:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 12, 2026 Advanced sensor data is not available in Manager UI 2h 43m Trackunit Manager

Started Mar 12, 2026, 04:38 PM UTC· resolved Mar 12, 2026, 07:21 PM UTC

  1. investigating Mar 12, 2026, 04:38 PM UTC

    We are currently investigating this issue.

  2. investigating Mar 12, 2026, 04:38 PM UTC

    We are continuing to investigate this issue.

  3. identified Mar 12, 2026, 04:52 PM UTC

    The issue has been identified and a fix is being implemented.

  4. resolved Mar 12, 2026, 07:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 5, 2026 Specifications can't be edited 23m Trackunit Manager, Trackunit Verify

Started Mar 05, 2026, 02:31 PM UTC· resolved Mar 05, 2026, 02:54 PM UTC

  1. investigating Mar 05, 2026, 02:31 PM UTC

    We are currently investigating the issue.

  2. resolved Mar 05, 2026, 02:54 PM UTC

    This incident has been resolved. Please logout and log back in again.

Read the full incident report →

Major March 2, 2026 We are experiencing data delays for Trackunit and onei3 assets 57m Trackunit Go, Trackunit API, Streaming API

Started Mar 02, 2026, 07:55 PM UTC· resolved Mar 02, 2026, 08:53 PM UTC

  1. investigating Mar 02, 2026, 07:55 PM UTC

    Due to an Trackunit infrastructure issue, some customers can experience data delays in Trackunit Manager, APIs, Go, and On.

  2. investigating Mar 02, 2026, 08:12 PM UTC

    The issue has been identified, and we are working on a fix.

  3. resolved Mar 02, 2026, 08:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 3, 2026 ONE i3 M-Series Data Delay 1h 3m Onei3

Started Feb 03, 2026, 07:38 PM UTC· resolved Feb 03, 2026, 08:42 PM UTC

  1. investigating Feb 03, 2026, 07:38 PM UTC

    Currently we are facing some delays in M-series data. Investigating about what is impacting the performance.

  2. monitoring Feb 03, 2026, 07:51 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 03, 2026, 08:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 30, 2026 Degraded Platform Performance 1h 55m Trackunit Manager, Trackunit Go, Trackunit On, Trackunit API

Started Jan 30, 2026, 12:41 PM UTC· resolved Jan 30, 2026, 02:36 PM UTC

  1. investigating Jan 30, 2026, 12:41 PM UTC

    We are currently experiencing degraded performance across parts of the Trackunit platform. This may affect Manager, Verify, and some API endpoints.

  2. monitoring Jan 30, 2026, 01:48 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 30, 2026, 02:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 29, 2026 Degraded Platform Performance 1h 31m Trackunit Manager, Trackunit Go, Trackunit API, Trackunit Verify

Started Jan 29, 2026, 12:37 PM UTC· resolved Jan 29, 2026, 02:08 PM UTC

  1. investigating Jan 29, 2026, 12:37 PM UTC

    We are currently experiencing degraded performance across parts of the Trackunit platform. This may affect Manager, Verify, and some API endpoints. Our team is actively investigating the issue. We will provide another update as soon as we have more information.

  2. monitoring Jan 29, 2026, 01:12 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 29, 2026, 02:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 27, 2026 Degraded Platform Performance 1h 8m Trackunit Manager, Trackunit Go, Trackunit On, Trackunit API

Started Jan 27, 2026, 02:18 PM UTC· resolved Jan 27, 2026, 03:26 PM UTC

  1. investigating Jan 27, 2026, 02:18 PM UTC

    We are currently experiencing degraded performance on the Trackunit platform.Some users may notice slower response times, primarily related to events and the attention list.Our team is investigating the issue and working to restore normal performance as quickly as possible.We will provide updates as more information becomes available.

  2. monitoring Jan 27, 2026, 02:48 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 27, 2026, 03:26 PM UTC

    System performance is back to normal.

Read the full incident report →

Minor January 26, 2026 Missing unit visibility in IRIS 8m Trackunit Manager, Trackunit Go, Trackunit On

Started Jan 26, 2026, 09:59 AM UTC· resolved Jan 26, 2026, 10:08 AM UTC

  1. identified Jan 26, 2026, 09:59 AM UTC

    We've identified the root cause and are working on implementing a fix

  2. identified Jan 26, 2026, 10:08 AM UTC

    Fix has been implemented and visibilities should be in order again.

  3. resolved Jan 26, 2026, 10:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 15, 2026 Issues loading asset detail page in manager 1h 40m Trackunit Manager

Started Jan 15, 2026, 10:56 AM UTC· resolved Jan 15, 2026, 12:37 PM UTC

  1. investigating Jan 15, 2026, 10:56 AM UTC

    We are currently experiencing an issue with loading certain pages in Trackunit manager, including asset details page.

  2. identified Jan 15, 2026, 11:09 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jan 15, 2026, 11:36 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jan 15, 2026, 12:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 14, 2026 Potential delays in Access Key generation in Manager 4h 43m Trackunit Manager, Trackunit API, Manager Classic

Started Jan 14, 2026, 09:51 AM UTC· resolved Jan 14, 2026, 02:35 PM UTC

  1. investigating Jan 14, 2026, 09:51 AM UTC

    We are currently investigating this issue.

  2. investigating Jan 14, 2026, 09:54 AM UTC

    We are continuing to investigate this issue.

  3. identified Jan 14, 2026, 09:55 AM UTC

    The issdue has been identified and a fix is being implemented. More information will follow .

  4. monitoring Jan 14, 2026, 09:56 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jan 14, 2026, 02:35 PM UTC

    This incident has been resolved.

Read the full incident report →