Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Invers driftsforstyrrelser

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

    Tilbage til aktuel status

    Generelle spørgsmål (Øget fejlprocent for anmodninger)

    Startede 2. september 2026 kl. 11.22 UTC · 1h 11m

    IssuesMindre hændelse
    Berørte komponenter
    OneAPI REST APICloudBoxx Events, Trackings, Heartbeats (Classic)LoginCloudBoxx REST API (Classic)FleetControlService PartnersDriving AnalysisSmartControlDamage Detection Activation/DeactivationOneAPI Event ConsumersAnomaly Detection
    1. 2. september 2026 kl. 11.22 UTCinvestigating

      Vi oplever i øjeblikket problemer med vores tjenester. Vores indsatshold undersøger det. Vi sender en opdatering med detaljer og omfang af hændelsen så hurtigt som muligt.

    2. 2. september 2026 kl. 11.27 UTCinvestigating

      Nogle tjenester forventer en højere fejlprocent end normalt (20%), hvilket betyder ~ 80% af anmodningerne er upåvirket. Genforsøg kan løse midlertidige problemer. Dette påvirker også begivenhedstransmission, som kan føre til en let forsinkelse.

    3. 2. september 2026 kl. 11.34 UTCinvestigating

      Vi fortsætter med at undersøge dette spørgsmål.

    4. 2. september 2026 kl. 11.55 UTCinvestigating

      Vores partnere var i stand til at bestemme kilden til fejlen, og både de og INVERS arbejder med alle tilgængelige hold for at løse problemet.

    5. 2. september 2026 kl. 12.13 UTCinvestigating

      Root årsagen er blevet sporet til en forbindelse problem på vores hosting udbyder. Deres ingeniørhold har identificeret det berørte område og arbejder aktivt på at genoprette fuld funktionalitet. INVERS hold forbliver i tæt koordinering med dem for at fremskynde fix. Som tidligere nævnt er virkningen begrænset - omkring 80% af anmodningerne fortsætter med at behandle normalt, og forsøger at løse de fleste midlertidige fejl. Forsinket begivenhedstransmission er fortsat den vigtigste sekundære effekt.

    6. 2. september 2026 kl. 12.14 UTCidentified

      Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

    7. 2. september 2026 kl. 12.16 UTCmonitoring

      Fejlprocent og begivenhed transmission er kommet sig.

    8. 2. september 2026 kl. 12.17 UTCmonitoring

      Vi fortsætter med at overvåge for yderligere spørgsmål.

    9. 2. september 2026 kl. 12.33 UTCresolved

      Hændelsen er løst. Fejlhastighed og begivenhedstransmission er tilbage til normal og stabil.

    10. 16. september 2026 kl. 07.51 UTCpostmortem

      Hændelsesrapporten\ (post mortem\) er tilgængelig fra [https: / / help.invers.com / incident- reports /] (https: / / help.invers.com / incident- reports /).

    Automatisk oversat fra den officielle hændelsesopdatering.

    API-problemer opdaget

    Startede 27. august 2026 kl. 07.21 UTC · 5h 15m

    Pending
    Berørte komponenter
    OneAPI REST APICloudBoxx REST API (Classic)CloudBoxx 4G (LTE / 2G)CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 3G (3G / 2G)
    1. 27. august 2026 kl. 07.21 UTCmonitoring

      Vores overvågning opdagede problemer fra 06: 58- 07: 08 UTC. Situationen er blevet bedre, og undersøgelsen er i gang.

    2. 27. august 2026 kl. 07.49 UTCmonitoring

      Vi fortsætter med at overvåge for yderligere spørgsmål.

    3. 27. august 2026 kl. 12.36 UTCresolved

      Denne hændelse er blevet løst. Der vil snart blive udarbejdet en detaljeret rapport efter hændelsen.

    4. 31. august 2026 kl. 09.02 UTCpostmortem

      Hændelsesrapporten\ (post mortem\) er tilgængelig fra vores support team på [support @ invers.com] (mailto: support @ invers.com).

    Automatisk oversat fra den officielle hændelsesopdatering.

    OneAPI og Insights Events (RabbitMQ) spørgsmål

    Startede 23. juli 2026 kl. 01.02 UTC · 19m

    IssuesMindre hændelse
    Berørte komponenter
    Driving AnalysisOneAPI Event ConsumersAnomaly Detection
    1. 23. juli 2026 kl. 01.02 UTCidentified

      Vi oplever i øjeblikket problemer med vores OneAPI og Insights Events Message Queue. Vores indsatshold undersøger det. Vi sender en opdatering med detaljer og omfang af hændelsen så hurtigt som muligt.

    2. 23. juli 2026 kl. 01.15 UTCmonitoring

      Et fix er blevet gennemført, og vi overvåger resultaterne.

    3. 23. juli 2026 kl. 01.21 UTCresolved

      Denne hændelse er blevet løst.

    Automatisk oversat fra den officielle hændelsesopdatering.

    Generelle spørgsmål

    Startede 16. juli 2026 kl. 16.55 UTC · 2h 2m

    Pending
    Berørte komponenter
    OneAPI REST APICloudBoxx Events, Trackings, Heartbeats (Classic)LoginCloudBoxx REST API (Classic)FleetControlService PartnersDriving AnalysisSmartControlDamage Detection Activation/DeactivationOneAPI Event ConsumersAnomaly Detection
    1. 16. juli 2026 kl. 16.55 UTCidentified

      Vi oplever i øjeblikket problemer med vores tjenester. Vores team efterforsker det. Vi sender en opdatering med detaljer og omfang af hændelsen så hurtigt som muligt.

    2. 16. juli 2026 kl. 17.10 UTCmonitoring

      Kommunikationsproblemer mellem vores datacenter er blevet løst alt er tilbage til normal. Vi holder øje med situationen.

    3. 16. juli 2026 kl. 18.57 UTCresolved

      Denne hændelse er blevet løst.

    Automatisk oversat fra den officielle hændelsesopdatering.

    Monitoring cellular connectivity issues with provider Orange in France only

    Startede 29. juni 2026 kl. 07.55 UTC · 3h 21m

    Pending
    Berørte komponenter
    CloudBoxx 4G (LTE / 2G)
    1. 29. juni 2026 kl. 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 kl. 08.22 UTCinvestigating

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

    3. 29. juni 2026 kl. 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 kl. 09.38 UTCmonitoring

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

    5. 29. juni 2026 kl. 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 kl. 11.15 UTCresolved

      This incident has been resolved.

    Service Restrictions with the Mobile Carrier “Orange” in France

    Startede 18. juni 2026 kl. 07.13 UTC · 7h 40m

    IssuesMindre hændelse
    Berørte komponenter
    CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
    1. 18. juni 2026 kl. 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 kl. 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 kl. 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 kl. 12.47 UTCidentified

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

    5. 18. juni 2026 kl. 13.52 UTCmonitoring

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

    6. 18. juni 2026 kl. 13.55 UTCmonitoring

      We are continuing to monitor for any further issues.

    7. 18. juni 2026 kl. 14.53 UTCresolved

      This incident has been resolved.

    Monitoring cellular connectivity issues

    Startede 28. maj 2026 kl. 08.46 UTC · 2h 26m

    Pending
    Berørte komponenter
    CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
    1. 28. maj 2026 kl. 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. maj 2026 kl. 08.53 UTCidentified

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

    3. 28. maj 2026 kl. 08.56 UTCmonitoring

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

    4. 28. maj 2026 kl. 09.16 UTCmonitoring

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

    5. 28. maj 2026 kl. 11.12 UTCresolved

      This incident has been resolved.

    Cellular connectivity issues

    Startede 19. maj 2026 kl. 18.55 UTC · 13h 7m

    OutageStørre hændelse
    Berørte komponenter
    CloudBoxx 4G (LTE / 2G)CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 3G (3G / 2G)
    1. 19. maj 2026 kl. 18.55 UTCinvestigating

      We currently experience cellular connectivity issues. We are investigating.

    2. 19. maj 2026 kl. 19.06 UTCinvestigating

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

    3. 19. maj 2026 kl. 19.25 UTCinvestigating

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

    4. 19. maj 2026 kl. 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. maj 2026 kl. 20.52 UTCidentified

      The situation regarding the remaining units continues to stabilize.

    6. 19. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 22.05 UTCmonitoring

      We are continuing to monitor for any further issues.

    9. 20. maj 2026 kl. 08.01 UTCresolved

      This incident has been resolved.

    10. 26. maj 2026 kl. 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

    Startede 12. maj 2026 kl. 11.54 UTC · 26m

    IssuesMindre hændelse
    Berørte komponenter
    OneAPI REST APICloudBoxx REST API (Classic)SmartControl
    1. 12. maj 2026 kl. 11.54 UTCinvestigating

      Setups are currently not being processed

    2. 12. maj 2026 kl. 11.59 UTCmonitoring

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

    3. 12. maj 2026 kl. 12.20 UTCresolved

      This incident has been resolved

    FleetControl issues: Delayed event processing for some vehicles

    Startede 14. april 2026 kl. 14.53 UTC · 31m

    IssuesMindre hændelse
    Berørte komponenter
    FleetControl
    1. 14. april 2026 kl. 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 kl. 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

    Startede 31. marts 2026 kl. 08.16 UTC · 16m

    OutageStørre hændelse
    Berørte komponenter
    OneAPI REST APICloudBoxx Events, Trackings, Heartbeats (Classic)LoginCloudBoxx REST API (Classic)FleetControlService PartnersDriving AnalysisSmartControlDamage Detection Activation/DeactivationOneAPI Event ConsumersAnomaly Detection
    1. 31. marts 2026 kl. 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. marts 2026 kl. 08.22 UTCidentified

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

    3. 31. marts 2026 kl. 08.26 UTCidentified

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

    4. 31. marts 2026 kl. 08.27 UTCmonitoring

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

    5. 31. marts 2026 kl. 08.32 UTCresolved

      This incident has been resolved.

    [ONLY BELGIUM] Connectivity issues with Proximus Belgium

    Startede 16. marts 2026 kl. 12.10 UTC · 2h 41m

    IssuesMindre hændelse
    Berørte komponenter
    CloudBoxx 4G (LTE / 2G)CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 3G (3G / 2G)
    1. 16. marts 2026 kl. 12.10 UTCidentified

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

    2. 16. marts 2026 kl. 13.42 UTCidentified

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

    3. 16. marts 2026 kl. 14.50 UTCresolved

      Our devices connected to alternative networks.

    Monitoring cellular connectivity issues on some CloudBoxx 4G devices

    Startede 10. marts 2026 kl. 16.27 UTC · 2h 34m

    Pending
    Berørte komponenter
    CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
    1. 10. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 19.01 UTCresolved

      This incident has been resolved.

    CloudBoxx 1020 connectivity service degradation

    Startede 25. februar 2026 kl. 10.30 UTC · 8h 29m

    IssuesMindre hændelse
    Berørte komponenter
    CloudBoxx 1020 (LTE-M / 2G)
    1. 25. februar 2026 kl. 11.06 UTCinvestigating

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

    2. 25. februar 2026 kl. 15.40 UTCinvestigating

      We are continuing to investigate this issue.

    3. 25. februar 2026 kl. 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 kl. 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 kl. 18.32 UTCmonitoring

      All values returned to normal. We continue monitoring.

    6. 25. februar 2026 kl. 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)

    Startede 25. februar 2026 kl. 09.54 UTC · 53m

    IssuesMindre hændelse
    Berørte komponenter
    CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
    1. 25. februar 2026 kl. 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 kl. 10.04 UTCmonitoring

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

    3. 25. februar 2026 kl. 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)

    Startede 25. februar 2026 kl. 00.15 UTC · 6h 34m

    Pending
    Berørte komponenter
    CloudBoxx 4G (LTE / 2G)CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 3G (3G / 2G)
    1. 25. februar 2026 kl. 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 kl. 01.05 UTCmonitoring

      We are continuing to monitor for any further issues.

    3. 25. februar 2026 kl. 06.49 UTCresolved

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

    General issues

    Startede 13. februar 2026 kl. 10.12 UTC · 1h 12m

    IssuesMindre hændelse
    Berørte komponenter
    OneAPI REST APICloudBoxx Events, Trackings, Heartbeats (Classic)CloudBoxx REST API (Classic)FleetControlService PartnersSmartControlOneAPI Event Consumers
    1. 13. februar 2026 kl. 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 kl. 10.15 UTCidentified

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

    3. 13. februar 2026 kl. 10.24 UTCidentified

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

    4. 13. februar 2026 kl. 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 kl. 10.58 UTCmonitoring

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

    6. 13. februar 2026 kl. 11.24 UTCresolved

      This incident has been resolved.

    7. 25. februar 2026 kl. 09.38 UTCpostmortem

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

    Damage Detection Activation delayed

    Startede 12. februar 2026 kl. 13.45 UTC · 5h 8m

    IssuesMindre hændelse
    Berørte komponenter
    Damage Detection Activation/Deactivation
    1. 12. februar 2026 kl. 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 kl. 16.47 UTCmonitoring

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

    3. 12. februar 2026 kl. 18.53 UTCresolved

      This incident has been resolved.

    Monitoring issues with setting up vehicles with the smartcontrol app

    Startede 11. februar 2026 kl. 16.03 UTC · 31m

    IssuesMindre hændelse
    Berørte komponenter
    SmartControlDamage Detection Activation/Deactivation
    1. 11. februar 2026 kl. 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 kl. 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 kl. 16.33 UTCresolved

      This incident has been resolved.

    Cellular connectivity issues in the Netherlands

    Startede 11. februar 2026 kl. 14.53 UTC · 1h 45m

    IssuesMindre hændelse
    Berørte komponenter
    CloudBoxx 1020 (LTE-M / 2G)
    1. 11. februar 2026 kl. 14.53 UTCinvestigating

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

    2. 11. februar 2026 kl. 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 kl. 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 kl. 16.39 UTCresolved

      This incident has been resolved.