Historial de interrupciones de Invers

1. September 2, 2026 at 11:22 AM 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. September 2, 2026 at 11:27 AM 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. September 2, 2026 at 11:34 AM UTCinvestigating

   Seguimos investigando esta cuestión.

4. September 2, 2026 at 11:55 AM 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. September 2, 2026 at 12:13 PM 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. September 2, 2026 at 12:14 PM UTCidentified

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

7. September 2, 2026 at 12:16 PM UTCmonitoring

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

8. September 2, 2026 at 12:17 PM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

9. September 2, 2026 at 12:33 PM UTCresolved

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

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

1. August 27, 2026 at 7:21 AM 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. August 27, 2026 at 7:49 AM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

3. August 27, 2026 at 12:36 PM UTCresolved

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

4. August 31, 2026 at 9:02 AM 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.

1. July 23, 2026 at 1:02 AM 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. July 23, 2026 at 1:15 AM UTCmonitoring

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

3. July 23, 2026 at 1:21 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 16, 2026 at 4:55 PM 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. July 16, 2026 at 5:10 PM UTCmonitoring

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

3. July 16, 2026 at 6:57 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. June 29, 2026 at 7:55 AM 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. June 29, 2026 at 8:22 AM UTCinvestigating

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

3. June 29, 2026 at 9:12 AM UTCidentified

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

4. June 29, 2026 at 9:38 AM UTCmonitoring

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

5. June 29, 2026 at 9:47 AM 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. June 29, 2026 at 11:15 AM UTCresolved

   This incident has been resolved.

1. June 18, 2026 at 7:13 AM 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. June 18, 2026 at 8:43 AM UTCinvestigating

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

3. June 18, 2026 at 10:56 AM UTCinvestigating

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

4. June 18, 2026 at 12:47 PM UTCidentified

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

5. June 18, 2026 at 1:52 PM UTCmonitoring

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

6. June 18, 2026 at 1:55 PM UTCmonitoring

   We are continuing to monitor for any further issues.

7. June 18, 2026 at 2:53 PM UTCresolved

   This incident has been resolved.

1. May 28, 2026 at 8:46 AM 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. May 28, 2026 at 8:53 AM UTCidentified

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

3. May 28, 2026 at 8:56 AM UTCmonitoring

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

4. May 28, 2026 at 9:16 AM UTCmonitoring

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

5. May 28, 2026 at 11:12 AM UTCresolved

   This incident has been resolved.

1. May 19, 2026 at 6:55 PM UTCinvestigating

   We currently experience cellular connectivity issues. We are investigating.

2. May 19, 2026 at 7:06 PM UTCinvestigating

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

3. May 19, 2026 at 7:25 PM UTCinvestigating

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

4. May 19, 2026 at 8:22 PM 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. May 19, 2026 at 8:52 PM UTCidentified

   The situation regarding the remaining units continues to stabilize.

6. May 19, 2026 at 9:37 PM UTCidentified

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

7. May 19, 2026 at 10:03 PM 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. May 19, 2026 at 10:05 PM UTCmonitoring

   We are continuing to monitor for any further issues.

9. May 20, 2026 at 8:01 AM UTCresolved

   This incident has been resolved.

10. May 26, 2026 at 7:38 AM UTCpostmortem

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

1. May 12, 2026 at 11:54 AM UTCinvestigating

   Setups are currently not being processed

2. May 12, 2026 at 11:59 AM UTCmonitoring

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

3. May 12, 2026 at 12:20 PM UTCresolved

   This incident has been resolved

1. April 14, 2026 at 2:53 PM 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. April 14, 2026 at 3:24 PM UTCresolved

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

1. March 31, 2026 at 8:16 AM 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. March 31, 2026 at 8:22 AM UTCidentified

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

3. March 31, 2026 at 8:26 AM UTCidentified

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

4. March 31, 2026 at 8:27 AM UTCmonitoring

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

5. March 31, 2026 at 8:32 AM UTCresolved

   This incident has been resolved.

1. March 16, 2026 at 12:10 PM UTCidentified

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

2. March 16, 2026 at 1:42 PM UTCidentified

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

3. March 16, 2026 at 2:50 PM UTCresolved

   Our devices connected to alternative networks.

1. March 10, 2026 at 4:27 PM 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. March 10, 2026 at 5:27 PM 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. March 10, 2026 at 5:49 PM 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. March 10, 2026 at 7:01 PM UTCresolved

   This incident has been resolved.

1. February 25, 2026 at 11:06 AM UTCinvestigating

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

2. February 25, 2026 at 3:40 PM UTCinvestigating

   We are continuing to investigate this issue.

3. February 25, 2026 at 5:34 PM 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. February 25, 2026 at 6:20 PM UTCmonitoring

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

5. February 25, 2026 at 6:32 PM UTCmonitoring

   All values returned to normal. We continue monitoring.

6. February 25, 2026 at 7:00 PM UTCresolved

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

1. February 25, 2026 at 9:54 AM 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. February 25, 2026 at 10:04 AM UTCmonitoring

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

3. February 25, 2026 at 10:48 AM UTCresolved

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

1. February 25, 2026 at 1:04 AM 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. February 25, 2026 at 1:05 AM UTCmonitoring

   We are continuing to monitor for any further issues.

3. February 25, 2026 at 6:49 AM UTCresolved

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

1. February 13, 2026 at 10:12 AM 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. February 13, 2026 at 10:15 AM UTCidentified

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

3. February 13, 2026 at 10:24 AM UTCidentified

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

4. February 13, 2026 at 10:35 AM 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. February 13, 2026 at 10:58 AM UTCmonitoring

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

6. February 13, 2026 at 11:24 AM UTCresolved

   This incident has been resolved.

7. February 25, 2026 at 9:38 AM UTCpostmortem

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

1. February 12, 2026 at 1:45 PM 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. February 12, 2026 at 4:47 PM UTCmonitoring

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

3. February 12, 2026 at 6:53 PM UTCresolved

   This incident has been resolved.

1. February 11, 2026 at 4:03 PM 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. February 11, 2026 at 4:12 PM 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. February 11, 2026 at 4:33 PM UTCresolved

   This incident has been resolved.

1. February 11, 2026 at 2:53 PM UTCinvestigating

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

2. February 11, 2026 at 4:06 PM 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. February 11, 2026 at 4:25 PM UTCmonitoring

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

4. February 11, 2026 at 4:39 PM UTCresolved

   This incident has been resolved.