eSIM Go Outage History

Started Oct 23, 2026, 08:41 AM UTC· resolved Oct 23, 2026, 10:28 AM UTC

1. investigating Oct 23, 2026, 08:41 AM UTC

   Status: On it Since at least 22:00 UTC, end users on Orange networks have been having trouble connecting to 4G. This affects all profiles. If your customers are travelling in a market where we use Orange, some of them are probably affected right now. What we know: This affects all profiles in every market where Orange is one of our network partners. We don’t know the cause yet. Our network partners have raised it with Orange, and we’re working on it with them. What to do: Where another network is available, ask end users to manually switch to it. In the eSIM’s network settings, they turn off automatic network selection and pick any network other than Orange. It takes a minute on the device, but your customers will need to be told how to do it. If you're not sure, we have articles for how to do this on various devices in our help centre: help.esim-go.com Where no other network is available, there’s no workaround while this is open. Once this is fixed, end users can turn automatic selection back on. We’ll tell you when. What comes next: We don’t have a fix time yet. We’ll update at 10:30 UTC whether or not we have one.

2. resolved Oct 23, 2026, 10:28 AM UTC

   4G is working normally again on Orange networks in Europe and Morocco, on all profiles. The fault was on the Orange network, and it has been fixed. What to do: If any end users switched networks by hand, they may now turn automatic network selection back on in the eSIM’s network settings if they wish. Nothing else is needed at your end.

Read the full incident report →

Started Oct 09, 2026, 12:37 AM UTC· resolved Oct 09, 2026, 12:52 PM UTC

1. investigating Oct 09, 2026, 12:37 AM UTC

   In the last hour, we have seen an increase in issues relating to Profile 5 connectivity in Saudi Arabia. What we know Profile 5 connectivity is affected in Saudi Arabia. We don’t know the cause yet. We’re working on it with our network partner. What to do There is currently no workaround available for this issue. We are working on it. What comes next We don’t have a fix time yet. We’ll update once we have more information.

2. investigating Oct 09, 2026, 03:12 AM UTC

   No change yet. Engineers are still on it with our network partner, and we don’t have a fix time. End users on Profile 5 in Saudi Arabia are still seeing patchy or no data. What comes next We don’t have a fix time yet. We’ll update once we have more information.

3. monitoring Oct 09, 2026, 08:06 AM UTC

   Data on Profile 5 in Saudi Arabia looks to be working normally again. Traffic is increasing close to normal levels. We’re keeping it under watch before we call it fixed. What to do If any of your end users are still seeing patchy or no data, please reach out to our Support Team so we can check their connection. What comes next We’ll confirm here when we are confident it’s fixed

4. resolved Oct 09, 2026, 12:52 PM UTC

   Data on Profile 5 in Saudi Arabia looks to be working normally again. Traffic has returned to normal levels. What to do If any of your end users are still seeing patchy or no data, please reach out to our Support Team so we can check their connection. What comes next There will be no further updates. This incident is resolved.

Read the full incident report →

Started Aug 26, 2026, 12:20 PM UTC· resolved Aug 26, 2026, 04:29 PM UTC

1. identified Aug 26, 2026, 12:20 PM UTC

   We have noticed some degradation in APIs relating to Profiles 2 and 3. Connectivity is unaffected: eSIMs already active on these Profiles are working normally. We're still assessing the scale of this and are working with our provider to understand the cause.

2. identified Aug 26, 2026, 01:19 PM UTC

   Our provider has reported that API services are now recovering. They report that connectivity services may also be degraded. Our provider is continuing to work on restoring full service. We will provide further updates as we receive them.

3. identified Aug 26, 2026, 02:27 PM UTC

   We believe this incident is causing some further degradation on eSIMGo's API and Portal. Some functions, for Profiles other than 2 & 3, on our API and Portal may not currently be available. We are still working to fix this as soon as possible and hope to provide a positive update soon.

4. monitoring Aug 26, 2026, 03:13 PM UTC

   The eSIM Go platform has now stabilised. The Portal and API are now functioning as expected. Upstream APIs have stabilised with orders and other requests completing successfully. Connectivity looks to be gradually recovering. We will commence a period of monitoring to ensure all services are restored to full strength. Thank you for your patience whilst we handled this matter.

5. resolved Aug 26, 2026, 04:29 PM UTC

   After a period of monitoring, we see that platforms are stable, both ours and our provider's. Connectivity on Profiles 2 and 3 has stabilised; please ask users to retry their connections. A number of stuck orders from during the incident are irretrievable. We'll cancel and refund these tomorrow during business hours and provide a list of those affected. We apologise for any disruption experienced.

