Precios
Historial de estadoActualizaciones RSSAPI de estado

Desarrollado por Uptimus

    Historial de interrupciones de Invers

    54 incidentes de Invers registrados desde junio de 2025, con actualizaciones oficiales, componentes afectados, duración y detalles de resolución.

    Volver al estado actual

    Cuestiones generales (aumento de la tasa de fracaso de las solicitudes)

    Comenzó 2 de septiembre de 2026 a las 11:22 UTC · 1h 11m

    IssuesIncidente menor
    Componentes afectados
    OneAPI REST APICloudBoxx Events, Trackings, Heartbeats (Classic)LoginCloudBoxx REST API (Classic)FleetControlService PartnersDriving AnalysisSmartControlDamage Detection Activation/DeactivationOneAPI Event ConsumersAnomaly Detection
    1. 2 de septiembre de 2026 a las 11:22 UTCinvestigating

      Actualmente estamos experimentando problemas con nuestros servicios. Nuestro equipo de respuesta a incidentes está investigando. Publicaremos una actualización con detalles y alcance del incidente lo antes posible.

    2. 2 de septiembre de 2026 a las 11:27 UTCinvestigating

      Algunos servicios están esperando una tasa de fracaso más alta de lo habitual (20%), lo que significa que ~80% de las solicitudes no son afectadas. Los registros pueden resolver problemas temporales. Esto también afecta la transmisión de eventos que puede llevar a que los eventos sean ligeramente retrasados.

    3. 2 de septiembre de 2026 a las 11:34 UTCinvestigating

      Seguimos investigando esta cuestión.

    4. 2 de septiembre de 2026 a las 11:55 UTCinvestigating

      Nuestros socios pudieron determinar la fuente del error, y tanto ellos como INVERS están trabajando con todos los equipos disponibles para resolver el problema.

    5. 2 de septiembre de 2026 a las 12:13 UTCinvestigating

      La causa raíz se ha rastreado a un problema de conectividad en nuestro proveedor de alojamiento. Su equipo de ingeniería ha identificado la zona afectada y está trabajando activamente para restaurar la funcionalidad completa. Los equipos INVERS permanecen en estrecha coordinación con ellos para acelerar la solución. Como se ha señalado anteriormente, el impacto es limitado: aproximadamente el 80% de las solicitudes continúan procesando normalmente, y los registros resuelven la mayoría de los fracasos temporales. La transmisión tardía de eventos sigue siendo el principal efecto secundario.

    6. 2 de septiembre de 2026 a las 12:14 UTCidentified

      Se ha determinado la cuestión y se está aplicando una solución.

    7. 2 de septiembre de 2026 a las 12:16 UTCmonitoring

      Se ha recuperado la tasa de fracaso y la transmisión de eventos.

    8. 2 de septiembre de 2026 a las 12:17 UTCmonitoring

      Continuamos monitoreando cualquier otro problema.

    9. 2 de septiembre de 2026 a las 12:33 UTCresolved

      El incidente se ha resuelto. La tasa de fracaso y la transmisión de eventos es normal y estable.

    10. 16 de septiembre de 2026 a las 7:51 UTCpostmortem

      El informe sobre el incidente \(post mortem\) puede consultarse en [https://help.invers.com/incident-reports/](https://help.invers.com/incident-reports/).

    Traducido automáticamente desde la actualización oficial del incidente.

    Problemas de API detectados

    Comenzó 27 de agosto de 2026 a las 7:21 UTC · 5h 15m

    Pending
    Componentes afectados
    OneAPI REST APICloudBoxx REST API (Classic)CloudBoxx 4G (LTE / 2G)CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 3G (3G / 2G)
    1. 27 de agosto de 2026 a las 7:21 UTCmonitoring

      Nuestro monitoreo detectó problemas de 06:58–07:08 UTC. La situación se ha recuperado y la investigación está en curso.

    2. 27 de agosto de 2026 a las 7:49 UTCmonitoring

      Continuamos monitoreando cualquier otro problema.

    3. 27 de agosto de 2026 a las 12:36 UTCresolved

      Este incidente ha sido resuelto. En breve se presentará un informe detallado posterior al incidente.

    4. 31 de agosto de 2026 a las 9:02 UTCpostmortem

      El informe del incidente \(post mortem\) está disponible por nuestro equipo de soporte en [[email protected]](mailto:[email protected]).

    Traducido automáticamente desde la actualización oficial del incidente.

    Asuntos de OneAPI e Insights (RabbitMQ)

    Comenzó 23 de julio de 2026 a las 1:02 UTC · 19m

    IssuesIncidente menor
    Componentes afectados
    Driving AnalysisOneAPI Event ConsumersAnomaly Detection
    1. 23 de julio de 2026 a las 1:02 UTCidentified

      Actualmente estamos experimentando problemas con nuestra búsqueda de mensajes de OneAPI e Insights. Nuestro equipo de respuesta a incidentes está investigando. Publicaremos una actualización con detalles y alcance del incidente lo antes posible.

    2. 23 de julio de 2026 a las 1:15 UTCmonitoring

      Se ha aplicado una solución y estamos monitoreando los resultados.

    3. 23 de julio de 2026 a las 1:21 UTCresolved

      Este incidente ha sido resuelto.

    Traducido automáticamente desde la actualización oficial del incidente.

    Cuestiones generales

    Comenzó 16 de julio de 2026 a las 16:55 UTC · 2h 2m

    Pending
    Componentes afectados
    OneAPI REST APICloudBoxx Events, Trackings, Heartbeats (Classic)LoginCloudBoxx REST API (Classic)FleetControlService PartnersDriving AnalysisSmartControlDamage Detection Activation/DeactivationOneAPI Event ConsumersAnomaly Detection
    1. 16 de julio de 2026 a las 16:55 UTCidentified

      Actualmente estamos experimentando problemas con nuestros servicios. Nuestro personal de emergencia está investigando. Publicaremos una actualización con detalles y alcance del incidente lo antes posible.

    2. 16 de julio de 2026 a las 17:10 UTCmonitoring

      Problemas de comunicación entre nuestros Datacenters han sido resueltos todo está de vuelta a la normalidad. Seguimos monitoreando la situación.

    3. 16 de julio de 2026 a las 18:57 UTCresolved

      Este incidente ha sido resuelto.

    Traducido automáticamente desde la actualización oficial del incidente.

    Monitoring cellular connectivity issues with provider Orange in France only

    Comenzó 29 de junio de 2026 a las 7:55 UTC · 3h 21m

    Pending
    Componentes afectados
    CloudBoxx 4G (LTE / 2G)
    1. 29 de junio de 2026 a las 7: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 de junio de 2026 a las 8:22 UTCinvestigating

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

    3. 29 de junio de 2026 a las 9: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 de junio de 2026 a las 9:38 UTCmonitoring

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

    5. 29 de junio de 2026 a las 9: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 de junio de 2026 a las 11:15 UTCresolved

      This incident has been resolved.

    Service Restrictions with the Mobile Carrier “Orange” in France

    Comenzó 18 de junio de 2026 a las 7:13 UTC · 7h 40m

    IssuesIncidente menor
    Componentes afectados
    CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
    1. 18 de junio de 2026 a las 7: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 de junio de 2026 a las 8:43 UTCinvestigating

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

    3. 18 de junio de 2026 a las 10:56 UTCinvestigating

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

    4. 18 de junio de 2026 a las 12:47 UTCidentified

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

    5. 18 de junio de 2026 a las 13:52 UTCmonitoring

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

    6. 18 de junio de 2026 a las 13:55 UTCmonitoring

      We are continuing to monitor for any further issues.

    7. 18 de junio de 2026 a las 14:53 UTCresolved

      This incident has been resolved.

    Monitoring cellular connectivity issues

    Comenzó 28 de mayo de 2026 a las 8:46 UTC · 2h 26m

    Pending
    Componentes afectados
    CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
    1. 28 de mayo de 2026 a las 8: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 de mayo de 2026 a las 8:53 UTCidentified

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

    3. 28 de mayo de 2026 a las 8:56 UTCmonitoring

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

    4. 28 de mayo de 2026 a las 9:16 UTCmonitoring

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

    5. 28 de mayo de 2026 a las 11:12 UTCresolved

      This incident has been resolved.

    Cellular connectivity issues

    Comenzó 19 de mayo de 2026 a las 18:55 UTC · 13h 7m

    OutageIncidente mayor
    Componentes afectados
    CloudBoxx 4G (LTE / 2G)CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 3G (3G / 2G)
    1. 19 de mayo de 2026 a las 18:55 UTCinvestigating

      We currently experience cellular connectivity issues. We are investigating.

    2. 19 de mayo de 2026 a las 19:06 UTCinvestigating

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

    3. 19 de mayo de 2026 a las 19:25 UTCinvestigating

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

    4. 19 de mayo de 2026 a las 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 de mayo de 2026 a las 20:52 UTCidentified

      The situation regarding the remaining units continues to stabilize.

    6. 19 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 22:05 UTCmonitoring

      We are continuing to monitor for any further issues.

    9. 20 de mayo de 2026 a las 8:01 UTCresolved

      This incident has been resolved.

    10. 26 de mayo de 2026 a las 7:38 UTCpostmortem

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

    Adding vehicles and setup problems

    Comenzó 12 de mayo de 2026 a las 11:54 UTC · 26m

    IssuesIncidente menor
    Componentes afectados
    OneAPI REST APICloudBoxx REST API (Classic)SmartControl
    1. 12 de mayo de 2026 a las 11:54 UTCinvestigating

      Setups are currently not being processed

    2. 12 de mayo de 2026 a las 11:59 UTCmonitoring

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

    3. 12 de mayo de 2026 a las 12:20 UTCresolved

      This incident has been resolved

    FleetControl issues: Delayed event processing for some vehicles

    Comenzó 14 de abril de 2026 a las 14:53 UTC · 31m

    IssuesIncidente menor
    Componentes afectados
    FleetControl
    1. 14 de abril de 2026 a las 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 de abril de 2026 a las 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

    Comenzó 31 de marzo de 2026 a las 8:16 UTC · 16m

    OutageIncidente mayor
    Componentes afectados
    OneAPI REST APICloudBoxx Events, Trackings, Heartbeats (Classic)LoginCloudBoxx REST API (Classic)FleetControlService PartnersDriving AnalysisSmartControlDamage Detection Activation/DeactivationOneAPI Event ConsumersAnomaly Detection
    1. 31 de marzo de 2026 a las 8: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 de marzo de 2026 a las 8:22 UTCidentified

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

    3. 31 de marzo de 2026 a las 8:26 UTCidentified

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

    4. 31 de marzo de 2026 a las 8:27 UTCmonitoring

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

    5. 31 de marzo de 2026 a las 8:32 UTCresolved

      This incident has been resolved.

    [ONLY BELGIUM] Connectivity issues with Proximus Belgium

    Comenzó 16 de marzo de 2026 a las 12:10 UTC · 2h 41m

    IssuesIncidente menor
    Componentes afectados
    CloudBoxx 4G (LTE / 2G)CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 3G (3G / 2G)
    1. 16 de marzo de 2026 a las 12:10 UTCidentified

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

    2. 16 de marzo de 2026 a las 13:42 UTCidentified

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

    3. 16 de marzo de 2026 a las 14:50 UTCresolved

      Our devices connected to alternative networks.

    Monitoring cellular connectivity issues on some CloudBoxx 4G devices

    Comenzó 10 de marzo de 2026 a las 16:27 UTC · 2h 34m

    Pending
    Componentes afectados
    CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
    1. 10 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 19:01 UTCresolved

      This incident has been resolved.

    CloudBoxx 1020 connectivity service degradation

    Comenzó 25 de febrero de 2026 a las 10:30 UTC · 8h 29m

    IssuesIncidente menor
    Componentes afectados
    CloudBoxx 1020 (LTE-M / 2G)
    1. 25 de febrero de 2026 a las 11:06 UTCinvestigating

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

    2. 25 de febrero de 2026 a las 15:40 UTCinvestigating

      We are continuing to investigate this issue.

    3. 25 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 18:32 UTCmonitoring

      All values returned to normal. We continue monitoring.

    6. 25 de febrero de 2026 a las 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)

    Comenzó 25 de febrero de 2026 a las 9:54 UTC · 53m

    IssuesIncidente menor
    Componentes afectados
    CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
    1. 25 de febrero de 2026 a las 9: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 de febrero de 2026 a las 10:04 UTCmonitoring

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

    3. 25 de febrero de 2026 a las 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)

    Comenzó 25 de febrero de 2026 a las 0:15 UTC · 6h 34m

    Pending
    Componentes afectados
    CloudBoxx 4G (LTE / 2G)CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 3G (3G / 2G)
    1. 25 de febrero de 2026 a las 1: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 de febrero de 2026 a las 1:05 UTCmonitoring

      We are continuing to monitor for any further issues.

    3. 25 de febrero de 2026 a las 6:49 UTCresolved

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

    General issues

    Comenzó 13 de febrero de 2026 a las 10:12 UTC · 1h 12m

    IssuesIncidente menor
    Componentes afectados
    OneAPI REST APICloudBoxx Events, Trackings, Heartbeats (Classic)CloudBoxx REST API (Classic)FleetControlService PartnersSmartControlOneAPI Event Consumers
    1. 13 de febrero de 2026 a las 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 de febrero de 2026 a las 10:15 UTCidentified

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

    3. 13 de febrero de 2026 a las 10:24 UTCidentified

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

    4. 13 de febrero de 2026 a las 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 de febrero de 2026 a las 10:58 UTCmonitoring

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

    6. 13 de febrero de 2026 a las 11:24 UTCresolved

      This incident has been resolved.

    7. 25 de febrero de 2026 a las 9:38 UTCpostmortem

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

    Damage Detection Activation delayed

    Comenzó 12 de febrero de 2026 a las 13:45 UTC · 5h 8m

    IssuesIncidente menor
    Componentes afectados
    Damage Detection Activation/Deactivation
    1. 12 de febrero de 2026 a las 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 de febrero de 2026 a las 16:47 UTCmonitoring

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

    3. 12 de febrero de 2026 a las 18:53 UTCresolved

      This incident has been resolved.

    Monitoring issues with setting up vehicles with the smartcontrol app

    Comenzó 11 de febrero de 2026 a las 16:03 UTC · 31m

    IssuesIncidente menor
    Componentes afectados
    SmartControlDamage Detection Activation/Deactivation
    1. 11 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 16:33 UTCresolved

      This incident has been resolved.

    Cellular connectivity issues in the Netherlands

    Comenzó 11 de febrero de 2026 a las 14:53 UTC · 1h 45m

    IssuesIncidente menor
    Componentes afectados
    CloudBoxx 1020 (LTE-M / 2G)
    1. 11 de febrero de 2026 a las 14:53 UTCinvestigating

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

    2. 11 de febrero de 2026 a las 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 de febrero de 2026 a las 16:25 UTCmonitoring

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

    4. 11 de febrero de 2026 a las 16:39 UTCresolved

      This incident has been resolved.