Soracom Inc. Status - Incident History

Service Incident on the Soracom Platform - Soracom Air for Cellular (Global Coverage)

Tue, 8 Sep 2026 02:04:52 +0000

Major incident - Air for Cellular, plan01s (Rendezvous point: Frankfurt), plan01s (Rendezvous point: Oregon), plan01s (Rendezvous point: Tokyo), plan01s (Rendezvous point: Sydney), planX3 (Rendezvous point: Tokyo), planX3 (Rendezvous point: Frankfurt), planM1, planV1

2026-09-08 · 11:03 JST
Resolved

The following service incident occurred on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plans:

plan01s
plan01s-LDV
planX1
planX3
planX3-EU
planM1
planV1

[Issue Identified]
Some SIMs from the affected plans were unable to connect to the network on the following carrier:

Vodafone (United Kingdom)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-09-08 00:05
End of Incident: 2026-09-08 01:55

We apologize for any inconvenience this incident may have caused. If you still require assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-09-08 · 09:34 JST
Investigating

We are currently experiencing a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plans:

plan01s
plan01s-LDV
planX1
planX3
planX3-EU
planM1
planV1

[Issue Identified]
Some SIMs from the affected plans cannot connect to the network on the following carrier:

Vodafone (United Kingdom)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-09-08 00:05

[Current Status]
Our engineering team is actively investigating the issue.

[Next Update]
As soon as the situation changes or at 2026-09-08 02:30 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

Service Incident on the Soracom Platform - Soracom Air for Cellular (plan-US-max)

Wed, 2 Sep 2026 15:54:15 +0000

Minor incident - Air for Cellular, plan-US-max

2026-09-03 · 00:48 JST
Retroactive

The following service incident occurred on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plan:

plan-US-max

[Issue Identified]
Some SIMs from the affected plan were unable to connect to the network on the following carrier:

AT&T (United States)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-09-02 14:52
End of Incident: 2026-09-02 15:39

We apologize for any inconvenience this incident may have caused. If you still require assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

Service Incident on the Soracom Platform - Soracom Air for Cellular (plan-D and plan-DU)

Wed, 29 Jul 2026 07:31:30 +0000

Major incident - Air for Cellular, plan-D, plan-DU

2026-07-29 · 16:24 JST
Retroactive

The following service incident occurred on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plans:

plan-D
plan-DU

[Issue Identified]
New sessions could not be established.

Existing data sessions were not affected.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-07-29 05:27
End of Incident: 2026-07-29 05:36

We apologize for any inconvenience this incident may have caused. If you still require assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

Service Incident on the Soracom Platform - Soracom Air for Cellular (plan-US-max)

Thu, 30 Jul 2026 02:40:08 +0000

Minor incident - Air for Cellular, plan-US-max

2026-07-30 · 11:34 JST
Post-mortem

Summary

Between 2026-07-24 07:59 and 2026-07-24 12:38 UTC, some Soracom IoT SIM subscriptions experienced issues where new cellular communication sessions could not be established or were difficult to establish.Additionally, a subset of existing cellular communication sessions experienced intermittent disconnections and required re-establishment.

Affected Services

During this period, devices using the following subscriptions were affected:

plan-US-max

Cause

Devices using these subscriptions connect to Soracom via network partner infrastructure through local mobile network operator (MNO) networks.
Regarding this incident, the network provider reported that an issue occurred in their related infrastructure during the affected period.

Resolution

After detecting the abnormal connectivity, Soracom updated the Status Dashboard, began an internal investigation, and escalated the issue to the network provider.
Following actions taken by the network provider, we confirmed that connectivity was restored around 2026-07-24 12:38 UTC.

Future Actions

We will continue to strengthen coordination with the network provider and work to improve service quality.
In addition, we will continue efforts to improve the speed and accuracy of anomaly detection, as well as reduce the time required to identify suspected components and escalate issues to the network provider when issues occur in their infrastructure. We will also continue to improve our customer communication approach.

2026-07-24 · 23:13 JST
Resolved

The following service incident occurred on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plan:

plan-US-max

