We are pleased to announce the following user interface improvements for Soracom Napter:

New Visual Explanation of the TLS Option

When creating an On-demand Remote Access session from the User Console, a new diagram will show the connection between the device and Napter, and the connection between Napter and the client. This diagram will update according to your TLS Option selection, allowing you to visually understand how the connection will be established:

View On-demand Remote Access Session Remaining Time

When viewing the list of On-demand Remote Access sessions, each session now displays the remaining time, allowing you to more easily check how much time is left before the session expires.

To check the originally requested session duration, simply hover your mouse over the [i] icon.

For more information, please refer to the Napter: Usage documentation.

We are pleased to announce that math functions can now be used in Soracom Flux expressions, such as in the execution condition of a Flux Action as well as in some input fields. These functions include trigonometric and logarithm functions, allowing for more complex calculations when building Flux applications.

For more information, please refer to the Use Expressions in Actions documentation.

Starting April 10, 2025, customers using invoice payments will have the option to change their payment due date from “month-end closing, next month-end payment (NET30)” to “month-end closing, payment end of month after next (NET60)”.

This change will apply to invoices issued for the April 2025 billing cycle onward.

Please note that a handling fee of 550 JPY (tax included) will be added per invoice when the due date is changed to NET60.

For details on how to switch to invoice payments or change the payment due date, please refer to the following guide: Update Invoice Information Issued by Net Protections (Japanese).

We are pleased to announce that the extension of the maximum Keep-Alive timeout for Soracom's HTTP entry points to 65 seconds will be rolled out starting from April 7, 2025.

As previously mentioned, by specifying Connection: keep-alive in the HTTP request header, devices using Soracom Air for Cellular and Soracom Arc can reuse TCP connections and reduce data usage due to reconnections when sending additional HTTP requests. With this change, if devices send HTTP requests to these entry points at intervals of less than 65 seconds, the connection will be maintained, and data usage will be reduced. Previously, the Keep-Alive timeout was set to 5 seconds.

Affected Entry Points

• Soracom Beam HTTP Entry Point
• Soracom Beam Website Entry Point
• Soracom Funk HTTP Entry Point
• Soracom Funnel HTTP Entry Point
• Soracom Harvest Data/Files HTTP Entry Point
• Unified Endpoint HTTP Entry Point

Implementation Date

April 7, 2025

This specification change will be reflected gradually after the implementation date.

Required Actions

If your device cannot support the extended Keep-Alive timeout, you can specify Connection: close in the HTTP request header to disable the Keep-Alive timeout.

If you have any questions or concerns, please feel free to contact the Soracom support team.

We are pleased to announce the following coverage updates for Soracom Air for Cellular connectivity.

plan01s and plan01s-LDV

