INVERS incident

Cloudboxx (REST API) issues

Critical Resolved View vendor source →

INVERS experienced a critical incident on December 1, 2025 affecting CloudBoxx REST API (Classic) and CloudBoxx Events, Trackings, Heartbeats (Classic), lasting 44m. The incident has been resolved; the full update timeline is below.

Started
Dec 01, 2025, 04:06 PM UTC
Resolved
Dec 01, 2025, 04:50 PM UTC
Duration
44m
Detected by Pingoru
Dec 01, 2025, 04:06 PM UTC

Affected components

CloudBoxx REST API (Classic)CloudBoxx Events, Trackings, Heartbeats (Classic)

Update timeline

  1. investigating Dec 01, 2025, 04:06 PM UTC

    We are currently experiencing issues with our CloudBoxx REST API and CloudBoxx Events (RabbitMQ). Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.

  2. monitoring Dec 01, 2025, 04:19 PM UTC

    Services have already recovered, we are investigating the incident cause.

  3. resolved Dec 01, 2025, 04:50 PM UTC

    This incident has been resolved.

  4. postmortem Dec 09, 2025, 12:35 PM UTC

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