Skip to content
M2M.globalGet early access

Deliver IoT SIM traffic into your datacenter or office

Updated

Your devices’ data can land directly in your own racks: by a cross-connect if your equipment is in a colocation facility where we are present, or by an IPsec tunnel to your firewall anywhere else. In both cases the SIMs use a private APN and private addresses; with a cross-connect, the traffic never touches the internet at all.

Status: Coming soon (checked 26 October 2026) · Notify me when available

Key points

Choosing between them

Cross-connectIPsec tunnel
Crosses the internetNoYes, encrypted
WhereColocation facility where we are presentAny site with a firewall
Set-up timeDays (building operator)Hours
BandwidthPort speed of the cross-connectYour internet access and firewall
Best forRegulated data, OT, paymentPilots, small sites, backup path

Steps (IPsec)

  1. Send us your firewall’s public IP, the private range of your servers, and your choice of BGP or static routing.
  2. We send the IPsec parameters (IKEv2 proposals, pre-shared key through a secure channel, our private range).
  3. Configure the tunnel and routes on your firewall, then filter so that only the SIM range reaches your servers.
  4. Test from a device: your server’s private IP must answer.

Learn more

Frequently asked questions

What is a cross-connect?

A cross-connect is a physical cable, usually fibre, laid by the colocation operator between two customers' equipment in the same building. Traffic on it never leaves the building and never touches the internet.

My servers are not in a colocation facility. Can I still receive private traffic?

Yes, through an IPsec tunnel to your firewall at any site. The tunnel is encrypted but uses the internet as transport; if that is not acceptable, a private line from your site to a colocation facility is the alternative.

Which firewalls work for IPsec delivery?

Any firewall or router that supports IKEv2 site-to-site IPsec with BGP or static routes. We give you the parameters to configure.