All Systems Operational

Uptime over the past 90 days. View historical uptime.
Travel Management Portal Operational
90 days ago
100.0 % uptime
Today
Travel API Operational
90 days ago
99.97 % uptime
Today
UK Domestic Management Portal Operational
90 days ago
100.0 % uptime
Today
UK Domestic API Operational
90 days ago
100.0 % uptime
Today
eSIM Go Website Operational
90 days ago
100.0 % uptime
Today
eSIM Connectivity Operational
90 days ago
99.88 % uptime
Today
eSIM Installations Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

eSIM Go Maintenance Jun 17, 2026 10:00-12:00 UTC

Dear Partners,

We will be introducing enhancements and performance improvements to the eSIM Go API and Portal.

There is no expected impact or downtime during this window, and all operations are expected to work as normal.

Please note there will be no requirement for you to alter your integrations before, during or after this change.
Posted on Jun 10, 2026 - 15:20 UTC
Jun 11, 2026

No incidents reported today.

Jun 10, 2026
Profiles 1 & 5 Connectivity (89444... and 89353...)
Resolved - Following an extended period of monitoring, both our provider's data and our own shows that connections and data usage remain stable.

We believe this incident is now resolved. Please contact our support team with a list of impacted ICCIDs to arrange a refund.

We are conducting a postmortem and will share our findings once we have a full understanding of the cause and impact. We are very sorry for the disruption this has caused to your business.
Jun 10, 09:30 UTC
Update - Following successful implementation of a fix from our upstream provider around 4pm, we have not been made aware of ongoing issues and we are seeing data connections establish within normal parameters.

If your customers are still experiencing problems, please contact us. Our 24/7 teams continue to monitor stability and remain on standby as per our SLA. We will begin processing refunds tomorrow once the incident is classed as completely resolved.

We apologise for the impact this may have had on your customer teams and your customers.
Jun 9, 21:41 UTC
Update - We are observing a stable service with all new orders, however, we are still receiving intermittent reports related to eSIMs ordered before the outage which started at 10:00 UTC on 09/06. This has been raised to our upstream provider for escalation and investigation.

If you are facing an outstanding issue with an eSIM, please issue a replacement eSIM and provide any impacted ICCIDs to our support team, who will be able to issue a refund to your account.
Jun 9, 18:16 UTC
Update - Our upstream provider has successfully rerouted traffic to the alternate route and we are waiting for the cloud provider to confirm that the emergency maintenance window was successful.

We are starting to see traffic levels increase again but will continue to monitor until traffic returns to normal.
Jun 9, 15:19 UTC
Update - We have received confirmation from our upstream mobile operator that the fix was not able to restore service to full capacity. The mobile operator is now rerouting traffic to an alternate route on their network which should improve stability, ahead of a full fix.

We have our mobile operator, their cloud provider and our OCS vendor all working on this and will continue to monitor traffic as we progress.

The issue arose during emergency maintenance related to Cloud Direct Connect infrastructure between the Mobile Operator and our OCS vendor. An emergency maintenance window has been put in place by the cloud provider that started at 11 and is now expected to last until 15:00 UTC. We will provide a further update when this is complete. Once service is resumed, we will be conducting a complete RCA and will share this.
Jun 9, 13:42 UTC
Update - Following a period of monitoring, we have not seen traffic return to normal so we have escalated this with our upstream provider.

They are implementing another fix and we will be able to provide a further update at 13:30 UTC.
Jun 9, 12:49 UTC
Monitoring - Upstream have put a fix in place to restore service. Traffic is increasing towards normal operational levels.
We will continue monitoring this incredibly closely and will continue to work with our provider to understand the root cause.

Further updates to this issue will be provided once we know more.
Jun 9, 11:43 UTC
Update - The temporary 503 errors were due to our provider rebooting some systems to improve service.
The API is now fully operational.

Connectivity degradation is still being investigated.
Jun 9, 11:28 UTC
Update - We are continuing to experience issues with our upstream providers for Profile 1 and 5. This may result in our API returning 503 "Service Unavailable" errors.

We are still investigating this and will provide updates as soon as possible.
Jun 9, 10:51 UTC
Investigating - Our Profile 1 & 5 provider has informed us that they are currently investigating issues with degraded connectivity across their platform.
They are investigating this with urgency and will provide an update as soon as possible.
Jun 9, 10:24 UTC
Jun 9, 2026
Jun 8, 2026

