Sierra Wireless incident

Service degradation notification – ESSENTIALS1 SIM Subscriptions in EU and NAM region (GNOC-12766)

Notice Resolved View vendor source →

Sierra Wireless experienced a notice incident on July 31, 2026 affecting Data and SMS and 1 more component, lasting 4h 2m. The incident has been resolved; the full update timeline is below.

Started
Jul 31, 2026, 05:32 AM UTC
Resolved
Jul 31, 2026, 09:34 AM UTC
Duration
4h 2m
Detected by Pingoru
Jul 31, 2026, 05:32 AM UTC

Affected components

DataSMSVoice

Update timeline

  1. investigating Jul 31, 2026, 05:32 AM UTC

    Semtech has detected a Degradation for ESSENTIALS1 SIM subscriptions in the EU and NAM region. Devices currently present in this region may find difficulty establishing a new data session; frequent disconnection from the network may be encountered for existing sessions. We have reported the issue to our partner carrier, and an investigation to determine the scope and cause is underway. Impact: Impacted devices may experience delays in establishing Data, SMS, and Voice services. We appreciate your patience in this regard.

  2. investigating Jul 31, 2026, 07:16 AM UTC

    Our engineers continue working with our partner carrier to bring a resolution on this issue. Impact: Impacted devices may experience delays in establishing Data, SMS, USSD, and Voice Services. We will provide an update in 2 hours.

  3. investigating Jul 31, 2026, 08:23 AM UTC

    Our monitoring system indicates that the services have been restored. Our engineers continue to observe improvements in our partner carrier network. We are closely monitoring to ensure stability. If there are no further impacts, we will consider this resolved after our monitoring period.

  4. monitoring Jul 31, 2026, 09:07 AM UTC

    Our monitoring system indicates that the services have been restored. Our engineers continue to observe improvements in our partner carrier network. We are closely monitoring to ensure stability. If there are no further impacts, we will consider this resolved after our monitoring period.

  5. resolved Jul 31, 2026, 09:34 AM UTC

    This incident has been resolved.