Spire Outage History

Spire experienced a service interruption affecting the Real Time Satellite data feed within their Maritime TCP 2.0 component, while terrestrial and dynamic/roaming data sources continued operating normally. The issue was identified and a fix was implemented, with the incident resolved after 1.5 hours.

The Spire GWS LVI API experienced performance degradation with increased response times, also impacting ShipView services. The incident lasted 5.3 hours and has been resolved.

The Spire Uniproxy platform experienced an unplanned service interruption lasting 4.3 hours. The Spire/Kpler team identified the root cause and implemented a fix, followed by monitoring to ensure stability. The incident was fully resolved with service restored to normal operation.

Spire experienced a reduction in Real Time Satellite data volume from 16:00 to 18:00 UTC on March 30, 2026, affecting the Maritime TCP 2.0 component. The incident lasted approximately 2.1 hours and was resolved by 18:00 UTC.

Spire experienced a major service interruption affecting the Uniproxy and Geospatial Web Services (GWS) API Platform, impacting all live and historical vessel data layers including Latest Vessel Information, Historical Vessel Points, Historical Vessel Tracks, and ShipView users. The outage affected clients accessing services through exactearth.com and spire.com endpoints as well as both Uniproxy service endpoints. The incident lasted 1.8 hours and was resolved after implementing a solution and monitoring period.

Spire's scheduled monthly maintenance for their Real Time Satellite constellation was extended for several hours due to an abundance of caution. This affected Maritime TCP 2.0, causing intermittent periods of Real Time Satellite data loss during the extended maintenance window. The incident was resolved after 3.5 hours with monitoring confirming the fix was successful.

Spire experienced a partial infrastructure outage that affected Uniproxy, SFTP services, and selected LVI/HVP/HVT data feeds for 2.2 hours. The infrastructure component recovered and was monitored to ensure all data flows resumed normal operation. The incident was fully resolved with all affected services restored.

Spire experienced reduced satellite data volumes that affected Maritime 2.0, Sense Cloud Messages API, and Maritime TCP 2.0 services for 10.8 hours. The incident impacted the normal flow of satellite data to these maritime and messaging components. The issue was resolved when the satellite feed returned to normal levels.