Read the full incident report →

Started Aug 13, 2026, 07:40 PM UTC· resolved Aug 14, 2026, 09:01 AM UTC

1. investigating Aug 13, 2026, 07:40 PM UTC

   Our Profiles 1 and 5 provider has informed us of a major outage affecting all data services across some regions. The exact nature and scope of this are being investigated and reviewed. We will provide any further updates on expected recovery times and the exact affected regions as soon as we have this information. While we are investigating, please raise any reports to our support team.

2. identified Aug 13, 2026, 09:03 PM UTC

   Our profile 1 & 5 provider has identified the issue and are making steps towards a resolution. This outage is affecting all data services across these profiles and is not localised to a single region. We will provide further updates on the status of the resolution as soon as they are available to us.

3. monitoring Aug 13, 2026, 09:46 PM UTC

   Our profile 1 & 5 provider has put a resolution in place and since 21:30 UTC, we have began to see a positive restoration of service on eSIMs, and an uptick in overall usage. We will continue to monitor stability and encourage partners to raise any issues should they still be experiencing them.

4. resolved Aug 14, 2026, 09:01 AM UTC

   This incident is now resolved. Following a night of successful monitoring, service has remained stable since restoration began at 21:30 UTC. We thank partners for their patience throughout, if you or your customers experience any further issues, please contact support. We will publish a full root cause analysis after we have completed the investigation in conjunction with our upstream provider.

Read the full incident report →

Started Aug 08, 2026, 07:56 AM UTC· resolved Aug 08, 2026, 11:38 AM UTC

1. investigating Aug 08, 2026, 07:56 AM UTC

   We have identified that our profile 2 &3 orders are failing. We are currently investigating this issue.

2. monitoring Aug 08, 2026, 09:17 AM UTC

   A fix has been implemented and we are monitoring the results. We are seeing successful orders.

3. resolved Aug 08, 2026, 11:38 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 01, 2026, 04:28 PM UTC· resolved Aug 02, 2026, 11:14 AM UTC

1. investigating Aug 01, 2026, 04:28 PM UTC

   We are working with our Profile 1 & 5 Provider to investigate connectivity in Tunisia.

2. investigating Aug 01, 2026, 07:07 PM UTC

   Our Provider is still investigating the issue. We are temporarily rerouting FIXED-sized Tunisia bundles via Profile 3. Unlimited or Regional bundles will not be rerouted. There are no changes to bundle names or pricing. Please issue new FIXED bundles to affected users.

3. identified Aug 01, 2026, 07:35 PM UTC

   The issue appears to be connected to the Orange Tunisia network. If issuing a replacement SIM via Profile 3, please advise users to select the Ooredoo network.

4. monitoring Aug 01, 2026, 09:37 PM UTC

   Our provider has confirmed that the Orange Tunisia network experienced an outage, which has now been resolved. We see data traffic increasing on previously affected Profile 1 & 5 eSIMs. Users with Profile 1 & 5 eSIMs should experience restored connectivity. Replacement eSIMs issued via Profile 3 will continue to work. We will leave Tunisia bundles routed via Profile 3 while we continue to monitor Profiles 1 & 5. We apologise for this disruption.

5. monitoring Aug 02, 2026, 10:41 AM UTC

   After an extended period of monitoring, we are satisfied that Profile 1 & 5 connectivity is fully restored in Tunisia. We will be routing Tunisia bundles back to Profile 5 at 11:00 UTC today. Replacement eSIMs issued via Profile 3 will continue to work.

6. resolved Aug 02, 2026, 11:14 AM UTC

   Tunisia bundles are now routed back to Profile 5. This incident is resolved. If you issued replacement eSIMs via Profile 3, and require the original Profile 5 eSIMs to be revoked and refunded, please compile a list of these and submit them to our Support Team. We apologise for this disruption.

Read the full incident report →

Started Jul 29, 2026, 04:08 PM UTC· resolved Jul 29, 2026, 08:57 PM UTC

1. identified Jul 29, 2026, 04:08 PM UTC

   We're looking into some connectivity issues on Costa Rica eSIMs on Profiles 1 and 5. We’re working closely with our connectivity provider to identify the cause. While we work to get to the bottom of this, please report any issues you experience to the eSIM Go Support team.

