INVERS incident

CloudBoxx 1020 connectivity service degradation

Minor Resolved View vendor source →
Started
Feb 25, 2026, 10:30 AM UTC
Resolved
Feb 25, 2026, 07:00 PM UTC
Duration
8h 29m
Detected by Pingoru
Feb 25, 2026, 10:30 AM UTC

Affected components

CloudBoxx 1020 (LTE-M / 2G)

Update timeline

  1. investigating Feb 25, 2026, 11:06 AM UTC

    Our monitoring systems detected a service degradation of CloudBoxx 1020 connectivity. We are investigating with our partners.

  2. investigating Feb 25, 2026, 01:33 PM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 25, 2026, 03:40 PM UTC

    We are continuing to investigate this issue.

  4. identified Feb 25, 2026, 05:34 PM UTC

    Our connectivity partner has identified a packet loss in the interconnection to our servers. They will switchover the traffic to another route which is part of our geo-redundant setup.

  5. monitoring Feb 25, 2026, 06:20 PM UTC

    The traffic switchover was successful and we are seeing huge improvements in our metrics. We continue monitoring for further issues.

  6. monitoring Feb 25, 2026, 06:32 PM UTC

    All values returned to normal. We continue monitoring.

  7. resolved Feb 25, 2026, 07:00 PM UTC

    No further issues occurred during the monitoring period. We consider this incident as resolved.

Looking to track INVERS downtime and outages?

Pingoru polls INVERS's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when INVERS reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track INVERS alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring INVERS for free

5 free monitors · No credit card required