INVERS experienced a major incident on February 2, 2026 affecting FleetControl and OneAPI REST API and 1 more component, lasting 1h 19m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 02, 2026, 01:07 PM UTC
We are currently experiencing issues with our FleetControl service. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.
- investigating Feb 02, 2026, 01:14 PM UTC
SmartControl is affected as well. We escalated to further teams.
- investigating Feb 02, 2026, 01:18 PM UTC
Our OneAPI is affected as well. Currently all requests fail. We are working on it with highest priority.
- investigating Feb 02, 2026, 01:20 PM UTC
We are continuing to investigate this issue.
- investigating Feb 02, 2026, 01:35 PM UTC
We are still continuing to investigate this issue and will provide an update as soon as we have more information.
- investigating Feb 02, 2026, 01:50 PM UTC
The issue is still under investigation, and our team is actively working toward a resolution. We’ll provide further updates shortly.
- identified Feb 02, 2026, 01:58 PM UTC
A possible root cause has been identified, and our team is currently investigating further.
- monitoring Feb 02, 2026, 01:59 PM UTC
All of our systems are functional again and we keep monitoring them.
- monitoring Feb 02, 2026, 02:08 PM UTC
The systems are slowly recovering but are not yet fully performing as expected. We are continuing to monitor and work on improvements.
- monitoring Feb 02, 2026, 02:16 PM UTC
All of our systems are now fully operational and we continue to monitor them.
- monitoring Feb 02, 2026, 02:19 PM UTC
We are continuing to monitor for any further issues.
- resolved Feb 02, 2026, 02:27 PM UTC
The systems remain stable and we are closing the incident. We apologize for any inconvenience caused by this incident.
- postmortem Feb 06, 2026, 09:55 AM UTC
The incident report \(post mortem\) is available from our support team at [[email protected]](mailto:[email protected]).