Historia awarii Invers

1. 2 września 2026 11:22 UTCinvestigating

   Obecnie doświadczamy problemów z naszymi usługami. Nasz zespół reagowania na incydenty prowadzi śledztwo. Prześlemy aktualizację ze szczegółami i zakresem incydentu jak najszybciej.

2. 2 września 2026 11:27 UTCinvestigating

   Niektóre usługi spodziewają się wyższego wskaźnika awarii niż zwykle (20%), co oznacza, że ~ 80% wniosków nie ma wpływu. Retries mogą rozwiązać tymczasowe problemy. Dotyczy to również transmisji zdarzeń, która może prowadzić do niewielkiego opóźnienia zdarzeń.

3. 2 września 2026 11:34 UTCinvestigating

   Nadal badamy tę kwestię.

4. 2 września 2026 11:55 UTCinvestigating

   Nasi partnerzy byli w stanie określić źródło błędu, a zarówno oni, jak i INVERS współpracują ze wszystkimi dostępnymi zespołami w celu rozwiązania problemu.

5. 2 września 2026 12:13 UTCinvestigating

   Przyczyna została powiązana z problemem łączności w naszym dostawcy hostingu. Ich zespół inżynieryjny zidentyfikował dotknięty obszar i aktywnie pracuje nad przywróceniem pełnej funkcjonalności. Zespoły INVERS pozostają w ścisłej koordynacji z nimi w celu przyspieszenia naprawy. Jak już wcześniej zauważono, wpływ jest ograniczony - około 80% wniosków nadal normalnie przetwarza i ponownie próbuje rozwiązać większość tymczasowych błędów. Opóźniona transmisja zdarzeń pozostaje głównym efektem wtórnym.

6. 2 września 2026 12:14 UTCidentified

   Problem został zidentyfikowany i jest w trakcie wdrażania.

7. 2 września 2026 12:16 UTCmonitoring

   Odzyskano wskaźnik awarii i transmisję zdarzeń.

8. 2 września 2026 12:17 UTCmonitoring

   Nadal monitorujemy wszelkie dalsze problemy.

9. 2 września 2026 12:33 UTCresolved

   Incydent został rozwiązany. Wskaźnik awarii i transmisji zdarzeń wraca do normy i stabilności.

10. 16 września 2026 07:51 UTCpostmortem

    Raport z incydentu\ (poubojowy\) dostępny jest w [https: / / help.invers.com / incident- reports /] (https: / / help.invers.com / incident- reports /).

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 27 sierpnia 2026 07:21 UTCmonitoring

   Nasze monitorowanie wykryło problemy z 06: 58- 07: 08 UTC. Sytuacja uległa poprawie, a dochodzenie jest w toku.

2. 27 sierpnia 2026 07:49 UTCmonitoring

   Nadal monitorujemy wszelkie dalsze problemy.

3. 27 sierpnia 2026 12:36 UTCresolved

   Ten incydent został rozwiązany. Wkrótce nastąpi szczegółowy raport po incydencie.

4. 31 sierpnia 2026 09:02 UTCpostmortem

   Raport z incydentu\ (poubojowy\) jest dostępny przez nasz zespół wsparcia pod adresem [support @ invers.com] (mailto: support @ invers.com).

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 23 lipca 2026 01:02 UTCidentified

   Obecnie doświadczamy problemów z naszym OneAPI i Insights Events Message Queue. Nasz zespół reagowania na incydenty prowadzi śledztwo. Prześlemy aktualizację ze szczegółami i zakresem incydentu jak najszybciej.

2. 23 lipca 2026 01:15 UTCmonitoring

   Wprowadzono rozwiązanie i monitorujemy wyniki.

3. 23 lipca 2026 01:21 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 16 lipca 2026 16:55 UTCidentified

   Obecnie doświadczamy problemów z naszymi usługami. Nasz personel w pogotowiu prowadzi śledztwo. Prześlemy aktualizację ze szczegółami i zakresem incydentu jak najszybciej.

2. 16 lipca 2026 17:10 UTCmonitoring

   Problemy z komunikacją między naszymi Datacenterami zostały rozwiązane wszystko wróciło do normy. Monitorujemy sytuację.

3. 16 lipca 2026 18:57 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 29 czerwca 2026 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 czerwca 2026 08:22 UTCinvestigating

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

