Invers 中断历史

1. 2026年9月2日 UTC 11:22investigating

   我们的服务目前遇到问题。 我们的事故反应小组正在调查 将尽快发布最新消息.

2. 2026年9月2日 UTC 11:27investigating

   一些服务预计故障率会高于通常(20%),这意味着约80%的请求没有受到影响。 报复可以解决临时问题。 这也影响到事件传送,这可能导致事件稍有延误.

3. 2026年9月2日 UTC 11:34investigating

   我们正在继续调查这一问题.

4. 2026年9月2日 UTC 11:55investigating

   我们的伙伴能够确定出错的原因,他们和INVERS正与所有现有小组合作解决这一问题.

5. 2026年9月2日 UTC 12:13investigating

   其根源已追溯到我们托管供应商的连通性问题。 他们的工程团队已经确定了灾区,并正在积极恢复全部功能. INVERS小组继续与它们密切协调,以加快修复工作。 如前所指出,影响有限——大约80%的请求继续正常处理,重审解决了大多数临时故障. 延迟事件传输仍然是主要的副作用.

6. 2026年9月2日 UTC 12:14identified

   这一问题已经确定,一个解决办法正在实施之中.

7. 2026年9月2日 UTC 12:16monitoring

   故障率和事件传输恢复.

8. 2026年9月2日 UTC 12:17monitoring

   我们正在继续监测任何其他问题.

9. 2026年9月2日 UTC 12:33resolved

   此事已决. 故障率和事件传输恢复正常稳定.

自动翻译自官方事件更新。

1. 2026年8月27日 UTC 07:21monitoring

   我们的监测从协调世界时06:58–07:08发现了问题。 局势已经恢复,调查仍在进行.

2. 2026年8月27日 UTC 07:49monitoring

   我们正在继续监测任何其他问题.

3. 2026年8月27日 UTC 12:36resolved

   这一事件已经得到解决。 稍后将提交一份详细的事件发生后报告.

4. 2026年8月31日 UTC 09:02postmortem

   事件报告\(死后\)可以从我们的支援团队获取,网址是[[email protected]](mailto:[email protected]).

自动翻译自官方事件更新。

1. 2026年7月23日 UTC 01:02identified

   我们正用我们的 OneAPI 和 Insights Events 消息队列处理问题 。 我们的事故反应小组正在调查 将尽快发布最新消息.

2. 2026年7月23日 UTC 01:15monitoring

   一项措施已经执行,我们正在监测结果.

3. 2026年7月23日 UTC 01:21resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月16日 UTC 16:55identified

   我们的服务目前遇到问题。 我们的紧急待命人员正在调查 将尽快发布最新消息.

2. 2026年7月16日 UTC 17:10monitoring

   我们的数据中心之间的沟通问题已经解决了 一切都恢复正常了 我们一直在监视局势.

3. 2026年7月16日 UTC 18:57resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年6月29日 UTC 07:55investigating

   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. 2026年6月29日 UTC 08:22investigating

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

3. 2026年6月29日 UTC 09:12identified

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

4. 2026年6月29日 UTC 09:38monitoring

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

5. 2026年6月29日 UTC 09:47monitoring

   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. 2026年6月29日 UTC 11:15resolved

   This incident has been resolved.

1. 2026年6月18日 UTC 07:13investigating

   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. 2026年6月18日 UTC 08:43investigating

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

3. 2026年6月18日 UTC 10:56investigating

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

4. 2026年6月18日 UTC 12:47identified

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

5. 2026年6月18日 UTC 13:52monitoring

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

6. 2026年6月18日 UTC 13:55monitoring

   We are continuing to monitor for any further issues.

7. 2026年6月18日 UTC 14:53resolved

   This incident has been resolved.

1. 2026年5月28日 UTC 08:46investigating

   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. 2026年5月28日 UTC 08:53identified

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

3. 2026年5月28日 UTC 08:56monitoring

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

4. 2026年5月28日 UTC 09:16monitoring

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

5. 2026年5月28日 UTC 11:12resolved

   This incident has been resolved.

