We would like to announce the following coverage updates for Soracom Air for Cellular global coverage connectivity.

plan01s and plan01s - Low Data Volume

Country	Networks	Before	Change	After
Denmark	TDC	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Denmark	Telia	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Hungary	Telekom.hu	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Hungary	Vodafone	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Luxembourg	Post	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Puerto Rico	AT&T	3G, 4G/LTE	Network shutdown	-
Puerto Rico	T-Mobile	-	New coverage	2G, 4G/LTE
Romania	Digi Mobile	3G, 4G/LTE	3G sunset	4G/LTE
Slovenia	A1	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Switzerland	Sunrise	2G, 3G, 4G/LTE	2G sunset	3G, 4G/LTE
US Virgin Islands	AT&T	3G, 4G/LTE	Network shutdown	-
US Virgin Islands	T-Mobile	-	New coverage	2G, 4G/LTE

planX3

Country	Networks	Before	Change	After
Denmark	TDC	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Denmark	Telenor	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Germany	O2	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Hungary	Vodafone	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Italy	TIM	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Italy	Vodafone	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Luxembourg	Post	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Netherlands	KPN	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Netherlands	Vodafone	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Norway	Telia	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Slovenia	A1	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Slovenia	Mobitel	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Switzerland	Salt	2G, 3G, 4G/LTE	2G sunset	3G, 4G/LTE
Switzerland	Sunrise	2G, 3G, 4G/LTE	2G sunset	3G, 4G/LTE

planP1

Country	Networks	Before	Change	After
Luxembourg	Post	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Netherlands	KPN	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Netherlands	Vodafone	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Norway	Telia	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE
Slovenia	A1	2G, 3G, 4G/LTE	3G sunset	2G, 4G/LTE

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

As previously announced, we have made the following changes to the User Console Billing & Payment History screen.

New permissions required

In order to improve the details displayed on the Billing & Payment History screen, the User Console was updated to retrieve additional information using the Order:listOrders API. Accordingly, SAM Users are now required to have permission to access this API (in addition to existing permissions) in order to continue viewing this section of the User Console.

Any SAM User that does not have permission to access the Order:listOrders API will not be able to view any billing and payment details, and will instead see the following error message when viewing the Billing & Payment History screen:

To allow a SAM User to continue viewing the Billing & Payment History screen, please update the SAM User's permission statement to add access to the Order:listOrders API, such as in the following permission statement:

{
  "statements": [
    {
      "effect": "allow",
      "api": [
        "Order:listOrders"
      ]
    }
  ]
}

Please note:

• The above example only demonstrates permission for a single API. The Order:listOrders API should be added to a SAM User's existing permissions.
• Besides allowing access to the Order:listOrders API specifically, you can also allow access using wildcards, such as Order:list* (allow access to all Order APIs that begin with list), Order:* (allow access to all Order APIs), or * (allow access to all APIs), depending on the level of granularity required.
• In addition to updating an individual SAM User's permission statement, you can also provide access to multiple SAM Users by updating the permission statements for a Role, or updating the Default SAM User Permissions.

Please refer to the Access Levels documentation for more details on configuring permission statements.

For users accessing accounts using their root account email address and password, no changes are necessary as root accounts have full permission to access all APIs by default.

Improved payment status information

For business customers located in Japan using payment by invoice, the payment status details displayed in the Payment History section of the Billing & Payment History screen has been updated to reflect the following statuses:

• Delegating to 3rd Party: When Soracom is in the process of transferring the invoice payment to a 3rd party payment provider
• Delegated to 3rd Party: When Soracom has transferred the invoice payment to a 3rd party payment provider

These statuses are valid for both Usage Charges (payments for monthly services) and Orders (payments for products purchased).

For additional information regarding invoice payments and payment history, please refer to the Checking past usage fees and Downloading usage fee files (CSV, PDF) documentation (Japanese).

We would like to inform customers of the following upcoming changes to the User Console Billing & Payment History screen.

New permissions required

In order to improve the details displayed on the Billing & Payment History screen, the User Console will be updated to retrieve additional information using the Order:listOrders API. Accordingly, SAM Users will be required to have permission to access this API (in addition to existing permissions) in order to continue viewing this section of the User Console.

Once this change has been applied, any SAM User that does not have permission to access the Order:listOrders API will not be able to view any billing and payment details, and will instead see the following error message when viewing the Billing & Payment History screen:

To allow a SAM User to continue viewing the Billing & Payment History screen, you will need to update the SAM User's permission statement to add access to the Order:listOrders API, such as in the following permission statement:

{
  "statements": [
    {
      "effect": "allow",
      "api": [
        "Order:listOrders"
      ]
    }
  ]
}

Please note:

• The above example only demonstrates permission for a single API. The Order:listOrders API should be added to a SAM User's existing permissions.
• Besides allowing access to the Order:listOrders API specifically, you can also allow access using wildcards, such as Order:list* (allow access to all Order APIs that begin with list), Order:* (allow access to all Order APIs), or * (allow access to all APIs), depending on the level of granularity required.
• In addition to updating an individual SAM User's permission statement, you can also provide access to multiple SAM Users by updating the permission statements for a Role, or updating the Default SAM User Permissions.

Please refer to the Access Levels documentation for more details on configuring permission statements.

For users accessing accounts using their root account email address and password, no changes are necessary as root accounts have full permission to access all APIs by default.

Improved payment status information

For business customers located in Japan using payment by invoice, the payment status details displayed in the Payment History section of the Billing & Payment History screen will be updated to reflect the following statuses:

• Delegating to 3rd Party: When Soracom is in the process of transferring the invoice payment to a 3rd party payment provider
• Delegated to 3rd Party: When Soracom has transferred the invoice payment to a 3rd party payment provider

