Sierra Wireless incident

Service Degradation Notification for Subscribers roaming under Carrier Partner Orange France (GNOC-12459)

Notice Resolved View vendor source →

Sierra Wireless experienced a notice incident on June 18, 2026 affecting Network Connectivity and Data (EU) and 1 more component, lasting 12h 4m. The incident has been resolved; the full update timeline is below.

Started
Jun 18, 2026, 05:07 AM UTC
Resolved
Jun 18, 2026, 05:11 PM UTC
Duration
12h 4m
Detected by Pingoru
Jun 18, 2026, 05:07 AM UTC

Affected components

Network ConnectivityData (EU)DataSMSVoiceVoLTE

Update timeline

  1. investigating Jun 18, 2026, 05:07 AM UTC

    Our monitoring systems have detected service degradation for Subscribers roaming under Carrier Partner Orange France on 4G network only. Most of the device services moved to 2G/3G service, however, few devices are failing to switch. 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 degradation in establishing Data, SMS, Voice services and network connectivity. We appreciate your understanding and will provide the next update within 2 hours.

  2. investigating Jun 18, 2026, 08:38 AM UTC

    Our Carrier Partner is actively investigating the issue. We are closely coordinating with them and continuously monitoring the situation. Further updates will be shared within the next 2 hours.

  3. investigating Jun 18, 2026, 10:48 AM UTC

    Our Carrier Partner continues to actively investigate the issue. We are closely coordinating with them and monitoring the situation. Further updates will be shared within the next 2 hours. We appreciate your patience and understanding.

  4. identified Jun 18, 2026, 12:45 PM UTC

    The issue has been identified, and a fix is currently being implemented by our carrier partner. We apologize for any inconvenience caused and appreciate your patience and understanding while the corrective actions are being taken.

  5. monitoring Jun 18, 2026, 03:34 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. resolved Jun 18, 2026, 05:11 PM UTC

    This incident has been resolved.