Soracom Inc. Status - Incident History

Service Maintenance Announcement For Soracom Air for Cellular (planX3)

Tue, 7 Apr 2026 08:43:42 +0000

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

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 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.

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-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.

Service Maintenance Announcement For Soracom Air for Cellular (plan-US)

Thu, 12 Mar 2026 10:00:00 +0000

Scheduled maintenance - Air for Cellular, plan-US

2026-03-12 · 19:00 JST
Resolved

This maintenance has been concluded as planned.

2026-03-12 · 13:00 JST
Started

This maintenance is now starting as planned.

2026-03-06 · 12:19 JST
Scheduled

The following scheduled maintenance will occur on the Soracom platfrom:

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

plan-US

[Customer Impact]
No impact

[Maintenance Timeline]
Times are in UTC:

Scheduled Start of Maintenence: 2026-03-12 04:00
Scheduled End of Maintenence: 2026-03-12 10: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 (plan01s)

Thu, 19 Mar 2026 03:14:52 +0000

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

2026-03-19 · 12:15 JST
Post-mortem

We are updating our previous announcement to include information regarding the cause of this incident, following a report received from the network provider.

Summary

From 2026-03-10 14:52 to 2026-03-10 23:32 UTC, some Soracom IoT SIM subscriptions experienced issues on the Telstra (Australia) network where new cellular communication sessions could not be established.

Affected Services

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

plan01s
plan01s - Low Data Volume

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

Cause

Devices using these subscriptions connect to Soracom via network partner infrastructure through local mobile network operator (MNO) networks.

In relation to this incident, the network provider reported that the issue originated from a connection failure between the network provider and Telstra.

Resolution

After detecting the abnormal connectivity, Soracom updated the Status Dashboard, began an internal investigation, and escalated the issue to the network provider.

Following the network provider’s corrective actions to resolve the issue on their side, we confirmed that connectivity began to recover around 2026-03-10 23:32 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.
We will also continue to improve our customer communication approach.

2026-03-11 · 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 - Low Data Volume

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

Telstra (Australia)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-03-10 15:00
Start of Recovery Trend: 2026-03-10 23:32
End of Incident: 2026-03-11 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-03-11 · 08:57 JST
Monitoring

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

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

plan01s
plan01s - Low Data Volume

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

Telstra (Australia)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-03-10 15:00 UTC
Start of Recovery Trend: 2026-03-10 23:32