These statuses will be valid for both Usage Charges (payments for monthly services) and Orders (payments for products purchased).

For additional information regarding invoice payments and payment history, please refer to the Checking past usage fees and Downloading usage fee files (CSV, PDF) documentation (Japanese).

Effective date

These updates are scheduled to take effect on November 8, 2023.

Please note that the effective date may change without prior notice.

If you or members of your organization currently use SAM Users to view the Billing & Payment History screen, we recommend updating your SAM User permission statements (or requesting the owner of your Soracom account to do so) according to the details above as needed, in order to avoid unexpected errors.

If you have any questions or concerns, please don't hesitate to contact the Soracom Support team.

We have added order tracking details to the User Console, allowing you to easily check the delivery status of your orders.

Once your order has shipped, order tracking details will become visible in the Order status section of your order history. These details will include the name of the delivery company and tracking number(s), and clicking the delivery company link will take you to the delivery company's shipment status inquiry page, where you can enter the tracking number to check the delivery status.

IMEI Lock is a standard feature of all Soracom SIMs that allows you to pair a SIM to a specific device based on the device's unique International Mobile Equipment Identifier (IMEI). When enabled, a SIM will only be allowed to connect to a network if the IMEI of the device it is used in matches its IMEI Lock setting. This allows you to effectively prevent unwanted usage charges in case the SIM is stolen and used in a different device.

However, in some cases, a local network might not report the IMEI of the device. Since the IMEI Lock feature strictly enforces IMEI matching, if the IMEI is not reported, Soracom will block the connection by default even if the device is correct, which may result in unexpected downtime.

With this update, the IMEI Lock feature now provides a new option to also allow network connections when a local network has not provided the device's IMEI. This can be used to ensure that a device can still connect to a network even if the network is not reporting the IMEI information, while still actively blocking connections when the IMEI is reported and does not match the IMEI Lock settings.

For more information on this feature, please refer to IMEI Lock.

We are excited to announce some interface improvements to the Soracom Napter On-demand Remote Access service.

Updated interface design

We have updated the Soracom Napter interface in the User Console. Now when you select a SIM and create a new On-demand Remote Access session, the new interface will appear as a side panel, matching the look and feel of other parts of the User Console and providing a more consistent experience.

New "Connect using" option

Besides remotely accessing cellular devices that are connected over a cellular network, Napter can also be used to remotely access Wi-Fi and other internet-connected devices that are connected to Soracom using Soracom Arc. The Soracom Arc connection can be added to an existing Soracom Air SIM, allowing a device to have both a Soracom Air connection over cellular networks and a Soracom Arc connection over a local Wi-Fi network, and to switch between them for backup/failover or load balancing applications.

With the updated Napter interface, if a SIM is actively connected with both Soracom Air and Soracom Arc, you can now use a new Connect using option to choose which of these connections to use for the remote access session.

This gives you the ability to specifically choose Soracom Arc for the remote access session in order to minimize cellular data usage costs, or choose Soracom Air if the device's Wi-Fi signal is degraded or offline.

For more information, please refer to the Soracom Napter documentation.

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

plan01s and plan01s - Low Data Volume

Coverage updates

Country	Networks	Before	→	After
Bonaire	Digicel	-	→	2G, 3G, 4G/LTE
British Virgin Islands	Digicel	2G, 3G, 4G/LTE	→	3G, 4G/LTE (*1)
Burundi	Lumitel	-	→	2G, 3G
Finland	Elisa	-	→	2G, 3G, 4G/LTE
Ghana	Vodafone	2G	→	2G, 3G, 4G/LTE
Greenland	Tele Greenland	2G, 3G	→	2G, 3G, 4G/LTE
Indonesia	Telkomsel	-	→	2G
Ireland	3	2G, 3G	→	2G, 3G, 4G/LTE
Malawi	Airtel	-	→	2G, 3G, 4G/LTE
Mauritius	my.t	2G, 3G	→	2G, 3G, 4G/LTE
Thailand	DTAC	-	→	2G, 3G

(*1) 2G network sunset/shutdown

Price updates

Country	Networks	Before	→	After
Andorra	All	Contact us	→	0.50 USD/MB
Monaco	All	Contact us	→	0.50 USD/MB

planP1

Coverage updates

Country	Networks	Before	→	After
Mexico	AT&T	-	→	3G, 4G/LTE

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

We are excited to introduce a new modern design for the User Console sign in screen!

In addition to improving the interface using the Soracom Design System, this update also increases the page loading speed by up to 5 times.

You can begin using the new sign in screen today at: https://auth.soracom.io/login

At this time, the existing sign in screen is still available. However, please note that we plan to automatically redirect to the new sign in screen at a future date.

As previously announced on August 25, 2023, the following changes have now been applied to the format of the filename when exporting images or videos from Soracom Cloud Camera Services:

• Milliseconds will be added to timestamps.
• The timestamp(s) will refer to the date/time that the video was recorded rather than the date/time that the file was exported.

For more details about the changes, please refer to the Upcoming changes to filename format when exporting SoraCam files announcement.

As previously announced, SIM IDs have been added to the service usage history CSVs as of August 24, 2023.

With this update, each line of the service usage history CSVs will also include the SIM's 19- or 32-digit SIM ID. As the SIM ID uniquely identifies each physical SIM regardless of whether Subscription Containers have been added, you will be able to easily track the total service usage for a particular SIM no matter which of its IMSIs were active.

For download instructions and additional information on service usage history CSVs, please refer to the following documentation:

• SORACOM Air
• SORACOM Beam
• SORACOM Funk
• SORACOM Funnel
• SORACOM Harvest Data

The corresponding export stats APIs have also been updated accordingly.