INVERS incident

General issues

Notice Resolved View vendor source →

INVERS experienced a notice incident on November 13, 2025 affecting CloudBoxx REST API (Classic) and FleetControl and 1 more component, lasting 4h 8m. The incident has been resolved; the full update timeline is below.

Started
Nov 13, 2025, 08:13 AM UTC
Resolved
Nov 13, 2025, 12:22 PM UTC
Duration
4h 8m
Detected by Pingoru
Nov 13, 2025, 08:13 AM UTC

Affected components

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

Update timeline

  1. investigating Nov 13, 2025, 08:13 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. investigating Nov 13, 2025, 08:23 AM UTC

    We are continuing to investigate this issue. Customers connected to the Classic-API are not affected.

  3. monitoring Nov 13, 2025, 08:45 AM UTC

    Due to redundancy, the Classic API functions are still available, and customer operations can continue as normal.

  4. monitoring Nov 13, 2025, 08:47 AM UTC

    The remaining systems are back online, and we are monitoring their stability.

  5. monitoring Nov 13, 2025, 09:02 AM UTC

    Most systems, including FleetControl, have been available again for several minutes. The One API message queue is still unavailable.

  6. monitoring Nov 13, 2025, 09:34 AM UTC

    Most systems have been available for several minutes. The One API message queue has recovered. We are still monitoring the situation and gathering facts about the root cause of this incident.

  7. monitoring Nov 13, 2025, 09:35 AM UTC

    We are continuing to monitor for any further issues.

  8. monitoring Nov 13, 2025, 10:19 AM UTC

    While the systems have all been back up and running for some time now, we have not yet received any reports from our partners that everything is finally running smoothly again. Until then, we will leave the status at "monitoring.”

  9. resolved Nov 13, 2025, 12:22 PM UTC

    Systems remain stable, and we are closing the incident. We will follow up on the issue internally with the responsible teams and our hosting partners and prepare a corresponding document with a summary. Once this is ready, we will announce it here and be available to discuss it with our customers. We apologize for any inconvenience caused by this incident.

  10. postmortem Nov 18, 2025, 03:40 PM UTC

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