INVERS incident

CloudBoxx Events (RabbitMQ) issues (only affects one message queue from one customer)

Notice Resolved View vendor source →

INVERS experienced a notice incident on December 17, 2025 affecting CloudBoxx Events, Trackings, Heartbeats (Classic), lasting 57m. The incident has been resolved; the full update timeline is below.

Started
Dec 17, 2025, 09:25 AM UTC
Resolved
Dec 17, 2025, 10:23 AM UTC
Duration
57m
Detected by Pingoru
Dec 17, 2025, 09:25 AM UTC

Affected components

CloudBoxx Events, Trackings, Heartbeats (Classic)

Update timeline

  1. investigating Dec 17, 2025, 09:25 AM UTC

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

  2. identified Dec 17, 2025, 09:32 AM UTC

    It only affects one message queue from one customer, who has been informed; other customers are not affected.

  3. monitoring Dec 17, 2025, 09:37 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Dec 17, 2025, 10:23 AM UTC

    This incident has been resolved.