Invers outage history

We are currently experiencing issues with our services. Our incident response team is investigating. We’ll post an update with details and scope of the incident as soon as possible.

Some services are expecting a higher failure rate than usual (20%), meaning ~80% of requests are unaffected. Retries can resolve temporary issues. This also affects event transmission which can lead to events being slightly delayed.

We are continuing to investigate this issue.

Our partners were able to determine the source of the error, and both they and INVERS are working with all available teams to resolve the issue.

The root cause has been traced to a connectivity issue at our hosting provider. Their engineering team has identified the affected area and is actively working to restore full functionality. INVERS teams remain in close coordination with them to accelerate the fix. As previously noted, the impact is limited — roughly 80% of requests continue to process normally, and retries resolve most temporary failures. Delayed event transmission remains the main secondary effect.

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

Failure rate and event transmission has recovered.

We are continuing to monitor for any further issues.

The incident has been resolved. Failure rate and event transmission is back to normal and stable.

The incident report \(post mortem\) is available from [https://help.invers.com/incident-reports/](https://help.invers.com/incident-reports/).

Our monitoring detected issues from 06:58–07:08 UTC. The situation has recovered and the investigation is ongoing.

We are continuing to monitor for any further issues.

This incident has been resolved. A detailed post-incident report will follow shortly.

The incident report \(post mortem\) is available from our support team at [[email protected]](mailto:[email protected]).

We are currently experiencing issues with our OneAPI and Insights Events Message Queue. Our incident response team is investigating. We’ll post an update with details and scope of the incident as soon as possible.

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

This incident has been resolved.

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.

Communication issues between our Datacenters have been resolved everything is back to normal. We keep monitoring the situation.

This incident has been resolved.

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.

The mobile carrier Orange is working on a solution, and the relevant teams remain involved.

The values are back to near-standard performance. This issue affected, and continues to affect, only older CloudBoxx 4G devices in France.

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

The issue with Orange in France has been resolved; we are keeping the status at "monitoring" for now and will continue to monitor whether the service remains stable. Most devices were not noticeably affected because they switched to alternative mobile networks in France.

This incident has been resolved.

The relevant internal INVERS teams and those of the connectivity provider are already looking into the issue and are working together to find a solution. This affects only 3G and 4G devices in France.

Our Carrier Partner is actively investigating the issue. We are closely coordinating with them and continuously monitoring the situation.

Our Carrier Partner continues to actively investigate the issue. We are closely coordinating with them and monitoring the situation.

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

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

We are continuing to monitor for any further issues.

This incident has been resolved.

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.

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

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

The systems remain stable; if this continues, we will close the incident in about 30 minutes.

This incident has been resolved.

We currently experience cellular connectivity issues. We are investigating.

We currently experience cellular connectivity issues with one of our providers. All CloudBoxxes connected via this provider are affected.

We are seeing improvements regarding the communication success rate. We will keep monitoring the connectivity metrics.

Due to scheduled maintenance at a connectivity provider, all devices connected to that provider have been switched over to the alternative connectivity provider. There were brief interruptions during the switchover process. The situation has since stabilized, and the emergency teams and the connectivity team are working on the remaining unstable units.

The situation regarding the remaining units continues to stabilize.

It's taking longer for the remaining units to reconnect, but our teams are still on top of the situation

The metrics are almost back to normal levels. The teams will continue to monitor the metrics and mark this incident as resolved if it remains stable over the next few hours.

We are continuing to monitor for any further issues.

This incident has been resolved.

The incident report \(post mortem\) is available from our support team at [[email protected]](mailto:[email protected]).

Setups are currently not being processed

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

This incident has been resolved

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.

Event processing is all caught up and the FleetControl event log displays the most recent events for all vehicles again.

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.

RootCause has been identified. We are working on resolving the issue.

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

Issue has been fixed. We are still monitoring the situation.

This incident has been resolved.

We are currently experiencing issues with Proximus Belgium. CloudBoxxes should change network so impact should be minimal.

Most CloudBoxxes switched network. We are working on a solution with our SIM provider.

Our devices connected to alternative networks.

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.

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.

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.

This incident has been resolved.

Our monitoring systems detected a service degradation of CloudBoxx 1020 connectivity. We are investigating with our partners.

We are continuing to investigate this issue.

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.

The traffic switchover was successful and we are seeing huge improvements in our metrics. We continue monitoring for further issues.

All values returned to normal. We continue monitoring.

No further issues occurred during the monitoring period. We consider this incident as resolved.

Our monitoring system detected cellular connectivity issues in several A1 networks in Austria, Slovenia, Croatia and North Macedonia. We are investigating with our partners.

The metrics returned to normal value. We continue monitoring for further issues.

No further issues occurred during the monitoring period. We consider this incident as resolved.

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.

We are continuing to monitor for any further issues.

No further issues occurred during the monitoring period. We consider this incident as resolved.

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.

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

Some systems are back up and running, we're staying on top of it.

The relevant part of the systems is still available, data processing is running, and we are in direct contact with all relevant teams and service providers.

Systems remain stable; if this continues, we will close this incident.

This incident has been resolved.

The incident report \(post mortem\) is available from our support team at [[email protected]](mailto:[email protected]).

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.

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

This incident has been resolved.

We are currently analyzing reported cases and investigating whether there is a general problem. We will post here when there are new findings.

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.

This incident has been resolved.

We currently experience cellular connectivity issues affecting CloudBoxx 1020 devices in the Netherlands. We are investigating.

The data communication in NL KPN network is degraded. We are temporary blocking this network. The CloudBoxxes will switch to other available networks.

Almost all devices switched to other networks and the performance is back to normal values. We continue monitoring.

This incident has been resolved.