[Issue Identified]
New sessions could not be created or were difficult to create on plan-US-max.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-07-24 11:00
Start of Recovery Trend: 2026-07-24 13:10
End of Incident: 2026-07-24 14:10

We apologize for any inconvenience this incident may have caused. If you still require assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-07-24 · 22:22 JST
Monitoring

We are currently experiencing a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plan:

plan-US-max

[Issue Identified]
New sessions cannot be created or are difficult to create on plan-US-max.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-07-24 11:00
Start of Recovery Trend: 2026-07-24 13:10

[Current Status]
Our engineering team has observed a recovery trend and is monitoring the service as it recovers.

[Next Update]
As soon as the situation changes or at 2026-07-24 15:00 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-07-24 · 21:16 JST
Issue

We are currently experiencing a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plan:

plan-US-max

[Issue Identified]
New sessions cannot be created or are difficult to create on plan-US-max.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-07-24 11:00 UTC

[Current Status]
Our engineering team is actively investigating the issue.

[Next Update]
As soon as the situation changes or at 2026-07-24 14:00 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

Service Incident on the Soracom Platform - Soracom Air for Cellular (Global Coverage)

Wed, 12 Aug 2026 02:42:12 +0000

2026-08-12 · 11:31 JST
Post-mortem

Summary

Between 2026-07-24 07:57 and 2026-07-24 09:32 UTC, some Soracom IoT SIM subscriptions experienced issues where new cellular communication sessions could not be established or were difficult to establish. Additionally, a subset of existing cellular communication sessions experienced intermittent disconnections and required re-establishment.

Affected Services

During this period, devices using the following subscriptions were affected:

plan01s
- Iliad（Italy）
- Kyivstar (Ukraine)
- Optus (Australia)
- Vodafone (Australia)
planP1
- Optus (Australia)
planM1
- Optus (Australia)
planV1
- Optus (Australia)
planX3
- ILIAD (Italy)
- Optus (Australia)

Cause

Resolution

Future Actions

2026-07-24 · 21:24 JST
Resolved

The following service incident occurred on the Soracom platform:

[Affected Services]
Soracom Air for Cellular IoT SIM cards on plans:

plan01s
planX3
planP1
plan-US-max
planM1
planV1

[Issues Identified]
Some SIMs from the affected plans cannot connect to the network across multiple countries and carriers. We have confirmed impacts on the following countries and carriers:

plan01s
- Iliad（Italy）
- Kyivstar (Ukraine)
- Optus (Australia)
- Vodafone (Australia)
planP1
- Optus (Australia)
planM1
- Optus (Australia)
planV1
- Optus (Australia)
plan-US-max
- Verizon (United States)
- T-Mobile (United States)
planX3
- ILIAD (Italy)
- Optus (Australia)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-07-24 07:55
Start of Recovery Trend: 2026-07-24 09:00
End of Incident: 2026-07-24 09:30

We apologize for any inconvenience this incident may have caused. If you still require assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-07-24 · 18:56 JST
Monitoring

We are currently experiencing a service incident on the Soracom platform:

[Affected Services]
Soracom Air for Cellular IoT SIM cards on plans:

plan01s
planX3
planP1
plan-US-max
planM1
planV1

[Issues Identified]
Some SIMs from the affected plans cannot connect to the network across multiple countries and carriers. We have confirmed impacts on the following countries and carriers:

plan01s
- Iliad（Italy）
- Kyivstar (Ukraine)
- Optus (Australia)
- Vodafone (Australia)
planP1
- Optus (Australia)
planM1
- Optus (Australia)
planV1
- Optus (Australia)
plan-US-max
- Verizon (United States)
- T-Mobile (United States)
planX3
- ILIAD (Italy)
- Optus (Australia)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-07-24 07:55
Start of Recovery Trend: 2026-07-24 09:00

[Current Status]
Our engineering team is observing a recovery trend and is monitoring the service as it is recovering.

[Next Update]
As soon as the situation changes or at 2026-07-24 12:00 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-07-24 · 17:41 JST
Issue

We are currently experiencing a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plan:

plan01s
planP1
planM1
planV1

