Simbase incident

[External] - SMS with no content

Notice Resolved View vendor source →

Simbase experienced a notice incident on July 21, 2026, lasting 3h 39m. The incident has been resolved; the full update timeline is below.

Started
Jul 21, 2026, 10:01 AM UTC
Resolved
Jul 21, 2026, 01:41 PM UTC
Duration
3h 39m
Detected by Pingoru
Jul 21, 2026, 10:01 AM UTC

Update timeline

  1. investigating Jul 21, 2026, 10:01 AM UTC

    Investigating reports of mobile-originated SMS messages with no content. Affected countries: XX

  2. investigating Jul 21, 2026, 10:01 AM UTC

    [2026-07-21 09:43:00] - Incident status was updated. Summary: Investigation underway for reports of mobile-originated SMS messages being delivered without content. Further updates to follow.

  3. investigating Jul 21, 2026, 10:21 AM UTC

    [2026-07-21 10:06:40] - Incident status was updated. Summary: Engineers are continuing to investigate the incident. No estimated time to resolution is currently available.

  4. identified Jul 21, 2026, 10:41 AM UTC

    [2026-07-21 10:35:40] - Incident status was updated. Summary: Engineers have isolated the problem and are continuing to work on a resolution. An estimated time to resolution will be provided in a future update.

  5. investigating Jul 21, 2026, 11:41 AM UTC

    [2026-07-21 11:31:46] - Incident status was updated. Summary: Engineers are continuing to work on a fix with no estimated time to resolution currently available.

  6. investigating Jul 21, 2026, 12:41 PM UTC

    [2026-07-21 12:36:08] - Incident status was updated. Summary: A fix has been implemented and is currently being monitored. Initial results appear positive, with ongoing testing and monitoring in progress.

  7. resolved Jul 21, 2026, 01:41 PM UTC

    [2026-07-21 13:25:44] - Incident status was updated. Summary: All testing has been successful and the full fix has been deployed. The incident has been resolved.