Monitoring - Status: Nearly there
CDRs for Profiles 2 and 3 have been coming through again since 22:05 UTC. New usage is being recorded normally.
CDRs for usage between 11:00 and 22:05 UTC are still missing. We’re waiting for our network partner to backfill them, and we’ll process them as soon as they arrive.
There’s still nothing you need to do. If you reconcile usage or bill your own customers from these CDRs, figures for Profiles 2 and 3 will stay incomplete for that window until the backfill lands.
Nov 04, 2026 - 22:17 UTC
CDRs for Profiles 2 and 3 have been coming through again since 22:05 UTC. New usage is being recorded normally.
CDRs for usage between 11:00 and 22:05 UTC are still missing. We’re waiting for our network partner to backfill them, and we’ll process them as soon as they arrive.
There’s still nothing you need to do. If you reconcile usage or bill your own customers from these CDRs, figures for Profiles 2 and 3 will stay incomplete for that window until the backfill lands.
Nov 04, 2026 - 22:17 UTC
Investigating - 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.
Nov 04, 2026 - 21:24 UTC
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.
Nov 04, 2026 - 21:24 UTC
Travel Management Portal
Operational
Travel API
Operational
UK Domestic Management Portal
Operational
UK Domestic API
Operational
eSIM Go Website
Operational
eSIM Connectivity
Operational
eSIM Installations
Operational
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.
Scheduled Maintenance
Planned maintenance: Profiles 2 & 3 (89320) Nov 9, 2026 05:30-06:00 UTC
Status: On it
Our Profiles 2 & 3 connectivity supplier is doing maintenance on Monday 9 November, between 05:30 and 06:00 UTC and a period of downtime is expected.
What's affected
During the window, on Profiles 2 and 3:
• API calls to all endpoints may fail or timeout
• Usage data and callbacks will be delayed.
End users who are already connected aren't expected to lose data connectivity. All other profiles are unaffected.
What to do
If your integration retries failed requests automatically, there's nothing to do. Requests will go through once the window closes. If you run scheduled batches or bulk provisioning on Profiles 2 and 3, move them outside 05:30 to 06:00 UTC. No changes are needed to devices or installed profiles.
What comes next
We'll confirm here once the work is done. If you see anything unusual afterwards, contact support.
Posted on Nov 05, 2026 - 13:00 UTC
Our Profiles 2 & 3 connectivity supplier is doing maintenance on Monday 9 November, between 05:30 and 06:00 UTC and a period of downtime is expected.
What's affected
During the window, on Profiles 2 and 3:
• API calls to all endpoints may fail or timeout
• Usage data and callbacks will be delayed.
End users who are already connected aren't expected to lose data connectivity. All other profiles are unaffected.
What to do
If your integration retries failed requests automatically, there's nothing to do. Requests will go through once the window closes. If you run scheduled batches or bulk provisioning on Profiles 2 and 3, move them outside 05:30 to 06:00 UTC. No changes are needed to devices or installed profiles.
What comes next
We'll confirm here once the work is done. If you see anything unusual afterwards, contact support.
Posted on Nov 05, 2026 - 13:00 UTC
Planned maintenance: Profiles 2 & 3 (89320), 16 November, 08:00 to 15:00 UTC Nov 16, 2026 08:00-15:00 UTC
Our network partner is upgrading its infrastructure in one of their nodes on 16 November between 08:00 and 15:00 UTC.
What's affected
During the window, end users on Profiles 2&3 may lose their data connection for up to a minute at a time.
What to do
Nothing is needed at your end. Connections should come back on their own. If an end user's data hasn't returned after a few minutes, turning flight mode off and on again will force the device to reconnect. It's worth letting your support team know about the window so they can recognise short drops as maintenance.
Posted on Oct 29, 2026 - 12:57 UTC
What's affected
During the window, end users on Profiles 2&3 may lose their data connection for up to a minute at a time.
What to do
Nothing is needed at your end. Connections should come back on their own. If an end user's data hasn't returned after a few minutes, turning flight mode off and on again will force the device to reconnect. It's worth letting your support team know about the window so they can recognise short drops as maintenance.
Posted on Oct 29, 2026 - 12:57 UTC