INVERS incident

Cellular connectivity issues

Major Resolved View vendor source →

INVERS experienced a major incident on May 19, 2026 affecting CloudBoxx 1020 (LTE-M / 2G) and CloudBoxx 4G (LTE / 2G) and 1 more component, lasting 13h 6m. The incident has been resolved; the full update timeline is below.

Started
May 19, 2026, 06:55 PM UTC
Resolved
May 20, 2026, 08:01 AM UTC
Duration
13h 6m
Detected by Pingoru
May 19, 2026, 06:55 PM UTC

Affected components

CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)

Update timeline

  1. investigating May 19, 2026, 06:55 PM UTC

    We currently experience cellular connectivity issues. We are investigating.

  2. investigating May 19, 2026, 07:06 PM UTC

    We currently experience cellular connectivity issues with one of our providers. All CloudBoxxes connected via this provider are affected.

  3. investigating May 19, 2026, 07:25 PM UTC

    We are seeing improvements regarding the communication success rate. We will keep monitoring the connectivity metrics.

  4. identified May 19, 2026, 08:22 PM UTC

    Due to scheduled maintenance at a connectivity provider, all devices connected to that provider have been switched over to the alternative connectivity provider. There were brief interruptions during the switchover process. The situation has since stabilized, and the emergency teams and the connectivity team are working on the remaining unstable units.

  5. identified May 19, 2026, 08:52 PM UTC

    The situation regarding the remaining units continues to stabilize.

  6. identified May 19, 2026, 09:37 PM UTC

    It's taking longer for the remaining units to reconnect, but our teams are still on top of the situation

  7. monitoring May 19, 2026, 10:03 PM UTC

    The metrics are almost back to normal levels. The teams will continue to monitor the metrics and mark this incident as resolved if it remains stable over the next few hours.

  8. monitoring May 19, 2026, 10:05 PM UTC

    We are continuing to monitor for any further issues.

  9. resolved May 20, 2026, 08:01 AM UTC

    This incident has been resolved.