Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Störungsverlauf von Invers

    54 Invers incidents · Juni 2025 — official updates, affected components, duration and resolution details.

    Zurück zum aktuellen Status

    Allgemeine Probleme (Erhöhte Anforderungsfehlerrate)

    Beginn 2. September 2026 um 11:22 UTC · 1h 11m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    OneAPI REST APICloudBoxx Events, Trackings, Heartbeats (Classic)LoginCloudBoxx REST API (Classic)FleetControlService PartnersDriving AnalysisSmartControlDamage Detection Activation/DeactivationOneAPI Event ConsumersAnomaly Detection
    1. 2. September 2026 um 11:22 UTCinvestigating

      Wir haben derzeit Probleme mit unseren Dienstleistungen. Unser Incident Response Team untersucht. Wir werden so schnell wie möglich ein Update mit Details und Umfang des Vorfalls veröffentlichen.

    2. 2. September 2026 um 11:27 UTCinvestigating

      Einige Dienste erwarten eine höhere Ausfallrate als üblich (20%), was bedeutet, dass ~80% der Anfragen nicht betroffen sind. Retries können temporäre Probleme lösen. Dies wirkt sich auch auf die Ereignisübertragung aus, die zu einer geringfügigen Verzögerung von Ereignissen führen kann.

    3. 2. September 2026 um 11:34 UTCinvestigating

      Wir werden dieses Problem weiter untersuchen.

    4. 2. September 2026 um 11:55 UTCinvestigating

      Unsere Partner konnten die Fehlerquelle ermitteln, und sowohl sie als auch INVERS arbeiten mit allen verfügbaren Teams zusammen, um das Problem zu lösen.

    5. 2. September 2026 um 12:13 UTCinvestigating

      Die Ursache wurde auf ein Verbindungsproblem bei unserem Hosting-Provider zurückgeführt. Ihr Engineering-Team hat den betroffenen Bereich identifiziert und arbeitet aktiv daran, die volle Funktionalität wiederherzustellen. Die INVERS-Teams bleiben in enger Abstimmung mit ihnen, um den Fix zu beschleunigen. Wie bereits erwähnt, sind die Auswirkungen begrenzt - etwa 80% der Anfragen werden weiterhin normal verarbeitet, und Retries beheben die meisten temporären Fehler. Verzögerte Ereignisübertragung bleibt der Hauptsekundäreffekt.

    6. 2. September 2026 um 12:14 UTCidentified

      Das Problem wurde identifiziert und ein Fix wird implementiert.

    7. 2. September 2026 um 12:16 UTCmonitoring

      Fehlerrate und Ereignisübertragung haben sich erholt.

    8. 2. September 2026 um 12:17 UTCmonitoring

      Wir werden weiterhin auf weitere Probleme achten.

    9. 2. September 2026 um 12:33 UTCresolved

      Der Vorfall wurde behoben. Die Fehlerrate und Ereignisübertragung ist wieder normal und stabil.

    10. 16. September 2026 um 07:51 UTCpostmortem

      Der Vorfallsbericht \(post mortem\) ist abrufbar unter [https://help.invers.com/incident-reports/](https://help.invers.com/incident-reports/).

    Automatisch aus der offiziellen Störungsmeldung übersetzt.

    API-Probleme erkannt

    Beginn 27. August 2026 um 07:21 UTC · 5h 15m

    Pending
    Betroffene Komponenten
    OneAPI REST APICloudBoxx REST API (Classic)CloudBoxx 4G (LTE / 2G)CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 3G (3G / 2G)
    1. 27. August 2026 um 07:21 UTCmonitoring

      Unsere Überwachung erkannte Probleme von 06: 58-07: 08 UTC. Die Situation hat sich erholt und die Untersuchung läuft noch.

    2. 27. August 2026 um 07:49 UTCmonitoring

      Wir werden weiterhin auf weitere Probleme achten.

    3. 27. August 2026 um 12:36 UTCresolved

      Dieser Vorfall wurde behoben. Ein detaillierter Post-Incident-Bericht wird in Kürze folgen.

    4. 31. August 2026 um 09:02 UTCpostmortem

      Der Vorfallsbericht \(post mortem\) ist bei unserem Support-Team unter [[email protected]](mailto:[email protected]) verfügbar.

    Automatisch aus der offiziellen Störungsmeldung übersetzt.

    OneAPI und Insights Events (RabbitMQ) Probleme

    Beginn 23. Juli 2026 um 01:02 UTC · 19m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    Driving AnalysisOneAPI Event ConsumersAnomaly Detection
    1. 23. Juli 2026 um 01:02 UTCidentified

      Wir haben derzeit Probleme mit unserer OneAPI und Insights Events Message Queue. Unser Incident Response Team untersucht. Wir werden so schnell wie möglich ein Update mit Details und Umfang des Vorfalls veröffentlichen.

    2. 23. Juli 2026 um 01:15 UTCmonitoring

      Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

    3. 23. Juli 2026 um 01:21 UTCresolved

      Dieser Vorfall wurde behoben.

    Automatisch aus der offiziellen Störungsmeldung übersetzt.

    Allgemeine Fragen

    Beginn 16. Juli 2026 um 16:55 UTC · 2h 2m

    Pending
    Betroffene Komponenten
    OneAPI REST APICloudBoxx Events, Trackings, Heartbeats (Classic)LoginCloudBoxx REST API (Classic)FleetControlService PartnersDriving AnalysisSmartControlDamage Detection Activation/DeactivationOneAPI Event ConsumersAnomaly Detection
    1. 16. Juli 2026 um 16:55 UTCidentified

      Wir haben derzeit Probleme mit unseren Dienstleistungen. Unser Notfall-Standby-Personal untersucht. Wir werden so schnell wie möglich ein Update mit Details und Umfang des Vorfalls veröffentlichen.

    2. 16. Juli 2026 um 17:10 UTCmonitoring

      Kommunikationsprobleme zwischen unseren Rechenzentren wurden behoben, alles ist wieder normal. Wir beobachten die Situation weiter.

    3. 16. Juli 2026 um 18:57 UTCresolved

      Dieser Vorfall wurde behoben.

    Automatisch aus der offiziellen Störungsmeldung übersetzt.

    Monitoring cellular connectivity issues with provider Orange in France only

    Beginn 29. Juni 2026 um 07:55 UTC · 3h 21m

    Pending
    Betroffene Komponenten
    CloudBoxx 4G (LTE / 2G)
    1. 29. Juni 2026 um 07:55 UTCinvestigating

      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.

    2. 29. Juni 2026 um 08:22 UTCinvestigating

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

    3. 29. Juni 2026 um 09:12 UTCidentified

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

    4. 29. Juni 2026 um 09:38 UTCmonitoring

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

    5. 29. Juni 2026 um 09:47 UTCmonitoring

      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.

    6. 29. Juni 2026 um 11:15 UTCresolved

      This incident has been resolved.

    Service Restrictions with the Mobile Carrier “Orange” in France

    Beginn 18. Juni 2026 um 07:13 UTC · 7h 40m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
    1. 18. Juni 2026 um 07:13 UTCinvestigating

      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.

    2. 18. Juni 2026 um 08:43 UTCinvestigating

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

    3. 18. Juni 2026 um 10:56 UTCinvestigating

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

    4. 18. Juni 2026 um 12:47 UTCidentified

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

    5. 18. Juni 2026 um 13:52 UTCmonitoring

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

    6. 18. Juni 2026 um 13:55 UTCmonitoring

      We are continuing to monitor for any further issues.

    7. 18. Juni 2026 um 14:53 UTCresolved

      This incident has been resolved.

    Monitoring cellular connectivity issues

    Beginn 28. Mai 2026 um 08:46 UTC · 2h 26m

    Pending
    Betroffene Komponenten
    CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
    1. 28. Mai 2026 um 08:46 UTCinvestigating

      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.

    2. 28. Mai 2026 um 08:53 UTCidentified

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

    3. 28. Mai 2026 um 08:56 UTCmonitoring

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

    4. 28. Mai 2026 um 09:16 UTCmonitoring

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

    5. 28. Mai 2026 um 11:12 UTCresolved

      This incident has been resolved.

    Cellular connectivity issues

    Beginn 19. Mai 2026 um 18:55 UTC · 13h 7m

    OutageSchwerwiegender Vorfall
    Betroffene Komponenten
    CloudBoxx 4G (LTE / 2G)CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 3G (3G / 2G)
    1. 19. Mai 2026 um 18:55 UTCinvestigating

      We currently experience cellular connectivity issues. We are investigating.

    2. 19. Mai 2026 um 19:06 UTCinvestigating

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

    3. 19. Mai 2026 um 19:25 UTCinvestigating

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

    4. 19. Mai 2026 um 20:22 UTCidentified

      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.

    5. 19. Mai 2026 um 20:52 UTCidentified

      The situation regarding the remaining units continues to stabilize.

    6. 19. Mai 2026 um 21:37 UTCidentified

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

    7. 19. Mai 2026 um 22:03 UTCmonitoring

      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.

    8. 19. Mai 2026 um 22:05 UTCmonitoring

      We are continuing to monitor for any further issues.

    9. 20. Mai 2026 um 08:01 UTCresolved

      This incident has been resolved.

    10. 26. Mai 2026 um 07:38 UTCpostmortem

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

    Adding vehicles and setup problems

    Beginn 12. Mai 2026 um 11:54 UTC · 26m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    OneAPI REST APICloudBoxx REST API (Classic)SmartControl
    1. 12. Mai 2026 um 11:54 UTCinvestigating

      Setups are currently not being processed

    2. 12. Mai 2026 um 11:59 UTCmonitoring

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

    3. 12. Mai 2026 um 12:20 UTCresolved

      This incident has been resolved

    FleetControl issues: Delayed event processing for some vehicles

    Beginn 14. April 2026 um 14:53 UTC · 31m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    FleetControl
    1. 14. April 2026 um 14:53 UTCmonitoring

      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. 14. April 2026 um 15:24 UTCresolved

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

    General issues

    Beginn 31. März 2026 um 08:16 UTC · 16m

    OutageSchwerwiegender Vorfall
    Betroffene Komponenten
    OneAPI REST APICloudBoxx Events, Trackings, Heartbeats (Classic)LoginCloudBoxx REST API (Classic)FleetControlService PartnersDriving AnalysisSmartControlDamage Detection Activation/DeactivationOneAPI Event ConsumersAnomaly Detection
    1. 31. März 2026 um 08:16 UTCinvestigating

      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. 31. März 2026 um 08:22 UTCidentified

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

    3. 31. März 2026 um 08:26 UTCidentified

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

    4. 31. März 2026 um 08:27 UTCmonitoring

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

    5. 31. März 2026 um 08:32 UTCresolved

      This incident has been resolved.

    [ONLY BELGIUM] Connectivity issues with Proximus Belgium

    Beginn 16. März 2026 um 12:10 UTC · 2h 41m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    CloudBoxx 4G (LTE / 2G)CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 3G (3G / 2G)
    1. 16. März 2026 um 12:10 UTCidentified

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

    2. 16. März 2026 um 13:42 UTCidentified

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

    3. 16. März 2026 um 14:50 UTCresolved

      Our devices connected to alternative networks.

    Monitoring cellular connectivity issues on some CloudBoxx 4G devices

    Beginn 10. März 2026 um 16:27 UTC · 2h 34m

    Pending
    Betroffene Komponenten
    CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
    1. 10. März 2026 um 16:27 UTCinvestigating

      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. 10. März 2026 um 17:27 UTCidentified

      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. 10. März 2026 um 17:49 UTCmonitoring

      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. 10. März 2026 um 19:01 UTCresolved

      This incident has been resolved.

    CloudBoxx 1020 connectivity service degradation

    Beginn 25. Februar 2026 um 10:30 UTC · 8h 29m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    CloudBoxx 1020 (LTE-M / 2G)
    1. 25. Februar 2026 um 11:06 UTCinvestigating

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

    2. 25. Februar 2026 um 15:40 UTCinvestigating

      We are continuing to investigate this issue.

    3. 25. Februar 2026 um 17:34 UTCidentified

      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.

    4. 25. Februar 2026 um 18:20 UTCmonitoring

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

    5. 25. Februar 2026 um 18:32 UTCmonitoring

      All values returned to normal. We continue monitoring.

    6. 25. Februar 2026 um 19:00 UTCresolved

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

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

    Beginn 25. Februar 2026 um 09:54 UTC · 53m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
    1. 25. Februar 2026 um 09:54 UTCinvestigating

      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. 25. Februar 2026 um 10:04 UTCmonitoring

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

    3. 25. Februar 2026 um 10:48 UTCresolved

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

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

    Beginn 25. Februar 2026 um 00:15 UTC · 6h 34m

    Pending
    Betroffene Komponenten
    CloudBoxx 4G (LTE / 2G)CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 3G (3G / 2G)
    1. 25. Februar 2026 um 01:04 UTCmonitoring

      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. 25. Februar 2026 um 01:05 UTCmonitoring

      We are continuing to monitor for any further issues.

    3. 25. Februar 2026 um 06:49 UTCresolved

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

    General issues

    Beginn 13. Februar 2026 um 10:12 UTC · 1h 12m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    OneAPI REST APICloudBoxx Events, Trackings, Heartbeats (Classic)CloudBoxx REST API (Classic)FleetControlService PartnersSmartControlOneAPI Event Consumers
    1. 13. Februar 2026 um 10:12 UTCinvestigating

      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. 13. Februar 2026 um 10:15 UTCidentified

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

    3. 13. Februar 2026 um 10:24 UTCidentified

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

    4. 13. Februar 2026 um 10:35 UTCmonitoring

      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.

    5. 13. Februar 2026 um 10:58 UTCmonitoring

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

    6. 13. Februar 2026 um 11:24 UTCresolved

      This incident has been resolved.

    7. 25. Februar 2026 um 09:38 UTCpostmortem

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

    Damage Detection Activation delayed

    Beginn 12. Februar 2026 um 13:45 UTC · 5h 8m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    Damage Detection Activation/Deactivation
    1. 12. Februar 2026 um 13:45 UTCidentified

      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. 12. Februar 2026 um 16:47 UTCmonitoring

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

    3. 12. Februar 2026 um 18:53 UTCresolved

      This incident has been resolved.

    Monitoring issues with setting up vehicles with the smartcontrol app

    Beginn 11. Februar 2026 um 16:03 UTC · 31m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    SmartControlDamage Detection Activation/Deactivation
    1. 11. Februar 2026 um 16:03 UTCidentified

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

    2. 11. Februar 2026 um 16:12 UTCmonitoring

      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. 11. Februar 2026 um 16:33 UTCresolved

      This incident has been resolved.

    Cellular connectivity issues in the Netherlands

    Beginn 11. Februar 2026 um 14:53 UTC · 1h 45m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    CloudBoxx 1020 (LTE-M / 2G)
    1. 11. Februar 2026 um 14:53 UTCinvestigating

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

    2. 11. Februar 2026 um 16:06 UTCidentified

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

    3. 11. Februar 2026 um 16:25 UTCmonitoring

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

    4. 11. Februar 2026 um 16:39 UTCresolved

      This incident has been resolved.