2. monitoring Jul 29, 2026, 05:36 PM UTC

   Our Profiles 1 and 5 provider has been working closely with the local network in Costa Rica to restore service. We now see active data sessions starting to increase. We will continue to monitor performance closely.

3. resolved Jul 29, 2026, 08:57 PM UTC

   After a period of monitoring, we see that usage levels have returned to normal and remained stable. This issue is now resolved. If you continue to experience issues, please raise them to our Support Team. We apologise for the disruption.

Read the full incident report →

Started Jul 28, 2026, 11:04 AM UTC· resolved Jul 29, 2026, 04:11 PM UTC

1. identified Jul 28, 2026, 11:04 AM UTC

   We're aware of some connectivity issues in Germany on Profile 5 eSIMs - not all eSIMs are impacted. While we work with our connectivity provider to get to the bottom of this, please report any issues you experience to the eSIM Go Support team.

2. monitoring Jul 28, 2026, 03:15 PM UTC

   Our connectivity provider found configuration issue that they believe has been causing the connectivity issues seen on some Germany eSIMs They've implemented a fix at 1pm UTC today. We will continue to monitor connectivity in Germany to make sure the fix has resolved this incident. In the meantime, please continue to raise any examples of connectivity issues you see. Thank you for your continued patience while we investigate this.

3. resolved Jul 29, 2026, 04:11 PM UTC

   Following a period of monitoring, we are now satisfied the fix implemented by our upstream provider has been effective in restoring the service in Germany. Thank you for your patience whilst we investigated and resolved this matter. If you encounter any further issues, please do not hesitate to contact our support team.

Read the full incident report →

Started Jul 24, 2026, 09:19 AM UTC· resolved Jul 24, 2026, 12:37 PM UTC

1. investigating Jul 24, 2026, 09:19 AM UTC

   We've been made aware of a connectivity issue impacting Profiles 1 and 5. This has been raised to our connectivity provider and we're working with them to investigate. We'll provide a further update as soon as possible.

2. identified Jul 24, 2026, 10:12 AM UTC

   Our upstream provider have identified the issue and are deploying a fix.

3. monitoring Jul 24, 2026, 11:15 AM UTC

   Our provider for Profiles 1 and 5 has now rolled out a potential fix. As a result, we are now seeing some impacted eSIMs connecting successfully but we expect service to resume gradually. We will continue to monitor this closely to make sure things continue to improve and provide a further update at 12:30 UTC.

4. resolved Jul 24, 2026, 12:37 PM UTC

   We've been monitoring data usage since the last update and this has now returned to normal so we are marking this incident as resolved. We're sorry for the disruption this caused. If you continue to experience any issues, please contact our Support Team. Our Provider will prepare and share an RCA with us. Once we receive this, we will publish a postmortem of the incident.

Read the full incident report →

Started Jul 20, 2026, 07:32 AM UTC· resolved Jul 20, 2026, 10:49 AM UTC

1. investigating Jul 20, 2026, 07:32 AM UTC

   We're experiencing an elevated level of Order API errors related to Profile 2 and Profile 3. We're currently investigating.

2. identified Jul 20, 2026, 08:04 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Jul 20, 2026, 08:07 AM UTC

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

4. resolved Jul 20, 2026, 10:49 AM UTC

   Dear Partners, we are now observing no new errors and believe this incident is now resolved. If you are still experiencing any issues, please do not hesitate to reach out to our support team. We apologise for any inconvenience this caused.

Read the full incident report →

Started Jul 03, 2026, 01:53 PM UTC· resolved Jul 03, 2026, 02:09 PM UTC

1. investigating Jul 03, 2026, 01:53 PM UTC

   We're seeing intermittent connectivity issues on network Profile 4. Our provider for Profile 4 is already aware and looking into the cause of this. Destinations/bundles covered by Profile 4 can be found by checking your latest rate sheet. We will continue to work closely with them to resolve this and provide a further update as soon as possible.

2. resolved Jul 03, 2026, 02:09 PM UTC

   Our Profile 4 provider has informed us that the issue causing intermittent connectivity has been resolved and services should return to normal. We will continue to monitor for the next hour to ensure this is resolved and provide further updates at 15:00 UTC. EDIT at 15:04 UTC: After a period of monitoring, we are seeing no further issues so have resolved this incident.

Read the full incident report →

Started Jun 09, 2026, 10:24 AM UTC· resolved Jun 10, 2026, 09:30 AM UTC

1. investigating Jun 09, 2026, 10:24 AM UTC

   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.

