INVERS incident

General issues

Critical Resolved View vendor source →

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

Started
Nov 20, 2025, 02:33 PM UTC
Resolved
Nov 20, 2025, 04:23 PM UTC
Duration
1h 49m
Detected by Pingoru
Nov 20, 2025, 02:33 PM UTC

Affected components

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

Update timeline

  1. investigating Nov 20, 2025, 02:33 PM 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 Nov 20, 2025, 02:46 PM UTC

    The issue has been identified, and our hosting provider is currently working on a fix for it.

  3. identified Nov 20, 2025, 03:05 PM UTC

    Our systems are slowly recovering, but are still not fully functional again.

  4. monitoring Nov 20, 2025, 03:11 PM UTC

    All of our systems are functional again, and we keep monitoring them.

  5. resolved Nov 20, 2025, 04:23 PM UTC

    This incident has been resolved.

  6. postmortem Dec 03, 2025, 12:40 PM UTC

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