Soracom Inc. Status - Incident History

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.

[Maintenance] Soracom Air for Cellular (Global coverage)

Thu, 4 Jun 2026 10:30:00 +0000

Scheduled maintenance - Air for Cellular, plan-US-max

2026-06-04 · 19:30 JST
Resolved

This maintenance has been concluded as planned.

2026-06-03 · 17:30 JST
Started

This maintenance is now starting as planned.

2026-06-02 · 16:30 JST
Scheduled

The following scheduled maintenance will occur on the Soracom platfrom:

[Affected Service(s)]
SORACOM Air for Cellular:

plan-US-max

[Customer Impact]
No impact

[Maintenance Timeline]
Times are in UTC:

Scheduled Start of Maintenence: 2026-06-03 08:30
Scheduled End of Maintenence: 2026-06-04 10:30

If you have any concerns or would like additional information, 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, 3 Jun 2026 09:20:11 +0000

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

2026-06-03 · 18:15 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
planM1

[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
- Swisscom (Switzerland)
- SFR (France)
- Three (United Kingdom)
- Salt (Switzerland)
- Rogers (Canada)
- Iliad (Italy)
- Optus (Australia)
- Vodafone (Australia)
planX3
- Three (United Kingdom)
- Iliad (Italy)
- WIND (Italy)
planP1
- Optus (Australia)
planM1
- Vodafone (Australia)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-03 07:47
Start of Recovery Trend: 2026-06-03 08:17
End of Incident: 2026-06-03 09:20

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-03 · 17:40 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
planM1

[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
- Swisscom (Switzerland)
- SFR (France)
- Three (United Kingdom)
- Salt (Switzerland)
- Rogers (Canada)
- Iliad (Italy)
- Optus (Australia)
- Vodafone (Australia)
planX3
- Three (United Kingdom)
- Iliad (Italy)
- WIND (Italy)
planP1
- Optus (Australia)
planM1
- Vodafone (Australia)

[Incident Timeline]
Times are in UTC:

Start of Incident: 07:47
Start of Recovery Trend: 08:17

[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-03 09: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-03 · 17:05 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

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

[Incident Timeline]
Times are in UTC:

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

[Next Update]
As soon as the situation changes or at 2026-06-03 09: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 (Japan Coverage)

Fri, 5 Jun 2026 04:04:21 +0000

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

2026-06-05 · 13:00 JST
Post-mortem

Summary

Between 2026-06-02 09:25 and 14:52 UTC, some Japan Coverage IoT SIM subscriptions experienced issues where cellular communication services were unavailable or unstable.

Affected Services

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

plan-D and plan-DU
- 2026-06-02 18:25 - 18:42 Unable to establish new cellular communication sessions
plan-K2
- 2026-06-02 18:25 - 18:42 Unable to establish new cellular communication sessions
- 2026-06-02 18:42 - 23:52 Some devices unable to maintain cellular communication sessions, difficulty sending and receiving SMS

Data communication via already established cellular communication sessions prior to the incident were not affected.

Cause

At approximately 2026-06-02 09:25 UTC, an internal operation to create new resources was executed. Because this operation had been successfully performed in the past and verified in a development environment, it was not expected to affect active production resources. However, due to a configuration discrepancy between the development and production environments, this operation caused a configuration conflict, unintentionally altering the configuration of active production resources.

The altered resources included components responsible for processing cellular communication sessions for plan-D, plan-DU, and plan-K2. As a result, new cellular communication sessions could not be established for these subscriptions.

Following the implementation of a workaround at 09:42 UTC, the ability to process new cellular communication requests was restored, and connectivity for plan-D and plan-DU recovered. However, for plan-K2, a surge of reconnection requests from devices immediately following the workaround led to a situation where some devices were unable to maintain stable sessions and experienced problems with SMS.

Resolution

After detecting the abnormal connectivity, Soracom updated the Status Dashboard and began an internal investigation.

To address the issue where new sessions could not be established for plan-D, plan-DU, and plan-K2, traffic was rerouted to healthy resources at approximately 09:42 UTC. We confirmed that session establishment began to recover from 09:42 UTC.

To address the issue where new cellular communication sessions could not be maintained and SMS messages were difficult to send and receive for plan-K2, additional measures were applied to improve the performance of the affected resources. We took several measures, resulting in a gradual improvement of the situation, and recovery was finally observed at 14:52 UTC.

Future Actions

To prevent similar issues in the future, we are implementing measures to protect production resources from unintended modifications caused by configuration conflicts. Specifically, we are reviewing privileges for the operations, improving configuration management consistency between development and production environments, and revising operational procedures.

Additionally, to improve resilience against high loads caused by surges in device reconnection requests, we will continue to implement performance improvements for the related resources.

We remain committed to continuous infrastructure improvements. To minimize the duration of impact on customer systems and devices, we will further enhance monitoring and alerting, and continue efforts to reduce response times and improve overall service quality.

2026-06-03 · 01:30 JST
Resolved

The following service incident occurred on the Soracom platform:

[Affected Service]
Soracom Air for Cellular (Japan Coverage):

plan-D
plan-DU
plan-K2

[Issue Identified]
Some SIMs were unable to establish new data sessions.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-02 09:25
Recovery Trend Observed on plan-D and plan-DU: 2026-06-02 09:45
Partial Recovery Trend Observed on plan-K2: 2026-06-02 09:45
Recovery Trend Observed on plan-K2: 2026-06-02 14:52
End of Incident: 2026-06-02 16: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-06-03 · 00:30 JST
Monitoring

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

[Affected Service]
Soracom Air for Cellular (Japan Coverage) :

plan-D
plan-DU
plan-K2

[Issue Identified]
Some SIMs were unable to establish new data sessions.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-02 09:25
Recovery Trend Observed on plan-D and plan-DU: 2026-06-02 09:45
Partial Recovery Trend Observed on plan-K2: 2026-06-02 09:45
Recovery Trend Observed on plan-K2: 2026-06-02 14:52

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

[Next Update]
As soon as the situation changes or at 2026-06-02 16: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-02 · 23:25 JST
Investigating

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

[Affected Service]
Soracom Air for Cellular (Japan Coverage):

plan-D
plan-DU
plan-K2

[Issue Identified]
Some SIMs are unable to establish new data sessions.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-02 09:25
Mitigation Applied: 2026-06-02 09:42

[Current Status]
We have confirmed that new data sessions can be established on plan-D and plan-DU. We have also confirmed that new data sessions can be established on many plan-K2 devices.
We continue to work on issues affecting connectivity and SMS send and receive functionality for a subset of plan-K2 subscriptions.

[Next Update]
As soon as the situation changes or at 2026-06-02 15: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-02 · 22:25 JST
Investigating

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

[Affected Service]
Soracom Air for Cellular (Japan Coverage):

plan-D
plan-DU
plan-K2

[Issue Identified]
Some SIMs are unable to establish new data sessions.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-02 09:25
Mitigation Applied: 2026-06-02 09:42

[Next Update]
As soon as the situation changes or at 2026-06-02 14: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-02 · 21:26 JST
Investigating

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

[Affected Service]
Soracom Air for Cellular (Japan Coverage)

[Issue Identified]
Some SIMs are unable to establish new data sessions.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-02 09:25
Mitigation Applied: 2026-06-02 09:42

[Current Status]
We have confirmed that new data sessions can be established. We continue to work on issues affecting connectivity and SMS send and receive functionality for a subset of plan-K2 subscriptions.

[Next Update]
As soon as the situation changes or at 2026-06-02 13: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-02 · 20:29 JST
Investigating

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

[Affected Service]
Soracom Air for Cellular (Japan Coverage)

[Issue Identified]
Some SIMs are unable to establish new data sessions.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-02 09:25
Mitigation Applied: 2026-06-02 09:42

[Next Update]
As soon as the situation changes or at 2026-06-02 12: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-02 · 19:45 JST
Investigating

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

[Affected Service]
Soracom Air for Cellular (Japan Coverage)

[Issue Identified]
Some SIMs are unable to establish new data sessions.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-06-02 09:25
Mitigation Applied: 2026-06-02 09:42

[Current Status]
We have confirmed that new data sessions can be established. We are aware of an issue affecting SMS send and receive functionality on plan-K2 and are continuing to work on a resolution.

[Next Update]
As soon as the situation changes or at 2026-06-02 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-06-02 · 19:05 JST
Investigating

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

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

Japan Coverage

[Issue Identified]
Some SIMs are unable to establish new data sessions.

[Incident Timeline]
TBA

[Current Status]
We have applied mitigation measures and confirmed recovery for some subscriptions. Our engineering team continues to work toward full recovery.

[Next Update]
As soon as the situation changes or at 2026-06-02 11: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-02 · 18:35 JST
Issue

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

[Affected Service]
Soracom Air for Cellular (Japan Coverage)

[Issue Identified]
Unable to establish new data sessions.

[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-02 10: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 (plan01s)

Thu, 14 May 2026 11:59:15 +0000

Minor incident - Air for Cellular, plan01s (Rendezvous point: Frankfurt), plan01s (Rendezvous point: Oregon), plan01s (Rendezvous point: Tokyo), plan01s (Rendezvous point: Sydney)

2026-05-14 · 20:37 JST
Resolved

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

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

plan01s

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

Rogers (Canada)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-05-14 05:37 UTC
Start of Recovery Trend: 2026-05-14 06:30 UTC
Monitoring the situation: 2026-05-14 11:00 UTC
Confirmed the recovery: 2026-05-14 12:00 UTC

[Current Status]
The recovery trend is sustained, and our engineering team continues to monitor the service.

[Next Update]
As soon as the situation changes or at 2026-05-15 00: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-05-14 · 19:54 JST
Monitoring

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

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

plan01s

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

Rogers (Canada)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-05-14 05:37 UTC
Start of Recovery Trend: 2026-05-14 06:30 UTC
Monitoring the situation: 2026-05-14 11:00 UTC

[Current Status]
The recovery trend is sustained, and our engineering team continues to monitor the service.

2026-05-14 · 15:56 JST
Investigating

We are currently experiencing a service incident on the Soracom platform:
[Affected Service]
Soracom Air for Cellular IoT SIM cards on plan:

plan01s
[Issue Identified]
Some SIMs from the affected plan were unable to connect to the network on the following carrier:
Rogers (Canada)
[Incident Timeline]
Times are in UTC:
Start of Incident: 2026-05-14 05:37 UTC
Start of Recovery Trend: 2026-05-14 06:30 UTC
[Current Status]
Our engineering team is observing a recovery trend and are monitoring the service as it is recovering.
[Next Update]
As soon as the situation changes or at 2026-05-14 11: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-05-14 · 14:54 JST
Issue

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

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

plan01s

[Issue Identified]
Some SIMs from the affected plan(s) cannot connect to the network on the following carrier(s):

Rogers (Canada)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-05-14 05:37 UTC

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

[Next Update]
As soon as the situation changes or at 2026-05-14 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.

Service Maintenance Announcement For Soracom Air for Cellular (planX3)

Tue, 12 May 2026 09:00:00 +0000

Scheduled maintenance - Air for Cellular, planX3 (Rendezvous point: Frankfurt)

2026-05-12 · 18:00 JST
Resolved

This maintenance has been concluded as planned.

2026-05-12 · 14:00 JST
Started

This maintenance is now starting as planned.

2026-04-07 · 17:38 JST
Postponed

The scheduled maintenance on the Soracom platform has been rescheduled.

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

planX3

[Customer Impact]
No impact

[Maintenance Timeline]
Times are in UTC:

Scheduled Start of Maintenance: 2026-05-12 05:00
Scheduled End of Maintenance: 2026-05-12 09:00

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

Thank you for your understanding and cooperation.

2026-03-24 · 16:04 JST
Scheduled

The following scheduled maintenance will occur on the Soracom platform:

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

planX3

[Customer Impact]
No impact

[Maintenance Timeline]
Times are in UTC:

Scheduled Start of Maintenance: 2026-04-14 05:00
Scheduled End of Maintenance: 2026-04-14 09:00

If you have any concerns or would like additional information, 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)

Wed, 29 Apr 2026 11:59:33 +0000

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

2026-04-29 · 20:42 JST
Resolved

The following service incident occurred on the Soracom platform:

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 connectivity, on the following carrier:

O2 (United Kingdom)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-28 09:00
Start of Recovery Trend: 2026-04-29 08:13
End of Incident: 2026-04-29 11: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-04-29 · 18:06 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 from the affected plan cannot connect to the network, or may experience degraded connectivity, on the following carriers:

O2 (United Kingdom)

[Incident Timeline]
2026/04/28 09:00 UTC Start decreasing data traffic
2026/04/28 11:28 UTC Start investigation
2026/04/28 16:00 UTC Investigating by the roaming partner
2026/04/28 19:00 UTC Investigating by the roaming partner
2026/04/28 22:00 UTC Investigating by the roaming partner
2026/04/29 01:00 UTC Investigating by the roaming partner
2026/04/29 04:00 UTC Investigating by the roaming partner
2026/04/29 07:00 UTC Investigating by the roaming partner
2026/04/29 08:13 UTC Seeing recovery trend

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

[Next Update]
As soon as the situation changes or at 2026-04-29 13: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-04-29 · 15:59 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 connectivity, on the following carriers:

O2 (United Kingdom)

[Current Status]
The roaming partner is investigating the issue

[Next Update]
As soon as the situation changes or at 2026-04-29 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.

2026-04-29 · 13:00 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 connectivity, on the following carriers:

O2 (United Kingdom)

[Current Status]
The roaming partner is investigating the issue

[Next Update]
As soon as the situation changes or at 2026-04-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-04-29 · 10:01 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 connectivity, on the following carriers:

O2 (United Kingdom)

[Current Status]
The roaming partner is investigating the issue

[Next Update]
As soon as the situation changes or at 2026-04-29 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.

2026-04-29 · 07:01 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 connectivity, on the following carriers:

O2 (United Kingdom)

[Current Status]
The roaming partner is investigating the issue

[Next Update]
As soon as the situation changes or at 2026-04-29 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-04-29 · 03:02 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 connectivity, on the following carriers:

O2 (United Kingdom)

[Incident Timeline]
2026/04/28 09:00 UTC Start decreasing data traffic
2026/04/28 11:28 UTC Start investigation
2026/04/29 16:00 UTC Investigating by the roaming partner
2026/04/29 19:00 UTC Investigating by the roaming partner

[Current Status]
The roaming partner is investigating the issue

[Next Update]
As soon as the situation changes or at 2026-04-28 22: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-04-29 · 00: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 connectivity, on the following carriers:

O2 (United Kingdom)

[Incident Timeline]
2026/04/28 09:00 UTC Start decreasing data traffic
2026/04/28 11:28 UTC Start investigation
2026/04/29 16:00 UTC Investigating by the roaming partner

[Current Status]
The roaming partner is investigating the issue

[Next Update]
As soon as the situation changes or at 2026-04-28 19: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-04-28 · 23:10 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 connectivity, on the following carriers:

O2 (United Kingdom)

[Incident Timeline]
TBD

[Current Status]
The roaming partner is investigating the issue

[Next Update]
As soon as the situation changes or at 2026-04-28 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-04-28 · 21:06 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 connectivity, on the following carriers:

O2 (United Kingdom)

[Incident Timeline]
TBD

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

[Next Update]
As soon as the situation changes or at 2026-04-28 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 (plan01s)

Wed, 29 Apr 2026 12:09:20 +0000

Minor incident - Air for Cellular, plan01s (Rendezvous point: Frankfurt), plan01s (Rendezvous point: Oregon), plan01s (Rendezvous point: Tokyo), plan01s (Rendezvous point: Sydney)

2026-04-29 · 21:02 JST
Resolved

The following service incident occurred on the Soracom platform:

Soracom Air for Cellular IoT SIM cards on plan:

plan01s

[Issue Identified]
Some SIMs from the affected plan cannot connect to the network, or may experience degraded connectivity, on the following carriers:

AIS (Thailand)
True (Thailand)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-27 18:40
Start of Recovery Trend: 2026-04-28 14:44
End of Incident: 2026-04-29 11: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-04-29 · 15:55 JST
Monitoring

We are currently seeing recovery trend of the service incident on the Soracom platform:

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

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

AIS (Thailand)
True (Thailand)

[Incident Timeline]
Times are in UTC:
Start of Incident: 2026-04-27 18:40 UTC
Investigating: 2026-04-08 14:00 UTC
Seeing recovery trend 2026-04-28 14:44 UTC

[Current Status]
The roaming partner is investigating the issue

[Next Update]
As soon as the situation changes or at 2026-04-29 13: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-04-29 · 09:59 JST
Monitoring

We are currently seeing recovery trend of the service incident on the Soracom platform:

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

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

AIS (Thailand)
True (Thailand)

[Incident Timeline]
Times are in UTC:
Start of Incident: 2026-04-27 18:40 UTC
Investigating: 2026-04-08 14:00 UTC
Seeing recovery trend 2026-04-28 14:44 UTC

[Current Status]
The roaming partner is investigating the issue

[Next Update]
As soon as the situation changes or at 2026-04-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-04-29 · 07:00 JST
Monitoring

We are currently seeing recovery trend of the service incident on the Soracom platform:

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

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

AIS (Thailand)
True (Thailand)

[Incident Timeline]
Times are in UTC:
Start of Incident: 2026-04-27 18:40 UTC
Investigating: 2026-04-08 14:00 UTC
Seeing recovery trend 2026-04-28 14:44 UTC

[Current Status]
The roaming partner is investigating the issue

[Next Update]
As soon as the situation changes or at 2026-04-29 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-04-29 · 02:58 JST
Monitoring

We are currently seeing recovery trend of the service incident on the Soracom platform:

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

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

AIS (Thailand)
True (Thailand)

[Incident Timeline]
Times are in UTC:
Start of Incident: 2026-04-27 18:40 UTC
Investigating: 2026-04-08 14:00 UTC
Seeing recovery trend 2026-04-28 14:44 UTC

[Current Status]
The roaming partner is investigating the issue

[Next Update]
As soon as the situation changes or at 2026-04-28 22: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-04-29 · 00:50 JST
Investigating

We are currently seeing partial recovery trend of the service incident on the Soracom platform but the roaming partner continue investigating

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

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

AIS (Thailand)
True (Thailand)

[Incident Timeline]
Times are in UTC:
Start of Incident: 2026-04-27 18:40 UTC
Investigating: 2026-04-08 14:00 UTC
Seeing recovery trend 2026-04-28 14:44 UTC

[Current Status]
The roaming partner is investigating the issue

[Next Update]
As soon as the situation changes or at 2026-04-28 19: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-04-28 · 23:08 JST
Investigating

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

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

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

AIS (Thailand)
True (Thailand)

[Incident Timeline]
Times are in UTC:
Start of Incident: 2026-04-27 18:40 UTC
Investigating: 2026-04-08 14:00 UTC

[Current Status]
The roaming partner is investigating the issue

[Next Update]
As soon as the situation changes or at 2026-04-28 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-04-28 · 21:02 JST
Investigating

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

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

plan01s
[Issue Identified]
Some SIMs from the affected plan are unable to connect to the network on the following carrier:
AIS (Thailand)
True (Thailand)

[Incident Timeline]
Times are in UTC:
Start of Incident: 2026-04-27 18:40 UTC
Investigating: 2026-04-08 14:00 UTC

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

[Next Update]
As soon as the situation changes or at 2026-04-28 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-04-28 · 19:15 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

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

AIS (Thailand)
True (Thailand)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-27 18:40 UTC

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

[Next Update]
As soon as the situation changes or at 2026-04-28 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.

Service Incident on the Soracom Platform - Soracom Air for satellite (plan-NT1)

Wed, 15 Apr 2026 13:05:57 +0000

Minor incident - Air for Cellular, planNT1

2026-04-15 · 22:00 JST
Resolved

We have experienced a service incident on the Soracom platform. This issue is now resolved.

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

planNT1

[Issue Identified]
All SIMs from the affected plan could not connect to the network on the following carrier:

Skylo (Global)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-15 10:36 UTC
Resolved: 2026-04-15 11:11 UTC

[Current Status]
The issue has been resolved and the service is operating normally.

We apologize for any inconvenience this 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-04-15 · 20:18 JST
Monitoring

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

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

planNT1

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

Skylo (Global)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-15 10:36 UTC
Recovery Trend Confirmed: 2026-04-15 11:11 UTC

[Current Status]
Service has been restored and we are monitoring the stability. Our engineering team has confirmed recovery for planNT1 satellite communication (VPLMN: 90198) and is currently monitoring the connection.

[Next Update]
As soon as the situation changes or at 2026-04-15 13: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-04-15 · 19:54 JST
Issue

Service Incident on the Soracom Platform - Soracom Air for Satellite (planNT1)

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

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

planNT1

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

Skylo (Global)

[Incident Timeline]
Times are in UTC:

Start of Incident: Under investigation

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

[Next Update]
As soon as the situation changes or at 2026-04-15 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.

Service Incident on the Soracom Platform - Soracom Air for Sigfox

Mon, 13 Apr 2026 09:00:32 +0000

Minor incident - Air for Sigfox, Global coverage, Japan coverage

2026-04-13 · 18:00 JST
Resolved

The following service incident occurred on the Soracom platform:

[Affected Service]

Soracom Air for Sigfox

[Issue Identified]
Parts of the uplink/downlink communications have failed or have been delayed.

We have confirmed that communication on our equipment has recovered.
Please also refer to the Sigfox Backend status below:
https://status.unabiz.com/incidents/wwf5q7fwsmzw

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-13 00:09
Start of Recovery Trend: 2026-04-13 04:18

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-04-13 · 15:10 JST
Monitoring

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

[Affected Service]

Soracom Air for Sigfox (Global coverage)

[Issue Identified]
Parts of the uplink/downlink communications have failed or have been delayed.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-13 00:09 UTC

[Current Status]
The trend towards recovery is confirmed and progress is being monitored. Please also check the status on Sigfox Backend.
https://status.unabiz.com/incidents/wwf5q7fwsmzw

[Next Update]
As soon as the situation changes or at 2026-04-13 09: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-04-13 · 13:26 JST
Monitoring

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

[Affected Service]

Soracom Air for Sigfox (Global coverage)

[Issue Identified]
Parts of the uplink/downlink communications have failed or have been delayed.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-13 00:09 UTC

[Current Status]
The trend towards recovery is confirmed and progress is being monitored. Please also check the status on Sigfox Backend.
https://status.unabiz.com/incidents/wwf5q7fwsmzw

[Next Update]
As soon as the situation changes or at 2026-04-13 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-04-13 · 11:28 JST
Investigating

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

[Affected Service]

Soracom Air for Sigfox (Global coverage)

[Issue Identified]
Parts of the uplink/downlink communications have failed or have been delayed.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-13 00:09 UTC

[Current Status]
The uplink communication has been restored. Please also check the status of the Sigfox Backend.
https://status.unabiz.com/incidents/wwf5q7fwsmzw

[Next Update]
As soon as the situation changes or at 2026-04-13 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-04-13 · 10:04 JST
Issue

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

[Affected Service]

Soracom Air for Sigfox (Global coverage)

[Issue Identified]
Parts of the uplink/downlink communications have failed or have been delayed.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-13 00:09 UTC

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

[Next Update]
As soon as the situation changes or at 2026-04-13 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.

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

Tue, 7 Apr 2026 03:57:58 +0000

Major incident - Air for Cellular, plan-D

2026-04-07 · 12:57 JST
Post-mortem

Incident Summary

Between 2026-04-03 10:22 and 15:29 UTC, devices using Japan Coverage IoT SIMs on plan-D were unable to use data communication services.

Incident Timeline

Devices using the affected subscriptions connect to Soracom via NTT docomo’s infrastructure.

Around 2026-04-03 10:10 UTC, a rapid increase was observed in session creation requests with specific unsupported conditions sent from these subscriptions to the component responsible for processing cellular communication sessions (hereafter referred to as the P-GW). The P-GW responds to such requests with rejection messages via the carrier network to IoT devices.

As the volume of these requests significantly exceeded normal levels, the P-GW entered an unstable state. As a result, from around 10:22 UTC, the P-GW became unable to properly process cellular connection requests and data packets.
The P-GW is configured with redundancy, auto scale-out capabilities, and automatic process recovery mechanisms. However, due to the conditions described above, sufficient performance to sustain normal processing could not be maintained, ultimately resulting in data communication becoming unavailable for the affected subscriptions.

An alert triggered by a sharp decrease in data traffic initiated an investigation by our engineering team at 10:33 UTC, and an incident response structure was established. In parallel, customer notifications were issued via the Status Dashboard, and coordination with NTT docomo was initiated.

Based on the investigation results, a workaround was applied to a subset of P-GW instances at 12:18 UTC, and improvements in connectivity and data communication were confirmed. The workaround was then deployed across all P-GW instances, and recovery of connectivity was confirmed from approximately 12:54 UTC. Additional measures continued to be applied, and the incident was declared resolved at 15:29 UTC.

This incident did not affect Japan Coverage IoT SIMs other than plan-D, nor Global Coverage IoT SIMs.

Root Cause

Session creation requests with specific unsupported conditions directed to the P-GW had been observed under normal conditions prior to this incident. However, no performance issues had been identified under the request volumes observed before the incident occurred.
The investigation confirmed that the volume of such requests increased significantly around the time of the incident. Furthermore, the applied workaround, which included improvements to the handling of these requests, was effective.

Based on these findings, we concluded that the incident was caused by an abnormal request pattern exposing a latent issue within a P-GW component related to the processing of these requests, which led to degraded performance.

Future Actions

The latent performance issue related to handling session establishment requests containing specific unsupported conditions has been mitigated through the applied workaround, and we have identified the component that caused the issue.
We will continue to assess other subscription-related infrastructure and apply similar workarounds where necessary.

2026-04-04 · 01:56 JST
Resolved

The following service incident occurred on the Soracom platform:

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

plan-D

[Issue Identified]
All SIMs on the affected plan were unable to use data communication

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-03 10:20
Start of Recovery Trend: 2026-04-03 12:20
End of Incident: 2026-04-03 15:29

We will confirm the situation and provide further details on this page during the week of April 6, 2026.

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-04-04 · 00:55 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-D

[Issue Identified]
All SIMs on the affected plan are unable to use data communication

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-03 10:20
Start of Recovery Trend: 2026-04-03 12:20

[Current Status]
Our engineering team is addressing impacts affecting some use cases and continues to monitor the service.

[Next Update]
As soon as the situation changes or at 2026-04-03 17: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-04-03 · 23:58 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-D

[Issue Identified]
All SIMs on the affected plan are unable to use data communication

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-03 10:20
Start of Recovery Trend: 2026-04-03 12:20

[Current Status]
Our engineering team is addressing impacts affecting some use cases and continues to monitor the service.

[Next Update]
As soon as the situation changes or at 2026-04-03 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-04-03 · 22:40 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-D

[Issue Identified]
All SIMs on the affected plan are unable to use data communication

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-03 10:20
Start of Recovery Trend: 2026-04-03 12:20

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

[Next Update]
As soon as the situation changes or at 2026-04-03 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-04-03 · 22:00 JST
Investigating

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

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

plan-D

[Issue Identified]
All SIMs on the affected plan are unable to use data communication

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-03 10:20
Start of Recovery Trend: 2026-04-03 12:20

[Current Status]
Our engineering team has observed a partial recovery trend and continues to work on resolving the issue.

[Next Update]
As soon as the situation changes or at 2026-04-03 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.

2026-04-03 · 21:19 JST
Investigating

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

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

plan-D

[Issue Identified]
All SIMs on the affected plan are unable to use data communication

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-03 10:20 UTC

[Current Status]
Our engineering team is working in coordination with NTT Docomo to resolve the issue.

[Next Update]
As soon as the situation changes or at 2026-04-03 13: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-04-03 · 20:20 JST
Investigating

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

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

plan-D

[Issue Identified]
Some SIMs on the affected plan are unable to use data communication.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-04-03 10:20 UTC

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

[Next Update]
As soon as the situation changes or at 2026-04-03 12: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-04-03 · 19:43 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-D

[Issue Identified]
Some SIMs on the affected plan are unable to use data communication.

[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-04-03 11: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.