[Issue Identified]
Some SIMs from the affected plan cannot connect to the network.

[Incident Timeline]
Times are in UTC:

TBD

[Current Status]
Our engineering team is actively investigating the issue.

[Next Update]
As soon as the situation changes or at 2026-07-24 10:00 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

Service Incident on the Soracom Platform - Soracom Air for Cellular (Global Coverage)

Fri, 17 Jul 2026 02:01:59 +0000

Minor incident - Air for Cellular, plan01s (Rendezvous point: Frankfurt), plan01s (Rendezvous point: Oregon), plan01s (Rendezvous point: Tokyo), plan01s (Rendezvous point: Sydney), planX1 (Rendezvous point: Frankfurt), planX1 (Rendezvous point: Oregon), planX1 (Rendezvous point: Tokyo), planP1 (Rendezvous point: Frankfurt), planP1 (Rendezvous point: Oregon), planP1 (Rendezvous point: Tokyo), planP1 (Rendezvous point: Sydney), planX2 (Rendezvous point: Tokyo), planX3 (Rendezvous point: Tokyo), planX3 (Rendezvous point: Frankfurt), planM1, planV1, planNT1, plan-US, plan-US-NA, plan-US-max, plan-NA1, planXM1 (Rendezvous point: Frankfurt), planXM1 (Rendezvous point: Oregon), planXM1 (Rendezvous point: Tokyo), Others

2026-07-17 · 10:47 JST
Retroactive

The following service incident occurred on the Soracom platform:

[Affected Services]
Soracom Air for Cellular IoT SIM cards on plans:

Global Coverage

[Issues Identified]
Some SIMs from the affected plans were unable to connect to the network.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-07-17 00:52
End of Incident: 2026-07-17 01:15

We apologize for any inconvenience this incident may have caused. If you still require assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

Service Incident on the Soracom Platform - Soracom Air for Cellular (Global Coverage)

Fri, 17 Jul 2026 02:01:59 +0000

2026-07-17 · 10:47 JST
Retroactive

The following service incident occurred on the Soracom platform:

[Affected Services]
Soracom Air for Cellular IoT SIM cards on plans:

Global Coverage

[Issues Identified]
Some SIMs from the affected plans were unable to connect to the network.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-07-17 00:52
End of Incident: 2026-07-17 01:15

We apologize for any inconvenience this incident may have caused. If you still require assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

Service Incident on the Soracom Platform - Soracom Air for Cellular (plan-K)

Wed, 8 Jul 2026 06:48:04 +0000

Minor incident - Air for Cellular, plan-K

2026-07-08 · 15:44 JST
Update

(This update includes additional information regarding the incident.)
We previously experienced a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular:

plan-K

[Issue Identified]
Some SIMs experienced difficulty using the cellular network, or were unable to connect. In addition, packet loss rates were higher than normal.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-07-07 16:44
End of Incident: 2026-07-07 17:00

[Current Status]
Service has been fully restored. Normal operations have been confirmed.

We sincerely apologize for any inconvenience this incident may have caused. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/
Thank you for your understanding and cooperation.

2026-07-08 · 04:22 JST
Retroactive

We previously experienced a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular:

plan-K

[Issue Identified]
Some SIMs experienced difficulty using the cellular network, or were unable to connect.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-07-07 16:44
End of Incident: 2026-07-07 16:56

[Current Status]
Service has been fully restored. Normal operations have been confirmed.

Service Incident on the Soracom Platform - Soracom Air for Cellular (planX3)

Thu, 2 Jul 2026 02:02:39 +0000

Minor incident - Air for Cellular, planX3 (Rendezvous point: Tokyo), planX3 (Rendezvous point: Frankfurt)

2026-06-29 · 17:00 JST
Resolved

The following service incident occurred on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plan:

planX3

[Issue Identified]
Some SIMs on the affected plan were unable to connect to the network or experienced degraded cellular connectivity.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-29 03:34
Start of Recovery Trend: 2026-06-29 06:25
End of Incident: 2026-06-29 08:00

We apologize for any inconvenience this incident may have caused. If you still require assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-06-29 · 15:49 JST
Monitoring

