Invers kesinti geçmişi

1. 2 Eylül 2026 11:22 UTCinvestigating

   Şu anda hizmetlerimizle ilgili sorunlar yaşıyoruz. Olay yanıt ekibimiz araştırıyor. Olayın ayrıntıları ve kapsamı ile en kısa sürede bir güncelleme yayınlayacağız.

2. 2 Eylül 2026 11:27 UTCinvestigating

   Bazı hizmetler her zaman (% 20) daha yüksek bir başarısızlık oranı bekliyor, yani isteklerin% 80'i etkilenmez. Retries geçici sorunları çözebilir. Bu aynı zamanda olaylara yol açan olayı da etkiler.

3. 2 Eylül 2026 11:34 UTCinvestigating

   Bu konuyu araştırmaya devam ediyoruz.

4. 2 Eylül 2026 11:55 UTCinvestigating

   Ortaklarımız hata kaynağını belirleyebildiler ve her ikisi de ve INVERS, sorunu çözmek için mevcut tüm takımlarla çalışıyorlardı.

5. 2 Eylül 2026 12:13 UTCinvestigating

   Kök nedeni, hosting sağlayıcımızda bir bağlantı konusuna izlendi. Mühendislik ekibi etkilenen bölgeyi tespit etti ve tam işlevselliği geri yüklemek için aktif olarak çalışıyor. INVERS takımları düzeltmeyi hızlandırmaları için onlarla yakın bir koordinasyon içinde kalır. Daha önce de belirtildiği gibi, etki sınırlıdır - isteklerin yaklaşık% 80'i normal bir şekilde işlemeye devam eder ve retries çoğu geçici başarısızlığı çözer. Gecikmiş olay iletimi ana ikincil etki kalır.

6. 2 Eylül 2026 12:14 UTCidentified

   Sorun tespit edildi ve bir düzeltme uygulanır.

7. 2 Eylül 2026 12:16 UTCmonitoring

   Başarısızlık oranı ve olay iletimi geri alındı.

8. 2 Eylül 2026 12:17 UTCmonitoring

   Daha fazla sorun için izlemeye devam ediyoruz.

9. 2 Eylül 2026 12:33 UTCresolved

   Olay çözüldü. Başarısızlık ve olay iletimi normal ve istikrarlı geri döndü.

10. 16 Eylül 2026 07:51 UTCpostmortem

    Olay raporu \(post mortem\) [https://help.invers.com/incident-reports/](https://help.invers.com/incident-reports/).

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 27 Ağustos 2026 07:21 UTCmonitoring

   İzlememiz 06:58-07:08 UTC'den tespit edilen sorunlar. Durum iyileşti ve soruşturma devam ediyor.

2. 27 Ağustos 2026 07:49 UTCmonitoring

   Daha fazla sorun için izlemeye devam ediyoruz.

3. 27 Ağustos 2026 12:36 UTCresolved

   Bu olay çözüldü. Detaylı bir posta raporu kısa bir süre takip edecektir.

4. 31 Ağustos 2026 09:02 UTCpostmortem

   Olay raporu \(post mortem\) [[email protected]](mailto:[email protected]).

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 23 Temmuz 2026 01:02 UTCidentified

   Şu anda OneAPI ve Insights Events Mesaj Queue ile ilgili sorunlar yaşıyoruz. Olay yanıt ekibimiz araştırıyor. Olayın ayrıntıları ve kapsamı ile en kısa sürede bir güncelleme yayınlayacağız.

2. 23 Temmuz 2026 01:15 UTCmonitoring

   Bir düzeltme uygulandı ve sonuçları takip ediyoruz.

3. 23 Temmuz 2026 01:21 UTCresolved

   Bu olay çözüldü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 16 Temmuz 2026 16:55 UTCidentified

   Şu anda hizmetlerimizle ilgili sorunlar yaşıyoruz. Acil standby personelimiz araştırıyor. Olayın ayrıntıları ve kapsamı ile en kısa sürede bir güncelleme yayınlayacağız.

2. 16 Temmuz 2026 17:10 UTCmonitoring

   Datacenters arasındaki iletişim sorunları her şeyin normale geri döndü. Durumu izlemeye devam ediyoruz.

3. 16 Temmuz 2026 18:57 UTCresolved

   Bu olay çözüldü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

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

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

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

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

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

   This incident has been resolved.

1. 18 Haziran 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 Haziran 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 Haziran 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 Haziran 2026 12:47 UTCidentified

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

5. 18 Haziran 2026 13:52 UTCmonitoring

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

6. 18 Haziran 2026 13:55 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 18 Haziran 2026 14:53 UTCresolved

   This incident has been resolved.

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

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

3. 28 Mayıs 2026 08:56 UTCmonitoring

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

4. 28 Mayıs 2026 09:16 UTCmonitoring

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

5. 28 Mayıs 2026 11:12 UTCresolved

   This incident has been resolved.

1. 19 Mayıs 2026 18:55 UTCinvestigating

   We currently experience cellular connectivity issues. We are investigating.

2. 19 Mayıs 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 Mayıs 2026 19:25 UTCinvestigating

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

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

   The situation regarding the remaining units continues to stabilize.

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

   We are continuing to monitor for any further issues.

9. 20 Mayıs 2026 08:01 UTCresolved

   This incident has been resolved.

10. 26 Mayıs 2026 07:38 UTCpostmortem

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

1. 12 Mayıs 2026 11:54 UTCinvestigating

   Setups are currently not being processed

2. 12 Mayıs 2026 11:59 UTCmonitoring

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

3. 12 Mayıs 2026 12:20 UTCresolved

   This incident has been resolved

1. 14 Nisan 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 Nisan 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 Mart 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 Mart 2026 08:22 UTCidentified

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

3. 31 Mart 2026 08:26 UTCidentified

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

4. 31 Mart 2026 08:27 UTCmonitoring

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

5. 31 Mart 2026 08:32 UTCresolved

   This incident has been resolved.

1. 16 Mart 2026 12:10 UTCidentified

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

2. 16 Mart 2026 13:42 UTCidentified

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

3. 16 Mart 2026 14:50 UTCresolved

   Our devices connected to alternative networks.

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

   This incident has been resolved.

1. 25 Şubat 2026 11:06 UTCinvestigating

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

2. 25 Şubat 2026 15:40 UTCinvestigating

   We are continuing to investigate this issue.

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

   All values returned to normal. We continue monitoring.

6. 25 Şubat 2026 19:00 UTCresolved

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

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

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

3. 25 Şubat 2026 10:48 UTCresolved

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

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

   We are continuing to monitor for any further issues.

3. 25 Şubat 2026 06:49 UTCresolved

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

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

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

3. 13 Şubat 2026 10:24 UTCidentified

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

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

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

6. 13 Şubat 2026 11:24 UTCresolved

   This incident has been resolved.

7. 25 Şubat 2026 09:38 UTCpostmortem

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

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

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

3. 12 Şubat 2026 18:53 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

1. 11 Şubat 2026 14:53 UTCinvestigating

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

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

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

4. 11 Şubat 2026 16:39 UTCresolved

   This incident has been resolved.