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

We are excited to announce two new downlink APIs, Sim:sendDownlinkHttp and Sim:sendDownlinkSsh, which allow you to send data and commands to IoT SIM devices through the Soracom API.

Traditionally, sending cloud-to-device data or commands via IP communication has been difficult due to firewall and routing restrictions that require complicated network configurations or device-side applications.

These new APIs allow you to create HTTP/HTTPS requests or SSH connections directly to your device from within Soracom, and removes the need to set up advanced network architecture, keep track of device IP addresses, or implement custom device-side logic. Simply call the downlink API specifying the data or commands to send, and Soracom will create the request or connection and return any response or output from the device back as the response of the API call.

These APIs are especially beneficial to battery-powered or legacy embedded devices with resource contraints. When combined with Soracom Flux, calling these APIs can even be automated in order to easily build sophisticated IoT systems, such as sending commands to devices based on detected sensor data or cloud events.

Please note: Pricing for Sim:sendDownlinkHttp and Sim:sendDownlinkSsh APIs is scheduled to be announced in June 2025. Until then, these APIs are free to use.

For a detailed usage guide, please see the Downlink API documentation.

We are pleased to introduce Default Variables and improved Query functionality in Soracom Lagoon 3 to reduce manual work when creating dashboards and to visualize and manage data more efficiently.

Default Variables

Default Variables allow a viewer to easily change the devices and data series displayed in the panels of a dashboard, or to automatically repeat displayed panels for multiple devices. When you create a new dashboard, the following Default Variables will now be created automatically:

• resource_types: The resource type to display, such as Air, Sigfox, Inventory Device, etc.
• groups: The Soracom groups to display from the selected resource type (such as data from Air resources in a specific group)
• resources: The specific resources to display from the selected resource type and groups (such as data from a specific IoT SIM)
• properties: The data series to display

For more information, see the Soracom Lagoon: Variables documentation.

Query Editor

The Query editor now provides a Group option that allows you to easily select multiple resources that belong to a particular Soracom group. We have also redesigned the Query editor interface to make each field clearer and less confusing when configuring a query.

For more information, see the Soracom Lagoon: Query documentation.

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

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.

A new action, Weather Forecast (Japanese) is now available in Soracom Flux.

The Weather Forecast action provides the ability to retrieve weather forecasts based on location information, and to send the forecast to a specified channel. This action is based on the 1 km mesh pinpoint weather forecast (Japanese) provided by WeatherNews (Japanese).

For example, this action can be combined with road surface temperature sensors to obtain localized snowfall and rainfall forecasts and automate the management of construction sites, or with soil moisture sensors to optimize water management in agricultural applications.

The Weather Forecast action is only available in Japan Coverage, and forecasts can only be obtained for locations in Japan.

Using the Weather Forecast action consumes 50 credits per request. Please refer to the Check Credits documentation for information on how to check your remaining credits.

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.

Soracom Beam now supports sending client certificates during the TLS/SSL handshake when sending data to a destination server via HTTPS. This update improves the security of HTTPS by enabling devices to authenticate their identity to the destination server using customer-specified certificates.

While Soracom Beam has supported client certificates for MQTTS connections, it was previously not possible to do the same for HTTPS connections. Instead, client certificates had to be managed directly on a device, increasing the complexity of device implementation and certificate management across large numbers of devices.

Now, client certificates can be specified in Soracom Beam. Devices only need to send data to a Soracom Beam entry point using a lightweight protocol like HTTP or TCP, and in turn Soracom Beam will handle the TLS/SSL handshake using the specified client certificate on behalf of the device. This simplifies certificate management, reduces operational overhead, and allows you to focus more on developing critical features.

The following entry points now support client certificate authentication:

• HTTP to HTTPS Entry Point
• Website Entry Point (*)
• TCP to HTTPS Entry Point
• UDP to HTTPS Entry Point

This feature is also available when using Soracom Beam via the Unified Endpoint.

* Website Entry Point is not supported with Unified Endpoint.

For detailed configuration instructions, please refer to the documentation for each Soracom Beam entry point listed above.

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

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.