INVERS incident

General issues (Increased request failure rate)

Minor Resolved View vendor source →

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

Started
Sep 02, 2026, 11:22 AM UTC
Resolved
Sep 02, 2026, 12:33 PM UTC
Duration
1h 11m
Detected by Pingoru
Sep 02, 2026, 11:22 AM UTC

Affected components

CloudBoxx REST API (Classic)LoginFleetControlOneAPI REST APIOneAPI Event ConsumersCloudBoxx Events, Trackings, Heartbeats (Classic)SmartControlDamage Detection Activation/DeactivationService PartnersAnomaly Detection

Update timeline

  1. investigating Sep 02, 2026, 11:22 AM UTC

    We are currently experiencing issues with our services. Our incident response team is investigating. We’ll post an update with details and scope of the incident as soon as possible.

  2. investigating Sep 02, 2026, 11:27 AM UTC

    Some services are expecting a higher failure rate than usual (20%), meaning ~80% of requests are unaffected. Retries can resolve temporary issues. This also affects event transmission which can lead to events being slightly delayed.

  3. investigating Sep 02, 2026, 11:34 AM UTC

    We are continuing to investigate this issue.

  4. investigating Sep 02, 2026, 11:55 AM UTC

    Our partners were able to determine the source of the error, and both they and INVERS are working with all available teams to resolve the issue.

  5. investigating Sep 02, 2026, 12:13 PM UTC

    The root cause has been traced to a connectivity issue at our hosting provider. Their engineering team has identified the affected area and is actively working to restore full functionality. INVERS teams remain in close coordination with them to accelerate the fix. As previously noted, the impact is limited — roughly 80% of requests continue to process normally, and retries resolve most temporary failures. Delayed event transmission remains the main secondary effect.

  6. identified Sep 02, 2026, 12:14 PM UTC

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

  7. monitoring Sep 02, 2026, 12:16 PM UTC

    Failure rate and event transmission has recovered.

  8. monitoring Sep 02, 2026, 12:17 PM UTC

    We are continuing to monitor for any further issues.

  9. resolved Sep 02, 2026, 12:33 PM UTC

    The incident has been resolved. Failure rate and event transmission is back to normal and stable.

  10. postmortem Sep 16, 2026, 07:51 AM UTC

    The incident report \(post mortem\) is available from [https://help.invers.com/incident-reports/](https://help.invers.com/incident-reports/).