eSIM Go incident

Profile 2 & 3 (89320) - API degradation

Major Resolved View vendor source →

eSIM Go experienced a major incident on January 21, 2026 affecting Travel API, lasting 11h 30m. The incident has been resolved; the full update timeline is below.

Started
Jan 21, 2026, 08:51 PM UTC
Resolved
Jan 22, 2026, 08:21 AM UTC
Duration
11h 30m
Detected by Pingoru
Jan 21, 2026, 08:51 PM UTC

Affected components

Travel API

Update timeline

  1. identified Jan 21, 2026, 08:51 PM UTC

    Our upstream provider has identified an issue affecting all API requests relating to Profile 2 and Profile 3 eSIMs (ICCIDS beginning 89320). This will affect the ordering and application of bundles routed via these profiles. Affected bundles include: Turkey India Caribbean destinations Japan and others. A full list of Profile 2 and 3 destinations can be found by checking your most recent rate sheet.

  2. identified Jan 21, 2026, 09:56 PM UTC

    Upstream are still working on resolving the issue. We will provide further updates when we have them.

  3. identified Jan 21, 2026, 11:40 PM UTC

    Upstream inform us that they are close to resolving the issue and expect service to resume shortly. We will provide further updates when we have them.

  4. monitoring Jan 22, 2026, 01:13 AM UTC

    Upstream have implimented a fix and restored services. We will continue monitoring to ensure full stability.

  5. resolved Jan 22, 2026, 08:21 AM UTC

    After monitoring, we are confident that this issue is fully resolved. We will engage with the provider to understand the full cause of the issue and how further occurrences can be prevented. We apologise for the disruption caused.