INVERS incident

General issues

Notice Resolved View vendor source →

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

Started
Nov 04, 2025, 11:20 PM UTC
Resolved
Nov 04, 2025, 11:42 PM UTC
Duration
22m
Detected by Pingoru
Nov 04, 2025, 11:20 PM UTC

Affected components

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

Update timeline

  1. investigating Nov 04, 2025, 11:20 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. resolved Nov 04, 2025, 11:42 PM UTC

    Minor accessibility issue caused by a brief outage at a provider. No major impact detected. Services are running.

  3. postmortem Nov 05, 2025, 08:58 AM UTC

    # Update on the alert on the status page We subsequently reviewed the alarm procedure that triggered the alarm last night \(European time zone\). It turned out that all our systems were running smoothly at the time, but one alarm value had been configured too low. It was therefore a false alarm, but it proved that the alarm system for the relevant teams also works perfectly at night \(European time zone\).