No incidents reported.

Jun 7, 2026
Czech Republic Connectivity - Profiles 1 & 5 (89444 & 89353)
Resolved - After a period of monitoring, we are seeing continued growth in Czech Republic traffic.
We beleive that this incident is now resolved.
Please reach out to our Support Team if you have any further issues.
We apologise for the disruption.
Jun 7, 19:50 UTC
Monitoring - A fix has been implemented and is showing positive results.
We are now seeing successful usage in the Czech Republic across Profiles 1 & 5.

Please ask end users to retry their connections. Any continued issues should be reported to our Support Team.

We will continue monitoring performance.
Jun 7, 12:28 UTC
Investigating - We are continuing to investigate connectivity issues in the Czech Republic that have persisted over the last few days.
We are actively working alongside our upstream partners to resolve this disruption and restore full stability.

In the meantime, the issue may be bypassed by using the EU+ bundle from Profile 4.
Jun 7, 08:58 UTC
Jun 6, 2026
New Zealand Connectivity - Profile 1 (89444...)
Resolved - After a period of monitoring, we are seeing traffic levels returning to normal in New Zealand.
This incident is now resolved.
Please reach out to our Support Team if you have any further issues.
We apologise for the disruption.
Jun 6, 08:30 UTC
Monitoring - We are seeing traffic starting to improve once more in New Zealand.
Please ask end users to retry their connections. Any continued issues should be reported to our Support Team.

We will continue monitoring performance.
Jun 5, 12:29 UTC
Update - Investigations are still ongoing between our provider and the local network team.
We apologise for the ongoing nature of this incident.
Jun 5, 07:28 UTC
Update - The issue has been escalated with our Profile 1 Provider, and they are investigating with high priority.
Jun 3, 07:20 UTC
Investigating - We are currently investigating reports of connection issues in New Zealand.
Jun 3, 04:59 UTC
Jun 5, 2026
Jun 4, 2026
CDR Processing Delays - Profile 1, 5 & 6
Resolved - Dear Partners,

Following successful implementation of a fix from our upstream provider, we believe this incident is now resolved. Thank you for your patience and understanding whilst we investigated this. In the unlikely event you are still encountering any CDR-related issues, please do not hesitate to reach out to our support team.
Jun 4, 12:19 UTC
Identified - We are currently experiencing delays in processing CDRs for both Profile 1 and 6. We have already identified the fix and are now working with our upstream provider to get it implemented as soon as possible.

This will have no effect on any active eSIMs or the entitlements on any bundles. No data has been lost and will all be restored once this issue has been resolved.

If you have any questions or concerns, please contact your account manager or our support team. Thank you for your patience whilst we handle this matter.
Jun 4, 10:51 UTC
Jun 3, 2026
eSIM Go Maintenance
Completed - The scheduled maintenance has been completed.
Jun 3, 12:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 3, 10:00 UTC
Scheduled - Dear Partners,

We will be introducing enhancements and performance improvements to the eSIM Go API and Portal.

There is no expected impact or downtime during this window, and all operations are expected to work as normal.

Please note there will be no requirement for you to alter your integrations before, during or after this change.
May 27, 15:02 UTC
Jun 2, 2026

No incidents reported.

Jun 1, 2026

No incidents reported.

May 31, 2026

No incidents reported.

May 30, 2026

No incidents reported.

May 29, 2026

No incidents reported.

May 28, 2026
Profile 4 (89431) Service outage
Resolved - As of 06:30 UTC, our Profile 4 provider has confirmed a full resolution on this matter. After a period of monitoring, we are observing regular and expected levels of usage once again on this Profile.
If you encounter any further issues, please do not hesitate to reach out to our support team.
May 28, 08:44 UTC
Update - Our provider for Profile 4 (ICCIDs beginning 89431) has informed us that the issue has been identified and partially resolved. Data use has started to resume and the full resolution is expected to be deployed by 06:30 UTC. After this, we will continue to monitor the situation and provide any further updates
May 28, 02:17 UTC
Identified - Dear partners,
Our Profile 4 Provider has informed us of an issue causing a sudden loss of service across their Profile. We have been assured that this is being investigated with the highest priority and we are awaiting further updates that we will pass on as soon as they are received.
We apologise for any inconvenience caused during this time.
May 28, 01:13 UTC
← Incident History Powered by Atlassian Statuspage