2. investigating Jun 09, 2026, 10:51 AM UTC

   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.

3. investigating Jun 09, 2026, 11:28 AM UTC

   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.

4. monitoring Jun 09, 2026, 11:43 AM UTC

   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.

5. monitoring Jun 09, 2026, 12:49 PM UTC

   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.

6. monitoring Jun 09, 2026, 01:42 PM UTC

   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.

7. monitoring Jun 09, 2026, 03:19 PM UTC

   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.

8. monitoring Jun 09, 2026, 06:16 PM UTC

   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.

9. monitoring Jun 09, 2026, 09:41 PM UTC

   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.

10. resolved Jun 10, 2026, 09:30 AM UTC

    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.

Read the full incident report →

Started Jun 07, 2026, 08:58 AM UTC· resolved Jun 07, 2026, 07:50 PM UTC

1. investigating Jun 07, 2026, 08:58 AM UTC

   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.

2. monitoring Jun 07, 2026, 12:28 PM UTC

   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.

3. resolved Jun 07, 2026, 07:50 PM UTC

   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.

Read the full incident report →

Started Jun 04, 2026, 10:51 AM UTC· resolved Jun 04, 2026, 12:19 PM UTC

1. identified Jun 04, 2026, 10:51 AM UTC

   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.

2. resolved Jun 04, 2026, 12:19 PM UTC

   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.

Read the full incident report →

Started Jun 03, 2026, 04:59 AM UTC· resolved Jun 06, 2026, 08:30 AM UTC

1. investigating Jun 03, 2026, 04:59 AM UTC

   We are currently investigating reports of connection issues in New Zealand.

2. investigating Jun 03, 2026, 07:20 AM UTC

   The issue has been escalated with our Profile 1 Provider, and they are investigating with high priority.

3. investigating Jun 05, 2026, 07:28 AM UTC

   Investigations are still ongoing between our provider and the local network team. We apologise for the ongoing nature of this incident.

4. monitoring Jun 05, 2026, 12:29 PM UTC

   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.

5. resolved Jun 06, 2026, 08:30 AM UTC

   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.

Read the full incident report →

Started May 28, 2026, 01:13 AM UTC· resolved May 28, 2026, 08:44 AM UTC

1. identified May 28, 2026, 01:13 AM UTC

   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.

2. identified May 28, 2026, 02:17 AM UTC

   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

3. resolved May 28, 2026, 08:44 AM UTC

   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.

Read the full incident report →

Started May 19, 2026, 01:58 PM UTC· resolved May 19, 2026, 08:58 PM UTC

1. identified May 19, 2026, 01:58 PM UTC

   Our upstream provider for Profile 4 (ICCIDs beginning 89431) have identified some degraded performance with connectivity. They are actively engaged in resolving these issues as soon as possible. We will update once we have more information.

2. monitoring May 19, 2026, 03:51 PM UTC

   Our upstream provider for Profile 4 has identified the issue, and fixes are being put in place. End users who were experiencing problems should now be able to use 3G and 4G services again as expected. If you are still experiencing any issues, please do not hesitate to reach out to our support team. We will keep the incident open for a monitoring period to ensure all issues have been addressed.

3. resolved May 19, 2026, 08:58 PM UTC

   After a period of monitoring we are no longer observing service degradation on Profile 4 (89431). If any further issues arise, please do not hesitate to reach out to our support team. We apologise for any inconvenience caused during this time.

Read the full incident report →

Started May 05, 2026, 01:56 PM UTC· resolved May 05, 2026, 02:55 PM UTC

1. identified May 05, 2026, 01:56 PM UTC

   We have identified an issue with the SMS service for Profile 4 eSIMs (ICCID: 89431X). Currently, end users may not receive any SMS you send to their eSIMs on this particular profile. No other parts of the service, or any of our other profiles, appear to be affected. This has been raised to our upstream provider as a matter of priority, and we will provide updates as soon as possible.

2. resolved May 05, 2026, 02:55 PM UTC

   Dear Partners, A fix has been implemented for this issue and our SMS service on Profile 4 is now back operational. We apologise for any inconvenience caused. If you encounter any further problems, please do not hesitate to contact our support team.

Read the full incident report →

Started Mar 16, 2026, 02:10 PM UTC· resolved Mar 16, 2026, 02:52 PM UTC

