Get webhook notifications whenever Spire Maritime a Kpler Company creates an incident, updates an incident, resolves an incident or changes a component status.
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.
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.
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.
Mar 11, 18:37 UTC
Completed -
The scheduled maintenance has been completed.
Mar 12, 01:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 11, 17:00 UTC
Scheduled -
As part of our ongoing commitment to provide quality data and superior products, the Spire Maritime/Kpler Team have scheduled a maintenance cycle for the Real Time Satellite Constellation for Wednesday, 11 March, 2026.
Maintenance Details: Kpler Real Time Satellite Scheduled Maintenance Window
Start: Wednesday, 11 March 2026, 17:00 UTC
End: Wednesday, 12 March 2026, 01:00 UTC
Please note: The full duration of the maintenance window will be Eight (8) Hours.
Intermittent periods of duration loss of Real Time (RT) Satellite data will occur during the entire maintenance period. Standard Satellite data, Terrestrial data, and Dynamic data are unaffected by this process.
All account types will remain accessible and operational during this maintenance process.
All reasonable precautions have been taken to prevent additional data loss and minimize the impact to Maritime Data Platform services.
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.
Mar 5, 20:50 UTC
Resolved -
This incident has been resolved.
Mar 9, 13:49 UTC
Monitoring -
A solution has been implemented to address the issue, and we are currently monitoring the results of this action.
Mar 9, 12:29 UTC
Update -
We are continuing to investigate this issue.
Mar 9, 12:17 UTC
Investigating -
Please be advised that we are currently experiencing a service interruption of the legacy exactEarth/Spire Uniproxy and Geospatial Web Services (GWS) API Platform. This is affecting all GWS live and historical data layers. This includes all ShipView users.