[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-03-11 02: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-03-11 · 07: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(s):

plan01s
plan01s - Low Data Volume

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

Telstra (Australia)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-03-10 15:00 UTC

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

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

2026-03-11 · 05: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(s):

plan01s
plan01s - Low Data Volume

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

Telstra (Australia)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-03-10 15:00 UTC

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

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

2026-03-11 · 03: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(s):

plan01s
plan01s - Low Data Volume

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

Telstra (Australia)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-03-10 15:00 UTC

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

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

2026-03-11 · 01:30 JST
Investigating

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

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

plan01s
plan01s - Low Data Volume

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

Telstra (Australia)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-03-10 15:00 UTC

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

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

2026-03-11 · 00:29 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 cannot create new connections to the network on the following carrier:

Telstra (Australia)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-03-10 15:00 UTC

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

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

[Maintenance] SORACOM Air for Cellular (plan-US)

Thu, 5 Mar 2026 10:00:00 +0000

Scheduled maintenance - Air for Cellular, plan-US

2026-03-05 · 19:00 JST
Resolved

This maintenance has been concluded as planned.

2026-03-05 · 13:00 JST
Started

This maintenance is now starting as planned.

2026-03-02 · 13:06 JST
Scheduled

SORACOM Air for Cellular will undergo maintenance on the following schedule.

[Affected Services]
SORACOM Air for Cellular (plan-US)

[Maintenance Period]
Around 2026-03-05 04:00 - 10:00 UTC

[Impact]
There will be no impact on the service.

If you have any concerns or would like additional information, please contact the Soracom support team at your earliest convenience.

Thank you for your understanding and cooperation.

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

Wed, 25 Feb 2026 10:30:38 +0000

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

2026-02-25 · 19:26 JST
Resolved

The following service incident occurred on the Soracom platform:

Soracom Air for Cellular IoT SIM cards on plan(s):

plan01s
plan01s - Low Data Volume

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

EE (United Kingdom)
Orange (France)
NTT Docomo (Japan)
Orange (Slovakia)
Orange (Poland)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-02-25 08:30
Start of Recovery Trend: 2026-02-25 09:50
End of Incident: 2026-02-25 10: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-02-25 · 19:16 JST
Monitoring

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

Soracom Air for Cellular IoT SIM cards on plan(s):

• plan01s
• plan01s - Low Data Volume

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

EE (United Kingdom)
Orange (France)
NTT Docomo (Japan)
Orange (Slovakia)
Orange (Poland)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-02-25 08:30
Start of Recovery Trend: 2026-02-25 09:50 UTC

[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-02-25 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-02-25 · 18:32 JST
Investigating

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

Soracom Air for Cellular IoT SIM cards on plan(s):

plan01s
plan01s - Low Data Volume

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

EE (United Kingdom)
Orange (France)
NTT Docomo (Japan)
Orange (Slovakia)
Orange (Poland)

[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-02-25 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-02-25 · 18:07 JST
Investigating

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

Soracom Air for Cellular IoT SIM cards on plan(s):

plan01s
plan01s - Low Data Volume

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

EE (United Kingdom)
Orange (France)
NTT Docomo (Japan)

[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-02-25 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.

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

Wed, 25 Feb 2026 03:01:25 +0000

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

2026-02-25 · 12:00 JST
Resolved

The following service incident occurred on the Soracom platform:

Soracom Air for Cellular IoT SIM cards on plan(s):

plan01s
planX3

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

Vodafone (Germany)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-02-25 00:09
Start of Recovery Trend: 2026-02-25 02:10
End of Incident: 2026-02-25 02:40

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-02-25 · 11:35 JST
Monitoring

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

Soracom Air for Cellular IoT SIM cards on plan(s):

plan01s
planX3

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

Vodafone (Germany)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-02-25 00:09
Start of Recovery Trend: 2026-02-25 02:10

[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-02-25 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-02-25 · 10:02 JST
Investigating

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

Soracom Air for Cellular IoT SIM cards on plan(s):

plan01s
planX3

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

Vodafone (Germany)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-02-25 00:09 UTC

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

[Next Update]
As soon as the situation changes or at 2026-02-25 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 (plan01s, planX1, planX3)

Tue, 3 Feb 2026 08:34:36 +0000

Major 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), planX3 (Rendezvous point: Frankfurt)

2026-02-03 · 17:19 JST
Resolved

The following service incident occurred on the Soracom platform:

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

plan01s
planX1
planX3

[Issues Identified]

Some SIMs from the affected plans cannot connect to the network on the following carriers:

NTT Docomo (Japan)
SoftBank (Japan)

[Incident Timeline]

Start of Incident: 2026-02-03 06:40
Start of Recovery Trend: 2026-02-03 07:40
End of Incident: 2026-02-03 08:21

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-02-03 · 16:13 JST
Issue

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

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

plan01s
planX1
planX3

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

NTT Docomo (Japan)
SoftBank (Japan)

[Incident Timeline]
TBD

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

[Next Update]
As soon as the situation changes or at 2026-02-03 08: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, planX1, planX3)

Fri, 23 Jan 2026 22:58:44 +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), planX3 (Rendezvous point: Frankfurt)

2026-01-24 · 07:56 JST
Resolved

The following service incident occurred on the Soracom platform:

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

plan01s
planX1
planX3

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

NTT Docomo (Japan)
SoftBank (Japan)

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-01-23 19:25
Start of Recovery Trend: 2026-01-23 21:31
End of Incident: 2026-01-23 22: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-01-24 · 07:03 JST
Monitoring

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

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

planX3

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

NTT Docomo (Japan)
SoftBank (Japan)

[Incident Timeline]
TBD

[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-01-23 23: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-01-24 · 05:33 JST
Investigating

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

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

planX3

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

NTT Docomo (Japan)
SoftBank (Japan)

[Incident Timeline]
TBD

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

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

Service Incident on the Soracom Platform - VPG Type-F2

Fri, 20 Feb 2026 02:47:39 +0000

Minor incident - Virtual Private Gateway, Japan coverage

2026-02-20 · 11:45 JST
Resolved

The following service incident occurred on the Soracom platform:

[Affected Service]

Virtual Private Gateway Type-F2

[Issue(s) Identified]
Inability to create new Virtual Private Gateway Type-F2 instances.
There was no confirmed impact on existing Virtual Private Gateways.

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-02-06 · 14:58 JST
Update

[Affected Service]

Virtual Private Gateway Type-F2 (Japan coverage)

[Issue Identified]
Inability to create new Virtual Private Gateway Type-F2 instances for Japan coverage.
At this time, there is no confirmed impact on existing Virtual Private Gateways.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-01-23 (TBD)

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

[Next Update]
As soon as the situation changes

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-01-30 · 11:53 JST
Update

[Affected Service]

Virtual Private Gateway Type-F2 (Japan coverage)

[Issue Identified]
Inability to create new Virtual Private Gateway Type-F2 instances for Japan coverage.
At this time, there is no confirmed impact on existing Virtual Private Gateways.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-01-23 (TBD)

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

[Next Update]
As soon as the situation changes

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-01-27 · 11:11 JST
Investigating

[Affected Service]

Virtual Private Gateway Type-F2 (Japan coverage)

[Issue Identified]
Inability to create new Virtual Private Gateway Type-F2 instances for Japan coverage.
At this time, there is no confirmed impact on existing Virtual Private Gateways.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-01-23 (TBD)

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

[Next Update]
As soon as the situation changes

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-01-26 · 11:13 JST
Investigating

[Affected Service]

Virtual Private Gateway Type-F2 (Japan coverage)

[Issue Identified]
Inability to create new Virtual Private Gateway Type-F2 instances for Japan coverage.
At this time, there is no confirmed impact on existing Virtual Private Gateways.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-01-23 (TBD)

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

[Next Update]
As soon as the situation changes

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-01-23 · 21:11 JST
Investigating

[Affected Service]

• Virtual Private Gateway Type-F2 (Japan coverage)

[Issue Identified]
Inability to create new Virtual Private Gateway Type-F2 instances for Japan coverage.

At this time, there is no confirmed impact on existing Virtual Private Gateways.

[Incident Timeline]
Times are in UTC:

• Start of Incident: 2026-01-23 (TBD)

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

[Next Update]
As soon as the situation changes

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-01-23 · 18:47 JST
Issue

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

[Affected Service]

Virtual Private Gateway Type-F2 (Japan coverage)

[Issue Identified]
Inability to newly create Virtual Private Gateway Type-F2 in the Japan coverage.

There is currently no confirmed impact on existing Virtual Private Gateways.

[Incident Timeline]
Times are in UTC:

Start of Incident: 2026-01-23 (TBD)

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

[Next Update]
As soon as the situation changes.

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 (plan-US)

Thu, 22 Jan 2026 01:00:00 +0000

Scheduled maintenance - Air for Cellular, plan-US

2026-01-22 · 10:00 JST
Resolved

This maintenance has been concluded as planned.

2026-01-16 · 18:03 JST
Scheduled

SORACOM Air for Cellular will undergo maintenance on the following schedule.

[Affected Services]
SORACOM Air for Cellular (plan-US)

[Maintenance Period]
Around 2026-01-21 00:00 - 09:00 UTC

[Impact]
There will be no impact on the service.

If you have any concerns or would like additional information, please contact the Soracom support team at your earliest convenience.

Thank you for your understanding and cooperation.

Maintainance of Soracom Air for Cellular and Soracom Arc

Fri, 6 Feb 2026 09:00:00 +0000

Scheduled maintenance - 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, plan-D, plan-K, plan-K2, plan-DU, plan-KM1, plan-MC, Others, Arc, Global coverage (Rendezvous point: Frankfurt), Global coverage (Rendezvous point: Oregon), Global coverage (Rendezvous point: Tokyo), Global coverage (Rendezvous point: Sydney), Japan coverage

2026-02-06 · 18:00 JST
Resolved

This maintenance has been concluded as planned.

2026-01-12 · 10:00 JST
Started

This maintenance is now starting as planned.

2025-12-19 · 14:08 JST
Scheduled

Soracom Air for Cellular and Soracom Arc will undergo maintenance according to the following schedule.

[Maintenance Period]
January 12, 2026 – February 6, 2026

Maintenance will be performed daily between 01:00 and 09:00 (UTC) during this period.

[Affected Services]
This maintenance applies to IoT SIMs (Soracom Air) and Virtual SIMs/Subscribers (Soracom Arc) that meet all of the following conditions:

Not using a Virtual Private Gateway (VPG)
The session has been continuously online for 14 days or longer

[Impact]
During the maintenance window, sessions matching the criteria above will be disconnected a single time.

Soracom Air for Cellular: Most devices will automatically re-establish the connection after the session is disconnected. If your device does not reconnect automatically, please reboot the device or manually reconnect.
Soracom Arc: Sessions will not automatically reconnect. You must manually reconnect by following the steps in “Resetting a Session“ below.

To prevent a forced disconnection during the maintenance window, you may voluntarily reset your session beforehand (e.g., by rebooting the device or deleting the session via the User Console). This will exclude the device from any forced disconnections during the maintenance period.

If you have any questions or require further information, please contact the Soracom Support team.
https://developers.soracom.io/en/docs/account/support/

Thank you for your understanding and cooperation.