eSIM Go incident

Data Connectivity Issues

Minor Resolved View vendor source →

eSIM Go experienced a minor incident on September 6, 2025 affecting eSIM Connectivity, lasting 7h 27m. The incident has been resolved; the full update timeline is below.

Started
Sep 06, 2025, 10:36 AM UTC
Resolved
Sep 06, 2025, 06:03 PM UTC
Duration
7h 27m
Detected by Pingoru
Sep 06, 2025, 10:36 AM UTC

Affected components

eSIM Connectivity

Update timeline

  1. investigating Sep 06, 2025, 10:36 AM UTC

    We are currently investigating reports of data connectivity issues affecting a small number of Profile 1 (89444...) eSIMs. Our upstream provider has been informed and is actively investigating with us at the highest priority. You can find details of which countries are routed to Profile 1 by consulting the most recent rate sheet. We will provide further updates as soon as we have them.

  2. identified Sep 06, 2025, 11:00 AM UTC

    The issue has been identified. All teams are working towards implementing a solution. We will provide further updates as soon as we have them.

  3. identified Sep 06, 2025, 11:55 AM UTC

    All teams are still working towards implementing a solution. We will provide further updates as soon as we have them.

  4. identified Sep 06, 2025, 12:59 PM UTC

    We believe that we are now entering the final stages of implementing a solution. We will provide further updates as soon as we have them.

  5. monitoring Sep 06, 2025, 02:54 PM UTC

    A fix has been put in place, and we have seen some initial success with previously reported ICCIDs now connecting successfully. All affected ICCIDs should connect and begin working without further input; however, cycling airplane mode on/off may help to establish a new connection. Please reach out to our Support Team if your users continue to face difficulties. We will continue monitoring.

  6. resolved Sep 06, 2025, 06:03 PM UTC

    Having monitored for an extended period of time, we have seen successful data sessions across many of the eSIMs reported to us earlier in the day. This, combined with tests that we have carried out internally, gives us the confidence to mark this issue as resolved. Further details about this incident will be shared in the coming days. We apologise for the service disruption caused.