INVERS incident

Cellular connectivity issues affecting mainly CloudBoxx 4G units

Notice Resolved View vendor source →

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

Started
Jun 13, 2025, 09:27 AM UTC
Resolved
Jun 13, 2025, 11:55 AM UTC
Duration
2h 27m
Detected by Pingoru
Jun 13, 2025, 09:27 AM UTC

Affected components

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

Update timeline

  1. investigating Jun 13, 2025, 09:27 AM UTC

    We currently experience cellular connectivity issues. We are investigating.

  2. investigating Jun 13, 2025, 09:33 AM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 13, 2025, 09:34 AM UTC

    We are continuing to investigate this issue.

  4. investigating Jun 13, 2025, 09:35 AM UTC

    We are continuing to investigate this issue.

  5. investigating Jun 13, 2025, 09:47 AM UTC

    We are continuing to work with our partners' teams on this issue. We have reached a plateau in terms of missing connections, but have not yet seen any improvement. We will continue to post updates here.

  6. identified Jun 13, 2025, 10:06 AM UTC

    The issue has been identified and a fix is being implemented.

  7. monitoring Jun 13, 2025, 10:09 AM UTC

    The values are back to normal levels.

  8. monitoring Jun 13, 2025, 10:22 AM UTC

    We are continuing to monitor for any further issues.

  9. monitoring Jun 13, 2025, 10:23 AM UTC

    We will monitor it for another hour. If it remains unremarkable, we will close the incident.

  10. identified Jun 13, 2025, 10:36 AM UTC

    The connections are not remaining stable at the low level; we are continuing to work on the issue with our partners.

  11. monitoring Jun 13, 2025, 10:47 AM UTC

    The values are back to normal levels again. We are continuing to monitor for any further issues.

  12. monitoring Jun 13, 2025, 10:57 AM UTC

    We are continuing to monitor for any further issues.

  13. resolved Jun 13, 2025, 11:55 AM UTC

    This incident has been resolved.

  14. postmortem Jun 16, 2025, 11:28 AM UTC

    Our teams \(Support & Connectivity\) have compiled a post-mortem report, which INVERS customers can request at [[email protected]](mailto:[email protected]).