INVERS incident

General issues

Minor Resolved View vendor source →

INVERS experienced a minor incident on February 13, 2026 affecting CloudBoxx REST API (Classic) and FleetControl and 1 more component, lasting 1h 12m. The incident has been resolved; the full update timeline is below.

Started
Feb 13, 2026, 10:12 AM UTC
Resolved
Feb 13, 2026, 11:24 AM UTC
Duration
1h 12m
Detected by Pingoru
Feb 13, 2026, 10:12 AM UTC

Affected components

CloudBoxx REST API (Classic)FleetControlOneAPI REST APIOneAPI Event ConsumersCloudBoxx Events, Trackings, Heartbeats (Classic)SmartControlService Partners

Update timeline

  1. investigating Feb 13, 2026, 10:12 AM UTC

    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. identified Feb 13, 2026, 10:15 AM UTC

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

  3. identified Feb 13, 2026, 10:24 AM UTC

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

  4. monitoring Feb 13, 2026, 10:35 AM UTC

    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. monitoring Feb 13, 2026, 10:58 AM UTC

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

  6. resolved Feb 13, 2026, 11:24 AM UTC

    This incident has been resolved.

  7. postmortem Feb 25, 2026, 09:38 AM UTC

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