3. 29 czerwca 2026 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 czerwca 2026 09:38 UTCmonitoring

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

5. 29 czerwca 2026 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 czerwca 2026 11:15 UTCresolved

   This incident has been resolved.

1. 18 czerwca 2026 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 czerwca 2026 08:43 UTCinvestigating

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

3. 18 czerwca 2026 10:56 UTCinvestigating

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

4. 18 czerwca 2026 12:47 UTCidentified

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

5. 18 czerwca 2026 13:52 UTCmonitoring

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

6. 18 czerwca 2026 13:55 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 18 czerwca 2026 14:53 UTCresolved

   This incident has been resolved.

1. 28 maja 2026 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 maja 2026 08:53 UTCidentified

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

3. 28 maja 2026 08:56 UTCmonitoring

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

4. 28 maja 2026 09:16 UTCmonitoring

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

5. 28 maja 2026 11:12 UTCresolved

   This incident has been resolved.

1. 19 maja 2026 18:55 UTCinvestigating

   We currently experience cellular connectivity issues. We are investigating.

2. 19 maja 2026 19:06 UTCinvestigating

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

3. 19 maja 2026 19:25 UTCinvestigating

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

4. 19 maja 2026 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 maja 2026 20:52 UTCidentified

   The situation regarding the remaining units continues to stabilize.

6. 19 maja 2026 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 maja 2026 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 maja 2026 22:05 UTCmonitoring

   We are continuing to monitor for any further issues.

9. 20 maja 2026 08:01 UTCresolved

   This incident has been resolved.

10. 26 maja 2026 07:38 UTCpostmortem

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

1. 12 maja 2026 11:54 UTCinvestigating

   Setups are currently not being processed

2. 12 maja 2026 11:59 UTCmonitoring

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

3. 12 maja 2026 12:20 UTCresolved

   This incident has been resolved

1. 14 kwietnia 2026 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 kwietnia 2026 15:24 UTCresolved

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

1. 31 marca 2026 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 marca 2026 08:22 UTCidentified

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

3. 31 marca 2026 08:26 UTCidentified

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

4. 31 marca 2026 08:27 UTCmonitoring

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

5. 31 marca 2026 08:32 UTCresolved

   This incident has been resolved.

1. 16 marca 2026 12:10 UTCidentified

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

2. 16 marca 2026 13:42 UTCidentified

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

3. 16 marca 2026 14:50 UTCresolved

   Our devices connected to alternative networks.

1. 10 marca 2026 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 marca 2026 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 marca 2026 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 marca 2026 19:01 UTCresolved

   This incident has been resolved.

1. 25 lutego 2026 11:06 UTCinvestigating

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

2. 25 lutego 2026 15:40 UTCinvestigating

   We are continuing to investigate this issue.

3. 25 lutego 2026 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 lutego 2026 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 lutego 2026 18:32 UTCmonitoring

   All values returned to normal. We continue monitoring.

6. 25 lutego 2026 19:00 UTCresolved

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

1. 25 lutego 2026 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 lutego 2026 10:04 UTCmonitoring

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

3. 25 lutego 2026 10:48 UTCresolved

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

1. 25 lutego 2026 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 lutego 2026 01:05 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 25 lutego 2026 06:49 UTCresolved

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

1. 13 lutego 2026 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 lutego 2026 10:15 UTCidentified

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

3. 13 lutego 2026 10:24 UTCidentified

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

4. 13 lutego 2026 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 lutego 2026 10:58 UTCmonitoring

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

6. 13 lutego 2026 11:24 UTCresolved

   This incident has been resolved.

7. 25 lutego 2026 09:38 UTCpostmortem

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

1. 12 lutego 2026 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 lutego 2026 16:47 UTCmonitoring

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

3. 12 lutego 2026 18:53 UTCresolved

   This incident has been resolved.

1. 11 lutego 2026 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 lutego 2026 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 lutego 2026 16:33 UTCresolved

   This incident has been resolved.

1. 11 lutego 2026 14:53 UTCinvestigating

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

2. 11 lutego 2026 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 lutego 2026 16:25 UTCmonitoring

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

4. 11 lutego 2026 16:39 UTCresolved

   This incident has been resolved.