We are currently experiencing a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plan:

planX3

[Issue Identified]
Some SIMs on the affected plan cannot connect to the network or may experience degraded cellular connectivity.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-29 03:34
Start of Recovery Trend: 2026-06-29 06:25

[Current Status]
Our engineering team has observed a recovery trend and is continuing to monitor the service as it recovers.

[Next Update]
As soon as the situation changes or at 2026-06-29 08:00 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-06-29 · 14:58 JST
Investigating

We are currently experiencing a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plan:

planX3

[Issue Identified]
Some SIMs on the affected plan cannot connect to the network or may experience degraded cellular connectivity.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-29 03:34

[Current Status]
Our engineering team is actively investigating the issue in coordination with our network partner.

[Next Update]
As soon as the situation changes or at 2026-06-29 07:00 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-06-29 · 13:55 JST
Investigating

We are currently experiencing a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plan:

planX3

[Issue Identified]
Some SIMs from the affected plan cannot connect to the network or may experience degraded cellular connectivity.
The affected carrier is currently under investigation.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-29 03:34

[Current Status]
Our engineering team is actively investigating the issue in coordination with our network partner.

[Next Update]
As soon as the situation changes or at 2026-06-29 06:00 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-06-29 · 13:09 JST
Issue

We are currently experiencing a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plan:

planX3

[Issue Identified]
Some SIMs from the affected plan cannot connect to the network or may experience degraded cellular connectivity.
The affected carrier is currently under investigation.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-29 03:34

[Current Status]
Our engineering team is actively investigating the issue.

[Next Update]
As soon as the situation changes or at 2026-06-29 05:00 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

Service Incident on the Soracom Platform - Soracom Air for Cellular (planX3)

Sun, 28 Jun 2026 01:02:58 +0000

Minor incident - Others

2026-06-28 · 10:00 JST
Resolved

The investigation into the reported service incident on the Soracom platform has been completed.

[Investigation Results]
Following a thorough investigation by our engineering team, no issues or disruptions were identified on the Soracom platform. The service is operating normally. We have confirmed that this situation was caused by a temporary issue in our monitoring system. Going forward, we are committed to improving our monitoring systems to ensure operational accuracy.

We apologize for any confusion this matter may have caused.

If you have any questions, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-06-28 · 08:58 JST
Investigating

We are currently experiencing a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plan:

planX3

[Issue Identified]
Some SIMs from the affected plan cannot connect to the network

[Incident Timeline]
Times are in UTC:

Start of Incident: TBD

[Current Status]
Our engineering team is actively investigating the issue.

[Next Update]
As soon as the situation changes or at 2026-06-28 01:00 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

Service Incident on the Soracom Platform - Soracom Air for Cellular (planX3, planX3-EU)

Wed, 1 Jul 2026 04:12:20 +0000

Minor incident - Air for Cellular, planX3 (Rendezvous point: Frankfurt)

2026-07-01 · 13:01 JST
Post-mortem

Summary

Between 2026-06-24 02:00 and 2026-06-24 03:55 UTC, some Soracom Air SIM subscriptions experienced issues where new cellular communication sessions could not be established.

Affected Services

During this period, devices using the following subscriptions were affected:

planX3
planX3-EU

Data communication via already established cellular communication sessions was not affected.

Cause

In preparation for migrating to a new system, Soracom had been running a new system responsible for cellular session establishment alongside the original system, gradually increasing the number of sessions being hosted on the new system. When the parallel operation evaluation phase concluded, all processing was migrated to the new system prior to this incident. Following the migration, normal operations were confirmed to be functioning without issue.

However, at approximately 02:00 UTC on the same day, requests for new session connections concentrated within a short period. Cellular session establishment requests can sometimes spike rapidly due to device usage patterns or automated device reconnection behavior. A post-incident investigation revealed a defect in the new system that prolonged processing times when connection requests spiked. During the affected period, the time required to process session establishment was longer than it would have been under the original system.