Country	Network	Before	After	Remarks
Albania	Telekom.al	2G, 3G	2G, 3G, 4G (LTE)	4G (LTE) open
Bahamas	BTC	2G, 3G	3G	2G sunset
Brunei	DST	3G	3G, 4G (LTE)	4G (LTE) open
Congo (Republic)	Airtel	-	2G, 3G, 4G (LTE)	Network open
Egypt	Etisalat	-	2G, 3G, 4G (LTE)	Network open (*1)
Estonia	Elisa	2G, 3G, 4G (LTE)	2G, 4G (LTE)	3G sunset
Germany	O2	2G, 4G (LTE)	2G, 4G (LTE), LTE Cat.M1, NB-IoT	LTE Cat.M1, NB-IoT open
Hong Kong	3	-	3G	Network open
Hong Kong	CSL	2G, 3G, 4G (LTE)	3G, 4G (LTE)	2G sunset
Ireland	Vodafone	2G, 3G, 4G (LTE)	2G, 4G (LTE)	3G sunset
Macau	3	-	3G	Network open (*1)
Malaysia	Digi	2G	2G, 4G (LTE)	4G (LTE) open
Mayotte	SFR	-	2G, 3G, 4G (LTE)	Network open
Mexico	AT&T	2G, 3G, 4G (LTE)	3G, 4G (LTE)	2G sunset
Mexico	Movistar	3G, 4G (LTE)	3G, 4G (LTE), LTE Cat.M1	LTE Cat.M1 open
Nigeria	MTN	2G, 3G	2G, 3G, 4G (LTE)	4G (LTE) open (*1)
Pakistan	Jazz	2G, 3G	2G	3G sunset
Philippines	Globe	2G, 3G	2G, 3G, 4G (LTE)	4G (LTE) open
Poland	Orange	2G, 3G, 4G (LTE)	2G, 3G, 4G (LTE), LTE Cat.M1	LTE Cat.M1 open
Portugal	MEO	2G, 3G, 4G (LTE)	2G, 4G (LTE)	3G sunset
Portugal	NOS	2G, 3G	2G	3G sunset
Portugal	Vodafone	2G, 3G, 4G (LTE)	2G, 4G (LTE), LTE Cat.M1	3G sunset, LTE Cat.M1 open
Singapore	StarHub	3G, 4G (LTE)	4G (LTE)	3G sunset
Spain	Movistar	2G, 3G, 4G (LTE), LTE Cat.M1	2G, 3G, 4G (LTE), LTE Cat.M1, NB-IoT	NB-IoT open
United Kingdom	3	3G, 4G (LTE)	4G (LTE)	3G sunset
United Kingdom	Vodafone	2G, 4G (LTE)	2G, 4G (LTE), LTE Cat.M1	LTE Cat.M1 open
Vietnam	VietnaMobile	2G, 3G	3G	2G sunset
Vietnam	Viettel	2G, 4G (LTE)	4G (LTE)	2G sunset
Vietnam	Vinaphone	2G, 3G, 4G (LTE)	3G, 4G (LTE)	2G sunset

(*1) plan01s only

planP1

Country	Networks	Before	After	Remarks
China	China Unicom	2G, 3G, 4G (LTE)	3G, 4G (LTE)	2G sunset
Germany	Vodafone	-	2G, 4G (LTE)	Network open
Hong Kong	CSL	2G, 3G, 4G (LTE)	3G, 4G (LTE)	2G sunset
Ireland	Vodafone	-	2G, 4G (LTE)	Network open
Macau	CTM	2G, 3G, 4G (LTE)	3G, 4G (LTE)	2G sunset
Mexico	AT&T	2G, 3G, 4G (LTE)	3G, 4G (LTE)	2G sunset
Pakistan	Jazz	3G, 4G (LTE)	2G, 4G (LTE)	correction
Portugal	Vodafone	2G, 3G, 4G (LTE)	2G, 4G (LTE)	3G sunset
Singapore	StarHub	3G, 4G (LTE)	4G (LTE)	3G sunset
Slovakia	Orange	2G, 3G, 4G (LTE)	2G, 4G (LTE)	3G sunset
Thailand	TrueMove H	3G, 4G (LTE)	2G, 3G, 4G (LTE)	2G open
United Kingdom	3	3G, 4G (LTE)	4G (LTE)	3G sunset
Vietnam	Mobifone	2G, 3G, 4G (LTE)	3G, 4G (LTE)	2G sunset
Vietnam	VietnaMobile	2G, 3G, 4G (LTE)	3G, 4G (LTE)	2G sunset

Soracom is expanding its support for IPv6. As part of this effort, starting March 20, 2025, you will be able to access the Soracom API using IPv6.

• If explicitly specified, you will be able to use the Soracom API with IPv6. If not specified, you can continue using the API with IPv4 as before.
• When accessed via IPv6, audit logs will record the IPv6 address.
• Soracom Napter does not support specifying an IPv6 address in the source IP address range, meaning it cannot be used with IPv6.

Scheduled Change Date

March 20, 2025

If you have any questions, please contact Soracom Support.

Soracom Access Management (SAM) permissions can be configured to allow or deny access based on IP addresses, both in SAM User permission statements and Switch User trust policy statements. IP addresses are specified using the sourceIp variable and the ipAddress function.

With this update, the sourceIp variable and the ipAddress function now support IPv6 addresses. This means that, in addition to IPv4 addresses, you can now also manage access using IPv6 addresses when configuring SAM User permissions and Switch User trust policies.

Important Considerations When Denying Access by IPv4 Address

Please note that if you have configured a rule to deny access based on an IPv4 address such as in the permission statement example below, the deny rule will only be enforced for IPv4 addresses and a user will be able to bypass the rule by accessing using an IPv6 address.

