We have released a new feature that allows to block or unblock specific networks and RAT (Radio Access Technologies) directly within coverage policies via API and via Portal.

For more details please check product documentation for blocking networks and blocking Radio Access Technologies

The service policy enables or disables RAT types for all devices at once, which is less flexible.

The coverage policy provides greater flexibility, allowing customers to fine-tune their configurations with additional options, such as:

We have updated the interface on the emnify portal to improve clarity and address confusion around the different types of Multi-Factor Authentication (MFA) options: app MFA and email MFA. Additionally, we have enhanced the visibility of security settings in the user list to provide admins with greater control and transparency.

Key Updates in the Interface:

For customers using Factory test mode (FTM) feature we improved the flow and now you can create devices with Factory test straight from SIM inventory.

emnify is rolling out a new feature that will extend the IP address space available to customers to millions of devices, eliminating the current /24 and /28 limitations. This will enable long term growth and at the same time will provide customers significant flexibility in configuring their own IP address spaces.

This feature is available to all emnify customers starting on November 25, 2024 and will be subsequently rolled out for customers as per follow up announcements.

Highlights:

More details are provided in https://docs.emnify.com/how-tos/add-ip-address-spaces in the "Updated" tab.

We have added a new API and enhanced the "Reset Connectivity" feature on the Portal.

Use "Reset Connectivity" to immediately apply updates made under the Service and Coverage Policy to all devices associated with that policy.

Please check API Docs if you have any questions.

Herewith we announce the deprecation of the Quota with Throttling functionality. New devices should not be configured with Quota with Throttling, but Quota with Blocking should be used instead. Similarly, existing devices should be reconfigured to use Quota with Blocking.

Existing devices can continue using Quota with Throttling functionality with the current SLAs until December 31st, 2024.

After October 31st, 2024, we will remove the functionality from the Portal and API.

On December 31st, 2024, we will convert all Service Policies that still use Quota with Throttling to the Quota with blocking feature.

No data connectivity interruption will occur at any stage of the process.

We announce hereby the decommissioning of TCP as transport protocol for OpenVPN connections by 1st of October 2024 and solely support UDP. The goal is to reduce the complexity of our service and simplify operations, while TCP as OpenVPN transport layer does not bring any effective benefits in terms of data connectivity performance. On the contrary, it may produce head of line blocking and get particularly inefficient when transporting a TCP based application (see also https://openvpn.net/faq/what-is-tcp-meltdown/). In order to achieve reliability at the application layer, it is enough if the application itself uses TCP transport (e.g. http, https, ftp, ssh).

Please contact our support in case your Internet service provider blocks UDP traffic, which would then prevent you from establishing OpenVPN connections with our platform over UDP and hence make TCP the only viable alternative (see also https://openvpn.net/faq/why-does-openvpn-use-udp-and-tcp/).

Since the beginning of 2024, we have been collaborating with customers through an evaluation program to trial our converged cellular and satellite services. More than 20 evaluators have tested the solution, shared valuable feedback, and are now offering enhanced services to their customers who need reliable coverage in remote areas.

We are excited to announce that our converged cellular and satellite solutions are now generally available to all customers through our SATPlus (combined cellular and satellite), SATSolo (satellite only), and CellSolo data plans.

For more details on our satellite offerings, please refer to our documentation: https://docs.emnify.com/services/iot-supernetwork-satellite.

If you'd like to test any of our satellite products, we recommend opening a separate test account in the portal and ordering a Satellite eSIM from there. You'll receive a complimentary $10/€10 credit for testing. To upgrade to a production account, please contact your customer success manager.

Interested in learning about the portal features designed to help you better manage satellite connectivity? Find out more here: https://docs.emnify.com/how-tos/manage-satellite-connectivity.

emnify is planning to optimize the selection criteria for the automatic breakout region, taking advantage of the newly available regions eu-central-1 (Frankfurt) and eu-central-2 (Zurich) and the resulting inter-regional latency measurements.

The change will be rolled out starting with September 30th, 2024.

As a result, customers who configured the “Automatic breakout region” in the Service Policy will observe lower latencies on the data path due to the data traffic being shifted to a closer geographical location.

No interruption is expected, because data sessions will migrate to the newly assigned regions as they are being recreated by the devices.

However, customers who implement IP address filtering on the backend / application must be aware that the public IP addresses of the device may change and therefore may get blocked. To prevent this from happening, the firewall rules must be updated to include all the public IP address used by emnify, as documented here: https://support.emnify.com/hc/en-us/articles/4417775717010-List-of-emnify-s-public-IPs. The most frequent migration will be from eu-west-1 (Ireland) to eu-central-1 (Frankfurt).

The breakout region used by a particular device can be quickly identified in the portal:

The selection mechanism for the automatic breakout region may be overridden by explicitly configuring a region in the Service Policy (instead of the automatic breakout region).

We have released Reworked SIM inventory Interface.

Please check Product Docs if you have any questions.

In the following months we will keep updating SIM inventory providing new features for SIM management and filtering