Devices using these subscriptions connect to Soracom via network partner infrastructure through local Mobile Network Operator (MNO) networks. The network partner’s infrastructure enforces a timeout threshold for session establishment requests. Because the response time from Soracom’s system exceeded this timeout threshold, session establishment processing could not be completed, preventing some devices from initiating cellular communication.

Resolution

At 02:19 UTC, Soracom recognized this event as an incident and initiated its incident response framework. Upon identifying the abnormal communication status, Soracom promptly updated the Status Dashboard to notify customers, and simultaneously began an internal investigation while escalating the issue to the network partner.

Based on our investigation and responses from the network partner, the aforementioned cause was identified. At 03:44 UTC, Soracom executed a rollback of a portion of its system resources back to the original configuration. After confirming a trend toward recovery, a rollback of all remaining resources was performed, and full recovery was confirmed at 03:55 UTC.

Future Actions

We are addressing the aforementioned defect in the new system and will roll it out in phases following performance validation.

Additionally, to reduce the time required for the initial detection and identification of such incidents, we will improve our system monitoring configurations and alert settings to accurately measure and monitor response times for session establishment requests. Furthermore, we will consider adding new metrics to better evaluate the overall health of Soracom in order to improve service quality and shorten the time required from anomaly detection to recovery.

2026-06-24 · 13:59 JST
Resolved

The service incident on the Soracom platform has been fully resolved:

[Affected Services]
Soracom Air for Cellular IoT SIM cards on plans:

planX3
planX3-EU

[Issues Identified]
SIMs from all subscriptions could not connect to the network or experienced difficulty connecting.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-24 02:00
Start of Recovery Trend: 2026-06-24 03:44
Fully Resolved: 2026-06-24 05:00

[Current Status]
Following the countermeasures implemented by our engineering team, a recovery trend was observed from 03:44 UTC, and we have confirmed full recovery as of 05:00 UTC.

We sincerely apologize for any inconvenience caused. If you have any further questions, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

2026-06-24 · 13:00 JST
Monitoring

We are currently experiencing a service incident on the Soracom platform:

[Affected Services]
Soracom Air for Cellular IoT SIM cards on plans:

planX3
planX3-EU

[Issues Identified]
SIMs from all subscriptions cannot connect to the network or are experiencing difficulty connecting.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-24 02:00
Start of Recovery Trend: 2026-06-24 03:44

[Current Status]
Our engineering team has observed a recovery trend and is monitoring the service as it recovers.

[Next Update]
As soon as the situation changes or at 2026-06-24 05:00 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-06-24 · 11:40 JST
Issue

We are currently experiencing a service incident on the Soracom platform:

[Affected Services]
Soracom Air for Cellular IoT SIM cards on plans:

planX3
planX3-EU

[Issues Identified]
Some SIMs from the affected plans cannot connect to the network on the following carriers:

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-24 02:00

[Current Status]
Our engineering team is actively investigating the issue.

[Next Update]
As soon as the situation changes or at 2026-06-24 04:00 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

Service Incident on the Soracom Platform - Soracom Air for Cellular (Global Coverage)

Thu, 18 Jun 2026 16:01:29 +0000

2026-06-19 · 01:00 JST
Resolved

The following service incident occurred on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plans:

planX3
planX3-EU
plan01s

[Issue Identified]
Some SIMs from the affected plans cannot connect to the network on the following carrier:

EE (United Kingdom)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-18 12:15
Start of Recovery Trend: 2026-06-18 14:20
End of Incident: 2026-06-18 16:00

We apologize for any inconvenience this incident may have caused. If you still require assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-06-19 · 00:00 JST
Monitoring

We are currently experiencing a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plans:

planX3
planX3-EU
plan01s

[Issue Identified]
Some SIMs from the affected plans cannot connect to the network on the following carrier:

EE (United Kingdom)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-18 12:15
Start of Recovery Trend: 2026-06-18 14:20

[Current Status]
Our engineering team has observed a recovery trend and is monitoring the service as it recovers.

[Next Update]
As soon as the situation changes or at 2026-06-18 16:00 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-06-18 · 22:30 JST
Issue

We are currently experiencing a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular IoT SIM cards on plans:

planX3
planX3-EU
plan01s

[Issue Identified]
Some SIMs from the affected plans cannot connect to the network on the following carrier:

EE (United Kingdom)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-18 12:15

[Current Status]
Our engineering team is actively investigating the issue.

[Next Update]
As soon as the situation changes or at 2026-06-18 15:00 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

Service Issue on the Soracom Platform - Soracom Air for Cellular

Thu, 11 Jun 2026 01:39:12 +0000

Minor incident - Air for Cellular, plan01s (Rendezvous point: Frankfurt), plan01s (Rendezvous point: Oregon), plan01s (Rendezvous point: Tokyo), plan01s (Rendezvous point: Sydney), planX1 (Rendezvous point: Frankfurt), planX1 (Rendezvous point: Oregon), planX1 (Rendezvous point: Tokyo), planP1 (Rendezvous point: Frankfurt), planP1 (Rendezvous point: Oregon), planP1 (Rendezvous point: Tokyo), planP1 (Rendezvous point: Sydney), planX2 (Rendezvous point: Tokyo), planX3 (Rendezvous point: Frankfurt), planM1, planV1, planNT1, plan-US, plan-US-NA, plan-US-max, plan-NA1

2026-06-11 · 10:30 JST
Resolved

The following service incident occurred on the Soracom platform:

[Affected Service]
Soracom Air for Cellular (User Console and API):

All of Global Coverage subscriptions (e.g. plan01s, planX3)

[Issue Identified]
The recording of session events was delayed. There was no impact on cellular communication.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-10 01:00
Start of Recovery Trend: 2026-06-10 17:06
Fully recovered: 2026-06-11 01:36

[Current Status]
A mitigation was applied at 2026-06-10 17:06 UTC, and a recovery trend was confirmed. Subsequently, as a result of continuous monitoring by the engineering team, we have confirmed that all session events were fully recorded at 01:36 UTC.

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-06-11 · 10:00 JST
Monitoring

We are currently experiencing a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular (User Console and API):

All of Global Coverage subscriptions (e.g. plan01s, planX3)

[Issue Identified]
Session events are not being recorded.
There is no impact to cellular connectivity.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-10 01:00
Start of Recovery Trend: 2026-06-10 17:06

[Current Status]
A mitigation was applied at 2026-06-10 17:06 UTC. Our engineering team has observed a recovery trend and continues to verify the situation.
Session events that were not recorded since the start of the incident are being applied progressively.

[Next Update]
As soon as the situation changes or at 2026-06-11 03:00 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-06-11 · 02:45 JST
Monitoring

We are currently experiencing a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular (User Console and API):

All of Global Coverage subscriptions (e.g. plan01s, planX3)

[Issue Identified]
Session events are not being recorded.
There is no impact to cellular connectivity.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-10 01:00
Start of Recovery Trend: 2026-06-10 17:06

[Next Update]
As soon as the situation changes or at 2026-06-11 01:00 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-06-11 · 02:25 JST
Monitoring

We are currently experiencing a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular (User Console and API):

All of Global Coverage subscriptions (e.g. plan01s, planX3)

[Issue Identified]
Session events are not being recorded.
At this time, no impact to cellular connectivity has been confirmed.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-10 01:00
Start of Recovery Trend: 2026-06-10 17:06

[Current Status]
A mitigation was applied at 2026-06-10 17:06 UTC. Our engineering team has observed a recovery trend and continues to verify the situation.

[Next Update]
As soon as the situation changes or at 2026-06-10 18:30 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.

2026-06-11 · 02:10 JST
Issue

We are currently experiencing a service incident on the Soracom platform:

[Affected Service]
Soracom Air for Cellular (User Console and API):

All of Global Coverage subscriptions (e.g. plan01s, planX3)

[Issue Identified]
Session events are not being recorded.
At this time, no impact to cellular connectivity has been confirmed.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-10 01:00

[Current Status]
Our engineering team is actively investigating the issue.

[Next Update]
As soon as the situation changes or at 2026-06-10 17:30 UTC

We apologize for any inconvenience this may cause. If you need assistance, please contact our support team:
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.