
eSIM Go Status
Real-time updates of eSIM Go issues and outages
eSIM Go status is Under Maintenance
eSIM Go Travel Management Portal
eSIM Go Travel API
eSIM Go eSIM Connectivity
Active Incidents
Status: On it
CDRs for Profiles 2 and 3 have been delayed since 11:00 UTC today. That means billing for usage on these profiles will run late, and CDRs you receive via SFTP will arrive late too. Service itself is unaffected: data, activations and top-ups are working normally on both profiles.
What we know The delay is upstream, with our network partner. CDRs for all other profiles are arriving on time.
What to do Nothing at your end. Keep selling and activating on Profiles 2 and 3 as normal. If you reconcile usage or bill your own customers from these CDRs, expect figures for Profiles 2 and 3 to be incomplete from 11:00 UTC until the backlog clears.
What comes next Once our network partner has fixed the issue, we’ll process the delayed records and confirm here when they’ve come through. We’re still confirming that every delayed record will be recovered, and we’ll cover that in the next update.
Recently Resolved Incidents
Status: Sorted
Orders failed across all profiles during our planned maintenance window today (11:00–13:00 UTC). The issue has been resolved and order processing is restored as of approximately 11:55 UTC.
What happened A change applied during the maintenance window caused order processing to fail. The fault was identified and fixed within the maintenance window.
What to do Any orders that failed between 11:00 and 11:55 UTC today will need to be retried manually, they will not be reprocessed automatically.
We’re sorry for the disruption this caused during what should have been a routine window.
eSIM Go Outage Survival Guide
You're checking on eSIM Go - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
eSIM Go Components
eSIM Go Travel Management Portal
Status: Sorted
Orders failed across all profiles during our planned maintenance window today (11:00–13:00 UTC). The issue has been resolved and order processing is restored as of approximately 11:55 UTC.
What happened A change applied during the maintenance window caused order processing to fail. The fault was identified and fixed within the maintenance window.
What to do Any orders that failed between 11:00 and 11:55 UTC today will need to be retried manually, they will not be reprocessed automatically.
We’re sorry for the disruption this caused during what should have been a routine window.
eSIM Go Travel API
Status: On it
CDRs for Profiles 2 and 3 have been delayed since 11:00 UTC today. That means billing for usage on these profiles will run late, and CDRs you receive via SFTP will arrive late too. Service itself is unaffected: data, activations and top-ups are working normally on both profiles.
What we know The delay is upstream, with our network partner. CDRs for all other profiles are arriving on time.
What to do Nothing at your end. Keep selling and activating on Profiles 2 and 3 as normal. If you reconcile usage or bill your own customers from these CDRs, expect figures for Profiles 2 and 3 to be incomplete from 11:00 UTC until the backlog clears.
What comes next Once our network partner has fixed the issue, we’ll process the delayed records and confirm here when they’ve come through. We’re still confirming that every delayed record will be recovered, and we’ll cover that in the next update.
Status: Sorted
Orders failed across all profiles during our planned maintenance window today (11:00–13:00 UTC). The issue has been resolved and order processing is restored as of approximately 11:55 UTC.
What happened A change applied during the maintenance window caused order processing to fail. The fault was identified and fixed within the maintenance window.
What to do Any orders that failed between 11:00 and 11:55 UTC today will need to be retried manually, they will not be reprocessed automatically.
We’re sorry for the disruption this caused during what should have been a routine window.