INVERS Outage History

INVERS is up right now

There were 11 INVERS outages since February 10, 2026 totaling 32h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.invers.com

Minor April 14, 2026

FleetControl issues: Delayed event processing for some vehicles

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
  1. 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.

  2. 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 →

Major March 31, 2026

General issues

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
  1. 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.

  2. identified Mar 31, 2026, 08:22 AM UTC

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

  3. identified Mar 31, 2026, 08:26 AM UTC

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

  4. monitoring Mar 31, 2026, 08:27 AM UTC

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

  5. resolved Mar 31, 2026, 08:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 16, 2026

[ONLY BELGIUM] Connectivity issues with Proximus Belgium

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
  1. 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.

  2. 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.

  3. identified Mar 16, 2026, 01:42 PM UTC

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

  4. resolved Mar 16, 2026, 02:50 PM UTC

    Our devices connected to alternative networks.

Read the full incident report →

Notice March 10, 2026

Monitoring cellular connectivity issues on some CloudBoxx 4G devices

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
  1. 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.

  2. 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.

  3. 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.

  4. resolved Mar 10, 2026, 07:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 25, 2026

CloudBoxx 1020 connectivity service degradation

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
  1. 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.

  2. investigating Feb 25, 2026, 01:33 PM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 25, 2026, 03:40 PM UTC

    We are continuing to investigate this issue.

  4. 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.

  5. 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.

  6. monitoring Feb 25, 2026, 06:32 PM UTC

    All values returned to normal. We continue monitoring.

  7. 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 →

Minor February 25, 2026

Cellular connectivity issues in A1 networks (Austria, Slovenia, Croatia and North Macedonia)

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
  1. 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.

  2. monitoring Feb 25, 2026, 10:04 AM UTC

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

  3. 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 →

Notice February 25, 2026

Temporary problems in the network of vodafone.de (only Germany)

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
  1. 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.

  2. monitoring Feb 25, 2026, 01:05 AM UTC

    We are continuing to monitor for any further issues.

  3. 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 →

Minor February 12, 2026

Damage Detection Activation delayed

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
  1. 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.

  2. monitoring Feb 12, 2026, 04:47 PM UTC

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

  3. resolved Feb 12, 2026, 06:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 11, 2026

Monitoring issues with setting up vehicles with the smartcontrol app

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
  1. 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.

  2. 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.

  3. resolved Feb 11, 2026, 04:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 11, 2026

Cellular connectivity issues in the Netherlands

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
  1. investigating Feb 11, 2026, 02:53 PM UTC

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

  2. 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.

  3. 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.

  4. resolved Feb 11, 2026, 04:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 10, 2026

Problems with cellular provider KPN (Only relevant for devices in the Netherlands!)

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
  1. 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.

  2. resolved Feb 10, 2026, 08:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track INVERS downtime and outages?

Pingoru polls INVERS's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when INVERS reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track INVERS alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring INVERS for free

5 free monitors · No credit card required