Spire experienced a major incident on September 27, 2025 affecting Maritime 2.0 and Maritime TCP 2.0 and 1 more component, lasting 5h 1m. The incident has been resolved; the full update timeline is below.
Affected components
Maritime 2.0Maritime TCP 2.0Sense Cloud - Messages APIRealtime Satellite AIS (evRT)Latest Vessel Information (LVI) APIUniproxy FeedHistorical Vessel Points (HVP) APIHistorical Vessel Tracks (HVT) API
Update timeline
- identified Sep 27, 2025, 04:13 PM UTC
No data on realtime satellite AIS since ~4:20 UTC. All other types of data and APIs are otherwise nominal.
- monitoring Sep 27, 2025, 05:40 PM UTC
Data is coming in again, currently going through the backlog of data.
- monitoring Sep 27, 2025, 05:50 PM UTC
And caught up, back to nominal latencies.
- resolved Sep 27, 2025, 09:14 PM UTC
This incident has been resolved.