{
  "statements": [
    {
      "effect": "allow",
      "api": [
        "Sim:*",
        "Group:*"
      ]
    },
    {
      "effect": "deny",
      "api": [
        "Sim:*",
        "Group:*"
      ],
      "condition": "ipAddress('xxx.xxx.xxx.xxx/24')"
    }
  ]
}

In general, we do not recommend denying access based on IPv4 or IPv6 addresses, since a user can easily change their IP addresses and bypass restrictions.

Instead, we recommend configuring access to explicitly allow specific IP addresses or IP address ranges that you own or control, as shown in the following example:

{
  "statements": [
    {
      "effect": "allow",
      "api": [
        "Sim:*",
        "Group:*"
      ],
      "condition": "ipAddress('yyy.yyy.yyy.yyy/24')"
    }
  ]
}

If you have any questions, please feel free to contact Soracom Support.

We are pleased to announce that planX2, planX3, and plan-US subscription plans are now available as eSIM profiles.

Customers using devices that have an existing compatible eSIM can purchase eSIM profiles directly from the User Console (as well as Soracom API and CLI) and immediately install them in order to add Soracom Air connectivity, without needing to purchase and install a physical SIM card.

Subscriptions

• planX2: Available for purchase in all regions.
• planX3: Available for purchase for customers located in the European Union and United Kingdom.
• plan-US: Available for purchase for customers located in the United States and Canada.

Coverage information for each of these subscriptions is available in the Supported Carriers documentation.

Ordering eSIM Profiles

To help protect customer accounts, the eSIM Profile service is disabled by default. If you would like to use the eSIM Profile service, please contact your sales representative or contact us to opt-in.

Once the eSIM Profile service has been enabled for your account, please refer to the eSIM Profiles documentation for instructions on purchasing and installing profiles, as well as device requirements and limitations.

For pricing information, refer to the Pricing & Fee Schedule.

We are excited to announce that the Soracom Flux Webhook action now allows the use of credentials stored in the Credential Store to add Authorization headers.

Previously, while it was possible to add Authorization headers in the Webhook action, it was limited to fixed token authentication methods, which posed challenges in terms of security and flexibility. With this new feature, you can now dynamically generate Authorization headers, enabling you to authenticate with your servers or cloud services more securely. This enhancement significantly improves the flexibility and security of your automated workflows.

Key Improvements

• Dynamic Token Generation: You can now send Webhooks to services that require dynamic authentication tokens that change with each request, such as AWS Signature V4.
• Enhanced Security: By utilizing the Credential Store, sensitive credentials are not exposed in the Soracom User Console, reducing the risk of leaking credentials.

Available Authentication Schemes

The following authentication methods can now be used to add Authorization headers in the Webhook action:

AWS Signature Version 4

Generate an Authorization header in the AWS Signature Version 4 format, along with the specified AWS service and region.

• Supported Credentials: AWS credentials, AWS IAM Role credentials

Basic Authentication

Generate a value based on the username and password and add an Authorization: Basic ${value} header to the request.

• Supported Credentials: Username and passsword credentials

Bearer Token

Use a value stored in the Credential Store directly to add an Authorization: Bearer ${Token} header to the request.

• Supported Credentials: API Token credentials, Pre-Shared Key

Bearer Token (JWT)

Generate a JSON Web Token (JWT) based on the information stored in the Credential Store and add an Authorization: Bearer ${Token} header to the request.

• Supported Credentials: Google Service Account (JSON), Private Key (PEM)

Usage

For detailed instructions on how to utilize this feature, please refer to the following resources:

• Webhook Action
• Publish Data to AWS IoT with Webhook Action and AWS Signature V4 Authentication

If you have any questions or concerns, please feel free to contact Soracom Support.

We would like to inform customers of the following coverage changes for Soracom Air for Cellular connectivity.

planX3

2G, 3G, 4G (LTE) updates

Country	Network	Before	After	Remarks
Saudi Arabia	Zain	-	2G, 3G, 4G (LTE)	Network open
Saudi Arabia	STC	2G, 4G (LTE)	-	Network shutdown

For complete details about data rates, supported carriers and radio types, and coverage in other countries, please refer to the Supported Carriers documentation.