Spire experienced a minor incident on May 31, 2025 affecting Maritime 2.0 and Maritime TCP 2.0 and 1 more component, lasting 1d 19h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 31, 2025, 11:15 AM UTC
Since 10:40 UTC no real time satellite AIS data is available. Currently we don't have any information on when this incident is expected to be resolved - we'll update this report once more is known. All APIs/data delivery mechanisms are otherwise working normally. Customers that are not subscribed to real time satellite AIS data are not affected. And affected customers still get data or API results based on other AIS data.
- investigating May 31, 2025, 01:18 PM UTC
It's confirmed that the issue is being worked on, but unfortunately I do not have any information on a possible timeline to resolution.
- monitoring May 31, 2025, 01:48 PM UTC
We are seeing real time satellite data come through again since approx. 13:20 UTC, and the volume is now roughly at nominal levels.
- monitoring May 31, 2025, 02:26 PM UTC
Unfortunately the data flow is not stable yet, there are still interruptions and overall lower volumes. Also unfortunately still no information on any timeline until it's fully stable again. I'll continue monitoring and will only resolve once the feed was stable for a good while.
- monitoring Jun 01, 2025, 05:24 PM UTC
Last observable issue with real time satellite data volumes was around 11:30UTC today, it's been stable since.
- resolved Jun 02, 2025, 06:48 AM UTC
This incident has been resolved.