- Detected by Pingoru
- May 28, 2026, 08:46 AM UTC
- Resolved
- May 28, 2026, 11:12 AM UTC
- Duration
- 2h 26m
Affected: CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
Timeline · 5 updates
-
investigating May 28, 2026, 08:46 AM UTC
We received reports of cellular connectivity issues. Our partner confirmed that there is an issue on some data sessions. The 24/7 teams of INVERS and the partner are working on it, we post new updates once available.
-
identified May 28, 2026, 08:53 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring May 28, 2026, 08:56 AM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring May 28, 2026, 09:16 AM UTC
The systems remain stable; if this continues, we will close the incident in about 30 minutes.
-
resolved May 28, 2026, 11:12 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 06:55 PM UTC
- Resolved
- May 20, 2026, 08:01 AM UTC
- Duration
- 13h 6m
Affected: CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 11:54 AM UTC
- Resolved
- May 12, 2026, 12:20 PM UTC
- Duration
- 26m
Affected: CloudBoxx REST API (Classic)OneAPI REST APISmartControl
Timeline · 3 updates
-
investigating May 12, 2026, 11:54 AM UTC
Setups are currently not being processed
-
monitoring May 12, 2026, 11:59 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 12, 2026, 12:20 PM UTC
This incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 02:53 PM UTC
- Resolved
- Apr 14, 2026, 03:24 PM UTC
- Duration
- 31m
Affected: FleetControl
Timeline · 2 updates
-
monitoring Apr 14, 2026, 02:53 PM UTC
We are experiencing an issue regarding event processing for FleetControl. For some vehicles the event log is not up-to-date and doesn't display the most recent events. We have identified the issue and implemented a fix. The event log is catching up.
-
resolved Apr 14, 2026, 03:24 PM UTC
Event processing is all caught up and the FleetControl event log displays the most recent events for all vehicles again.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 08:16 AM UTC
- Resolved
- Mar 31, 2026, 08:32 AM UTC
- Duration
- 15m
Affected: CloudBoxx REST API (Classic)LoginFleetControlOneAPI REST APIOneAPI Event ConsumersCloudBoxx Events, Trackings, Heartbeats (Classic)SmartControlDamage Detection Activation/DeactivationService PartnersAnomaly DetectionDriving Analysis
Timeline · 5 updates
-
investigating Mar 31, 2026, 08:16 AM UTC
We are currently experiencing issues with our services. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.
-
identified Mar 31, 2026, 08:22 AM UTC
RootCause has been identified. We are working on resolving the issue.
-
identified Mar 31, 2026, 08:26 AM UTC
We are continuing to work on a fix for this issue.
-
monitoring Mar 31, 2026, 08:27 AM UTC
Issue has been fixed. We are still monitoring the situation.
-
resolved Mar 31, 2026, 08:32 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2026, 12:10 PM UTC
- Resolved
- Mar 16, 2026, 02:50 PM UTC
- Duration
- 2h 40m
Affected: CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
Timeline · 4 updates
-
identified Mar 16, 2026, 12:10 PM UTC
We are currently experiencing issues with Proximus Belgium. CloudBoxxes should change network so impact should be minimal.
-
identified Mar 16, 2026, 12:10 PM UTC
We are currently experiencing issues with Proximus Belgium. CloudBoxxes should change network so impact should be minimal.
-
identified Mar 16, 2026, 01:42 PM UTC
Most CloudBoxxes switched network. We are working on a solution with our SIM provider.
-
resolved Mar 16, 2026, 02:50 PM UTC
Our devices connected to alternative networks.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 04:27 PM UTC
- Resolved
- Mar 10, 2026, 07:01 PM UTC
- Duration
- 2h 33m
Affected: CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
Timeline · 4 updates
-
investigating Mar 10, 2026, 04:27 PM UTC
We are seeing problems with some mobile connections in our graphs. This has been confirmed by the connectivity provider, who is working on a solution. We will post updates here when there is any news.
-
identified Mar 10, 2026, 05:27 PM UTC
According to feedback from our connectivity providers, the cellular connectivity issues are currently due to ongoing maintenance at a partner, which was initially announced without any expected impact. The pattern of restrictions we see in the log files matches the way maintenance is carried out. We will check how long this maintenance is planned to last and post an update here.
-
monitoring Mar 10, 2026, 05:49 PM UTC
There have been no further incidents for almost an hour. We are now setting the incident to “Monitoring” and will close it if it remains unchanged during the observation period.
-
resolved Mar 10, 2026, 07:01 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 10:30 AM UTC
- Resolved
- Feb 25, 2026, 07:00 PM UTC
- Duration
- 8h 29m
Affected: CloudBoxx 1020 (LTE-M / 2G)
Timeline · 7 updates
-
investigating Feb 25, 2026, 11:06 AM UTC
Our monitoring systems detected a service degradation of CloudBoxx 1020 connectivity. We are investigating with our partners.
-
investigating Feb 25, 2026, 01:33 PM UTC
We are continuing to investigate this issue.
-
investigating Feb 25, 2026, 03:40 PM UTC
We are continuing to investigate this issue.
-
identified Feb 25, 2026, 05:34 PM UTC
Our connectivity partner has identified a packet loss in the interconnection to our servers. They will switchover the traffic to another route which is part of our geo-redundant setup.
-
monitoring Feb 25, 2026, 06:20 PM UTC
The traffic switchover was successful and we are seeing huge improvements in our metrics. We continue monitoring for further issues.
-
monitoring Feb 25, 2026, 06:32 PM UTC
All values returned to normal. We continue monitoring.
-
resolved Feb 25, 2026, 07:00 PM UTC
No further issues occurred during the monitoring period. We consider this incident as resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 09:54 AM UTC
- Resolved
- Feb 25, 2026, 10:48 AM UTC
- Duration
- 53m
Affected: CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
Timeline · 3 updates
-
investigating Feb 25, 2026, 09:54 AM UTC
Our monitoring system detected cellular connectivity issues in several A1 networks in Austria, Slovenia, Croatia and North Macedonia. We are investigating with our partners.
-
monitoring Feb 25, 2026, 10:04 AM UTC
The metrics returned to normal value. We continue monitoring for further issues.
-
resolved Feb 25, 2026, 10:48 AM UTC
No further issues occurred during the monitoring period. We consider this incident as resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 12:15 AM UTC
- Resolved
- Feb 25, 2026, 06:49 AM UTC
- Duration
- 6h 34m
Affected: CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
Timeline · 3 updates
-
monitoring Feb 25, 2026, 01:04 AM UTC
There are temporary problems in the above-mentioned provider / country. The CloudBoxx units will log into other available networks. We are monitoring reliability with the specialist teams here and involving our connectivity partners. It only affects this provider in this country.
-
monitoring Feb 25, 2026, 01:05 AM UTC
We are continuing to monitor for any further issues.
-
resolved Feb 25, 2026, 06:49 AM UTC
No further issues occurred during the monitoring period. We consider this incident as resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 12, 2026, 01:45 PM UTC
- Resolved
- Feb 12, 2026, 06:53 PM UTC
- Duration
- 5h 8m
Affected: Damage Detection Activation/Deactivation
Timeline · 3 updates
-
identified Feb 12, 2026, 01:45 PM UTC
We are currently experiencing a delay for the activation process of Damage Detection. In rare cases these might even fail. We identified the issue and implemented a fix. Our team will process all remaining activations once this is solved.
-
monitoring Feb 12, 2026, 04:47 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 12, 2026, 06:53 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 04:03 PM UTC
- Resolved
- Feb 11, 2026, 04:33 PM UTC
- Duration
- 30m
Affected: SmartControlDamage Detection Activation/Deactivation
Timeline · 3 updates
-
identified Feb 11, 2026, 04:03 PM UTC
We are currently analyzing reported cases and investigating whether there is a general problem. We will post here when there are new findings.
-
monitoring Feb 11, 2026, 04:12 PM UTC
We can confirm a previous problem with adding vehicles to the fleet using the SmartControl app and with activating and deactivating damage detection modules. A fix has been implemented and we are continuing to monitor the situation.
-
resolved Feb 11, 2026, 04:33 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 02:53 PM UTC
- Resolved
- Feb 11, 2026, 04:39 PM UTC
- Duration
- 1h 45m
Affected: CloudBoxx 1020 (LTE-M / 2G)
Timeline · 4 updates
-
investigating Feb 11, 2026, 02:53 PM UTC
We currently experience cellular connectivity issues affecting CloudBoxx 1020 devices in the Netherlands. We are investigating.
-
identified Feb 11, 2026, 04:06 PM UTC
The data communication in NL KPN network is degraded. We are temporary blocking this network. The CloudBoxxes will switch to other available networks.
-
monitoring Feb 11, 2026, 04:25 PM UTC
Almost all devices switched to other networks and the performance is back to normal values. We continue monitoring.
-
resolved Feb 11, 2026, 04:39 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 10, 2026, 05:15 PM UTC
- Resolved
- Feb 10, 2026, 08:19 PM UTC
- Duration
- 3h 3m
Affected: CloudBoxx 1020 (LTE-M / 2G)
Timeline · 2 updates
-
investigating Feb 10, 2026, 05:15 PM UTC
There are problems in the Netherlands with the provider KPN. Devices are switching to other networks, which may cause brief interruptions. Our partners have been informed and are looking into this issue. We will close the incident here once everything is working again.
-
resolved Feb 10, 2026, 08:19 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 02, 2026, 01:07 PM UTC
- Resolved
- Feb 02, 2026, 02:27 PM UTC
- Duration
- 1h 19m
Affected: FleetControlOneAPI REST APIOneAPI Event ConsumersSmartControl
Timeline · 13 updates
Read the full incident report →
- Detected by Pingoru
- Dec 17, 2025, 09:25 AM UTC
- Resolved
- Dec 17, 2025, 10:23 AM UTC
- Duration
- 57m
Affected: CloudBoxx Events, Trackings, Heartbeats (Classic)
Timeline · 4 updates
-
investigating Dec 17, 2025, 09:25 AM UTC
We are currently experiencing issues with our CloudBoxx Events Message Queue. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.
-
identified Dec 17, 2025, 09:32 AM UTC
It only affects one message queue from one customer, who has been informed; other customers are not affected.
-
monitoring Dec 17, 2025, 09:37 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 17, 2025, 10:23 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 13, 2025, 11:44 AM UTC
- Resolved
- Dec 13, 2025, 05:07 PM UTC
- Duration
- 5h 22m
Affected: OneAPI Event Consumers
Timeline · 4 updates
-
investigating Dec 13, 2025, 11:44 AM UTC
We are currently experiencing issues with our OneAPI and Insights Events Message Queue. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.
-
identified Dec 13, 2025, 11:55 AM UTC
Speeding Events delivery is delayed due to slow response times from a third party API
-
monitoring Dec 13, 2025, 02:08 PM UTC
Speeding Event delay has recovered back to normal. We will continue monitoring for it to remain stable.
-
resolved Dec 13, 2025, 05:07 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 05, 2025, 09:06 AM UTC
- Resolved
- Dec 05, 2025, 09:12 AM UTC
- Duration
- 6m
Affected: Ticket system
Timeline · 3 updates
-
identified Dec 05, 2025, 09:06 AM UTC
There are currently delays in processing support tickets via the ticket system (support.invers.com). Our partner (ticket system provider) has been informed. Support via telephone or direct email is not affected.
-
monitoring Dec 05, 2025, 09:09 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 05, 2025, 09:12 AM UTC
This incident has been resolved.
Read the full incident report →
Critical December 1, 2025 - Detected by Pingoru
- Dec 01, 2025, 04:06 PM UTC
- Resolved
- Dec 01, 2025, 04:50 PM UTC
- Duration
- 44m
Affected: CloudBoxx REST API (Classic)CloudBoxx Events, Trackings, Heartbeats (Classic)
Timeline · 4 updates
-
investigating Dec 01, 2025, 04:06 PM UTC
We are currently experiencing issues with our CloudBoxx REST API and CloudBoxx Events (RabbitMQ). Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.
-
monitoring Dec 01, 2025, 04:19 PM UTC
Services have already recovered, we are investigating the incident cause.
-
resolved Dec 01, 2025, 04:50 PM UTC
This incident has been resolved.
-
Read the full incident report →
- Detected by Pingoru
- Nov 19, 2025, 05:17 PM UTC
- Resolved
- Nov 19, 2025, 08:28 PM UTC
- Duration
- 3h 11m
Affected: OneAPI Event Consumers
Timeline · 3 updates
-
investigating Nov 19, 2025, 05:17 PM UTC
We are currently experiencing degradation of Speeding Detection due to degradation of an external upstream service. We are closely monitoring the situation.
-
monitoring Nov 19, 2025, 05:23 PM UTC
We are closely monitoring the situation.
-
resolved Nov 19, 2025, 08:28 PM UTC
Systems remain stable, and our metrics are back to normal. We will close this incident.
Read the full incident report →
- Detected by Pingoru
- Nov 06, 2025, 10:30 AM UTC
- Resolved
- Nov 06, 2025, 11:30 AM UTC
- Duration
- 1h
Timeline · 1 update
-
resolved Nov 06, 2025, 03:40 PM UTC
Our infrastructure provider carried out maintenance work the previous night (European time). This required unscheduled follow-up work during the course of the day, which led to minor delays. For reasons of transparency, we are reporting this maintenance work.
Read the full incident report →
- Detected by Pingoru
- Nov 05, 2025, 06:00 PM UTC
- Resolved
- Nov 05, 2025, 06:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Nov 06, 2025, 03:32 PM UTC
Our infrastructure provider carried out maintenance during this period. The type of maintenance and the components affected did not suggest that it would affect us. For this reason, this maintenance was not announced. However, as it did lead to delays, we are reporting this maintenance for transparency purposes.
Read the full incident report →
- Detected by Pingoru
- Oct 29, 2025, 04:10 PM UTC
- Resolved
- Oct 29, 2025, 08:40 PM UTC
- Duration
- 4h 30m
Affected: FleetControlDamage Detection Activation/Deactivation
Timeline · 8 updates
-
investigating Oct 29, 2025, 04:10 PM UTC
We are currently experiencing issues with our FleetControl service. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.
-
identified Oct 29, 2025, 04:23 PM UTC
Important note: This only affects the FleetControl login page. You only need this if you want to log in again. FleetControl continues to function as normal. We are working with our partner on a solution. They have already confirmed the problem and that the cause lies with them.
-
identified Oct 29, 2025, 04:28 PM UTC
Additional information: The login page is currently slower and graphically reduced, but login is still possible, even for our customers with their login details.
-
identified Oct 29, 2025, 05:02 PM UTC
FleetControl login issue is ongoing. The underlying issue is ongoing, our partners are working on a fix. In addition the activation and deactivation process for damage detection is impacted as well.
-
identified Oct 29, 2025, 06:34 PM UTC
We implemented a fix of our own to supply the login form with assets. Login form is operational again.
-
identified Oct 29, 2025, 06:49 PM UTC
Correction regarding damage detection: Activation and deactivation were not impacted but one specific step for vehicle inspection during installation within SmartControl is still affected. As updated previously the FleetControl login page is operational.
-
monitoring Oct 29, 2025, 06:54 PM UTC
Damage Detection activation inspection process in SmartControl is reported to be operational again. Updating the incident to monitoring.
-
resolved Oct 29, 2025, 08:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 28, 2025, 04:58 PM UTC
- Resolved
- Oct 28, 2025, 06:56 PM UTC
- Duration
- 1h 58m
Affected: CloudBoxx 1020 (LTE-M / 2G)
Timeline · 3 updates
-
investigating Oct 28, 2025, 04:58 PM UTC
We are currently experiencing problems with the provider “Movistar” in Chile. Devices are switching to other wireless network providers, where available. The INVERS teams are in contact with their partners and will post updates here as soon as they are available.
-
monitoring Oct 28, 2025, 06:15 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 28, 2025, 06:56 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 10, 2025, 01:56 PM UTC
- Resolved
- Oct 10, 2025, 02:53 PM UTC
- Duration
- 57m
Affected: FleetControlOneAPI REST APISmartControl
Timeline · 7 updates
-
investigating Oct 10, 2025, 01:56 PM UTC
We are currently experiencing issues with our OneAPI REST API. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.
-
investigating Oct 10, 2025, 02:03 PM UTC
We are continuing to investigate this issue.
-
identified Oct 10, 2025, 02:12 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Oct 10, 2025, 02:17 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Oct 10, 2025, 02:44 PM UTC
A fix has been implemented and we're monitoring the results.
-
resolved Oct 10, 2025, 02:53 PM UTC
This incident has been resolved.
-
Read the full incident report →
