INVERS incident

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

Resolved after 57 minutes, affecting CloudBoxx Events, Trackings, Heartbeats (Classic), on December 17, 2025.

monitoring Dec 17, 2025, 09:37 AM UTC

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

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.

Your product runs on more than INVERS

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →