Service Endpoints

While Soracom has never changed the IP addresses of its service endpoints, we can't guarantee that they won't change in the future. If you need to use IP addresses, ensure they remain configurable or refresh them periodically from DNS.

Soracom Air for Cellular

When connecting to a cellular network using a Soracom IoT SIM card, your device should be configured with the following APN settings:

| Item | Global | Japan | | ----|----|---- | Plans |


| | | | APN | soracom.io | soracom.io | du.soracom.io | | Username | sora | sora | sora | | Password | sora | sora | sora | | PDP Type | IP | IP | IP | | Authentication Type | CHAP or PAP | CHAP or PAP | CHAP or PAP |

4G/LTE and newer devices are often able to automatically retrieve the soracom.io APN setting directly from the network. However, for 2G and 3G connections, the APN must be configured on the device in advance. In general, you should configure the APN setting whenever possible. ! When a device uses a Soracom SIM to connect to a cellular network, Soracom will authenticate the device using credentials that are stored inside the SIM. In turn, the Username and Password settings can be treated as optional and omitted. However, these settings are provided in order to support devices that do not allow these settings to be omitted.

Ping Response Service

You can use the Ping Response Service to confirm that a device can reach the Soracom network. To do so, ping the endpoint:

If a device cannot reach the Soracom Ping Response Service (pong.soracom.io), another device or server may respond as a proxy. Verify that the IP address shown in the first line of ping output (e.g., PING pong.soracom.io (100.127.100.127)) is within the 100.64.0.0/10 range (100.64.0.0 - 100.127.255.255).

Soracom Beam

When sending data to Beam, your device should use the following endpoints:

Air for Cellular and Arc device endpoints:

Air for Sigfox and Air for LoRaWAN devices do not require endpoint configuration.

Inventory devices with resources where observe is enabled will automatically send resource data, and do not require endpoint configuration.

Soracom Endorse

When requesting a token from Endorse, your Air for Cellular or Arc device should use the following endpoint:

Soracom Funnel

When sending data to Funnel, your device should use the following endpoints:

Air for Cellular and Arc device endpoints:

Air for Sigfox and Air for LoRaWAN devices do not require endpoint configuration.

Inventory devices with resources where observe is enabled will automatically send resource data, and do not require endpoint configuration.

Soracom Funk

When sending data to Funk, your device should use the following endpoints:

Air for Cellular and Arc device endpoints:

Air for Sigfox and Air for LoRaWAN devices do not require endpoint configuration.

Inventory devices with resources where observe is enabled will automatically send resource data, and do not require endpoint configuration.

Soracom Harvest Data

When sending data to Harvest Data, your device should use the following endpoints:

Air for Cellular and Arc device endpoints:

Air for Sigfox and Air for LoRaWAN devices do not require endpoint configuration.

Inventory devices with resources where observe is enabled will automatically send resource data, and do not require endpoint configuration.

Inventory devices can also send arbitrary data by making HTTP POST requests on any interface to the Soracom API. See the Data Collection documentation for more information.

Soracom Harvest Files

When uploading files to Harvest Files, your device should use the following endpoint:

Air for Cellular and Arc device endpoints:

A file path and filename may be appended to the request URL in order to specify the location where the file should be saved within Harvest Files. For more information, refer to the Harvest Files: Uploading Files documentation.

Uploading files using other protocols, or using Air for Sigfox, Air for LoRaWAN, or Soracom Inventory devices, is not supported.

Soracom Inventory

When managing devices with Inventory, your device's LwM2M agent should connect to the following servers:

Soracom Orbit

When sending data to Orbit, your device should use the following endpoints:

For TCP, UDP, and HTTP entry points, you can also use uni.soracom.io.

Unified Endpoint

When sending data to Unified Endpoint, your device should use the following endpoints:

Air for Cellular and Arc device endpoints:

For TCP, UDP, and HTTP entry points, you can also use uni.soracom.io.

Air for Sigfox and Air for LoRaWAN devices do not require endpoint configuration.

Inventory devices with resources where observe is enabled will automatically send resource data, and do not require endpoint configuration.

Soracom APIs

When using the Soracom API, use the following endpoints:

Metadata Service

When using the Metadata Service, your device should use the following endpoint:

DNS Server

When a device using an IoT SIM establishes a session, the IPv4 address and DNS server provided by the Soracom platform are automatically configured. Devices can use this DNS server for name resolution.

The DNS server IP addresses 100.127.0.53 and 100.127.1.53 are part of the Soracom platform's internal address space (100.64.0.0/10 - Shared Address Space RFC6598 ). These addresses are automatically configured when a device establishes a cellular session and are accessible from both cellular and Arc interfaces.

NTP Server

Soracom provides an internal NTP server to allow devices that may not have internet access to keep accurate time.

The NTP server IP address 100.127.0.123 is part of the Soracom platform's internal address space (100.64.0.0/10 - Shared Address Space RFC6598 ). This address is accessible from both cellular and Arc interfaces.

The Soracom NTP server uses Leap Smearing to smooth out leap second adjustments, eliminating the need to worry about application errors caused by leap second additions.