Simbase incident

[External] - Network signaling issues affecting device connectivity

Minor Resolved View vendor source →

Simbase experienced a minor incident on March 25, 2026, lasting 1h 7m. The incident has been resolved; the full update timeline is below.

Started
Mar 25, 2026, 09:44 AM UTC
Resolved
Mar 25, 2026, 10:52 AM UTC
Duration
1h 7m
Detected by Pingoru
Mar 25, 2026, 09:44 AM UTC

Update timeline

  1. identified Mar 25, 2026, 09:44 AM UTC

    Signaling degradation is causing devices to require multiple connection attempts to the network. Issue identified and fix is being applied. Affected countries: XX

  2. investigating Mar 25, 2026, 09:45 AM UTC

    [2026-03-25 09:35:11] - Incident status was updated. Summary: Investigation ongoing for signalling degradation issue causing some devices to require multiple connection attempts. Team working to identify root cause and mitigate impact.

  3. identified Mar 25, 2026, 09:45 AM UTC

    [2026-03-25 09:39:33] - Incident status was updated. Summary: The issue has been identified with onset at approximately 09:05 UTC. A fix is currently being applied to resolve the signalling degradation. Mitigation efforts are actively underway with ongoing progress updates to follow.

  4. monitoring Mar 25, 2026, 09:51 AM UTC

    [2026-03-25 09:47:10] - Incident status was updated. Summary: The fix has been successfully applied and service is now restored and operating normally. Engineering teams continue to monitor the situation closely to ensure stability. Further updates will be provided if any additional issues are observed.

  5. resolved Mar 25, 2026, 10:52 AM UTC

    [2026-03-25 10:51:39] - Incident status was updated. Summary: The issue has been fully resolved and all services are operating normally.