1. identified Mar 16, 2026, 02:10 PM UTC

   Dear Partners, Our providers have informed us of that they are observing severe degradation for data service in Belgium for the Proximus network. The operator is aware and actively working on resolving the issue. Please note, this issue is only impacting Belgium at the moment. Any eSIMs currently in Belgium should automatically connect to our other supported networks, if this is not the case, please advise a device restart or manual network selection of the other networks. We are monitoring the situation closely and will provide updates as soon as they are available to us.

2. resolved Mar 16, 2026, 02:52 PM UTC

   Our providers have informed us that the issues have now been resolved and the Proximus network is operational again

Read the full incident report →

Started Feb 26, 2026, 04:39 PM UTC· resolved Feb 26, 2026, 04:39 PM UTC

1. resolved Feb 26, 2026, 04:39 PM UTC

   To comply with an immediate change in local regulations in Kosovo, we are forced to remove Kosovo from sale with immediate effect. This change impacts Kosovo single country bundles, these will no longer be available to purchase. Regional bundles that include Kosovo will still be available but Kosovo will no longer be included. All bundles currently active or queued will stop working so we will be issuing refunds for all single country bundles currently in use and will provide a list of impacted ICCIDs to impacted partners. We apologise for any inconvenience cause, if you have any questions or need any help, please reach out to the eSIM Go Support team.

Read the full incident report →

Started Jan 21, 2026, 08:51 PM UTC· resolved Jan 22, 2026, 08:21 AM UTC

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.

Read the full incident report →

Started Jan 16, 2026, 09:59 AM UTC· resolved Jan 16, 2026, 01:41 PM UTC

1. investigating Jan 16, 2026, 09:59 AM UTC

   We are currently experiencing an issue with all API requests associated with Profiles 2 & 3. This has been raised as a priority to our upstream provider and we will give our partners any updates as soon as possible. This should not effect any active profile 2/3 eSIMs that are already installed on devices, or the installation of any already created eSIMs. We thank you for our patience whilst we work to resolve this issue.

2. resolved Jan 16, 2026, 01:41 PM UTC

   We are now observing no further errors on Profiles 2 & 3. This is following a fix that was deployed by our upstream provider. After a period of monitoring, we believe this issue is now resolved. If you encounter any further issues, please do not hesitate to get in contact with support. Thank you for your patience and understanding whilst we worked with our upstream provider to resolve this issue.

Read the full incident report →

Started Jan 14, 2026, 09:26 AM UTC· resolved Jan 22, 2026, 08:24 AM UTC

1. identified Jan 14, 2026, 09:26 AM UTC

   Please be informed that, according to the Uganda Communications Commission, data services in Uganda have been temporarily suspended due to election-related procedures. Unfortunately, our provider has no influence over this situation. We will keep you updated as soon as new information becomes available.

2. resolved Jan 22, 2026, 08:24 AM UTC

   The network suspension in Uganda has been lifted.

Read the full incident report →

Started Dec 08, 2025, 02:58 PM UTC· resolved Dec 23, 2025, 11:10 AM UTC

1. investigating Dec 08, 2025, 02:58 PM UTC

   We are currently investigating potential issues across multiple countries that is causing a degredation of service. We have escalated this, as a priority, with our provider and will report back with any updates as soon as we have them.

2. identified Dec 08, 2025, 03:34 PM UTC

   Our Profile 1 Network Provider have found an issue with the online metering service for controlling data usage, and are applying a fix to restore the service. Once this fix is deployed we will provide further updates on the monitoring of the situation.

3. monitoring Dec 08, 2025, 11:14 PM UTC

   Our Profile 1 Provider has implemented a fix and we are observing data consumption services returning to normal. We will continue to monitor the situation. If any ICCIDs encounter further issues of the same type, please raise this with support.

4. resolved Dec 23, 2025, 11:10 AM UTC

   Following a period of monitoring, we are satisfied our Profile 1 Provider's fix has resolved this issue and this incident can now be resolved. If you encounter any further issues, please do not hesitate to get in contact with our support team.

Read the full incident report →

Started Dec 06, 2025, 06:24 PM UTC· resolved Dec 06, 2025, 08:27 PM UTC

1. monitoring Dec 06, 2025, 06:24 PM UTC

   We are aware of an issue that was causing some orders to fail. A fix has been applied for the issue looks to have been successful. We will continue monitoring for a period of time. We apologise for any inconvenience caused.

2. resolved Dec 06, 2025, 08:27 PM UTC

   After a period of monitoring, we believe that the issue is fully resolved. We apologise for any disruption caused.

Read the full incident report →