1. 2026年5月19日 UTC 18:55investigating

   We currently experience cellular connectivity issues. We are investigating.

2. 2026年5月19日 UTC 19:06investigating

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

3. 2026年5月19日 UTC 19:25investigating

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

4. 2026年5月19日 UTC 20:22identified

   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. 2026年5月19日 UTC 20:52identified

   The situation regarding the remaining units continues to stabilize.

6. 2026年5月19日 UTC 21:37identified

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

7. 2026年5月19日 UTC 22:03monitoring

   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. 2026年5月19日 UTC 22:05monitoring

   We are continuing to monitor for any further issues.

9. 2026年5月20日 UTC 08:01resolved

   This incident has been resolved.

10. 2026年5月26日 UTC 07:38postmortem

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

1. 2026年5月12日 UTC 11:54investigating

   Setups are currently not being processed

2. 2026年5月12日 UTC 11:59monitoring

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

3. 2026年5月12日 UTC 12:20resolved

   This incident has been resolved

1. 2026年4月14日 UTC 14:53monitoring

   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. 2026年4月14日 UTC 15:24resolved

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

1. 2026年3月31日 UTC 08:16investigating

   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. 2026年3月31日 UTC 08:22identified

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

3. 2026年3月31日 UTC 08:26identified

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

4. 2026年3月31日 UTC 08:27monitoring

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

5. 2026年3月31日 UTC 08:32resolved

   This incident has been resolved.

1. 2026年3月16日 UTC 12:10identified

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

2. 2026年3月16日 UTC 13:42identified

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

3. 2026年3月16日 UTC 14:50resolved

   Our devices connected to alternative networks.

1. 2026年3月10日 UTC 16:27investigating

   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. 2026年3月10日 UTC 17:27identified

   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. 2026年3月10日 UTC 17:49monitoring

   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. 2026年3月10日 UTC 19:01resolved

   This incident has been resolved.

1. 2026年2月25日 UTC 11:06investigating

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

2. 2026年2月25日 UTC 15:40investigating

   We are continuing to investigate this issue.

3. 2026年2月25日 UTC 17:34identified

   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. 2026年2月25日 UTC 18:20monitoring

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

5. 2026年2月25日 UTC 18:32monitoring

   All values returned to normal. We continue monitoring.

6. 2026年2月25日 UTC 19:00resolved

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

1. 2026年2月25日 UTC 09:54investigating

   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. 2026年2月25日 UTC 10:04monitoring

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

3. 2026年2月25日 UTC 10:48resolved

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

1. 2026年2月25日 UTC 01:04monitoring

   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. 2026年2月25日 UTC 01:05monitoring

   We are continuing to monitor for any further issues.

3. 2026年2月25日 UTC 06:49resolved

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

1. 2026年2月13日 UTC 10:12investigating

   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. 2026年2月13日 UTC 10:15identified

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

3. 2026年2月13日 UTC 10:24identified

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

4. 2026年2月13日 UTC 10:35monitoring

   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. 2026年2月13日 UTC 10:58monitoring

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

6. 2026年2月13日 UTC 11:24resolved

   This incident has been resolved.

7. 2026年2月25日 UTC 09:38postmortem

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

1. 2026年2月12日 UTC 13:45identified

   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. 2026年2月12日 UTC 16:47monitoring

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

3. 2026年2月12日 UTC 18:53resolved

   This incident has been resolved.

1. 2026年2月11日 UTC 16:03identified

   We are currently analyzing reported cases and investigating whether there is a general problem. We will post here when there are new findings.

2. 2026年2月11日 UTC 16:12monitoring

   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. 2026年2月11日 UTC 16:33resolved

   This incident has been resolved.

1. 2026年2月11日 UTC 14:53investigating

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

2. 2026年2月11日 UTC 16:06identified

   The data communication in NL KPN network is degraded. We are temporary blocking this network. The CloudBoxxes will switch to other available networks.

3. 2026年2月11日 UTC 16:25monitoring

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

4. 2026年2月11日 UTC 16:39resolved

   This incident has been resolved.