Legacy Spire Maritime Infrastructure Migration for Spire Martime APIs, TCP, SFTP and GWS/ShipView - Wednesday, 18 March 2026

Scheduled Maintenance Report for Spire Maritime a Kpler Company

Completed

The scheduled maintenance has been completed.

Posted Mar 18, 2026 - 16:00 UTC

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Posted Mar 18, 2026 - 08:00 UTC

Update

We will be undergoing scheduled maintenance during this time.

Posted Mar 16, 2026 - 12:38 UTC

Update

We will be undergoing scheduled maintenance during this time.

Posted Mar 13, 2026 - 16:00 UTC

Update

We will be undergoing scheduled maintenance during this time.

Posted Mar 13, 2026 - 16:00 UTC

Scheduled

Maintenance Notice: Spire Maritime Infrastructure Migration
Scheduled Change Date: Wednesday, March 18, 2026 ; 08:00UTC - 16:00UTC

As part of the continued migration from Spire Maritime to Kpler infrastructure, we are decommissioning legacy Spire DNS names for Maritime 2.0 GraphQL API group, TCP, Messages API, SFTP, and GWS/ShipView platforms. You must update your network and firewall configurations to ensure uninterrupted service. Please note, if you have already connected to the Kpler endpoints listed below, no further action is required on your end.

**At the conclusion of the maintenance window, you will no longer receive data from Legacy Spire Hostnames.

1. TCP Stream
Spire Hostname: streamingv2.ais.spire.com
Kpler Hostname: streaming.sml.kpler.com (Port 25000)
IP Addresses: 52.51.219.17, 54.195.92.196, 63.34.104.226
Action Required: * Ensure new IP addresses are reachable for outbound traffic.
Connect to the new Kpler hostname and port.
Note on Data Offsets: Following the switch, TCP Server offsets will reset to "Latest" (real-time). This may result in a data gap. To prevent data loss, you must manually set your offsets after the switch to initiate a backfill.

2. Maritime 2.0 GraphQL API group
(Vessels, Port Events, Routing)
Spire Hostname: https://api.spire.com/graphql
Kpler Hostname: https://api.sml.kpler.com/graphql
IP Addresses: 166.117.34.55, 166.117.222.208
Action Required: * Ensure new IP addresses are reachable for outbound traffic.
Connect to the new Kpler hostname and port.

3. Messages API
Spire Hostname: https://ais.spire.com/messages ; https://api.sense.spire.com/messages
Kpler Hostname: https://rest.sml.kpler.com/messages
IP Addresses: 166.117.34.55, 166.117.222.208
Action Required: * Ensure new IP addresses are reachable for outbound traffic.
Connect to the new Kpler hostname and port.

4. SFTP Server
(SUS, flat-file-writers)
Spire Hostname: clients.spire.com
Kpler Hostname: sftp.sml.kpler.com
IP Addresses: 54.170.202.218, 54.170.105.82
Action Required: * Ensure new IP addresses are reachable for outbound traffic.
Connect to the new Kpler hostname and port.
SSH Host Keys: If you use SSH host key verification, you will need to accept the new host key during your first connection to the new endpoint.
Note on File Timestamps: While file cadence remains the same, timestamps may shift slightly (e.g., a file previously arriving at 00:11 UTC may now arrive at 00:15 UTC).

5. Uniproxy
Spire Hostname: uniproxy-1.exactearth.com, uniproxy-2.exactearth.com
Kpler Hostname: uniproxy-1.exactearth.com, uniproxy-2.exactearth.com (Unchanged)
IP Addresses: 34.255.239.201, 54.78.25.67, 34.249.40.226
Action Required: Ensure the new IP addresses are reachable for outbound traffic.

6. Shipview
Spire Hostname: https://shipview.spire.com/, https://shipview.exactearth.com
Kpler Hostname: https://shipview.exactearth.com
Action Required: Connect to the new Kpler hostname for this service.

7. GWS APIs
(LVI, HVT, HVP, ShipTrax, AIS PV)
Spire Hostname: https://services.spire.com, https://services.exactearth.com
Kpler Hostname: https://services.exactearth.com
Action Required: Connect to the new Kpler hostname for this service.

We sincerely apologize for any inconvenience this may cause and thank you in advance for your patience and understanding. Should you encounter any issues or have any questions or concerns, please do not hesitate to contact your Spire Maritime/Kpler support team at sp@kpler.com.

Posted Mar 11, 2026 - 18:37 UTC

This scheduled maintenance affected: Maritime 2.0, Maritime 2.0 Port Events, Maritime 2.0 Vessel To Port ETA, Maritime 2.0 Routing, Maritime TCP 2.0, Sense Cloud - Messages API, Realtime Satellite AIS (evRT), Latest Vessel Information (LVI) API, Uniproxy Feed, Historical Vessel Points (HVP) API, and Historical Vessel Tracks (HVT) API.