Spire incident

Reduced volume of terrestrial AIS data

Minor Resolved View vendor source →

Spire experienced a minor incident on March 3, 2025 affecting Maritime 2.0 and Maritime TCP 2.0 and 1 more component, lasting 6h 31m. The incident has been resolved; the full update timeline is below.

Started
Mar 03, 2025, 08:11 AM UTC
Resolved
Mar 03, 2025, 02:43 PM UTC
Duration
6h 31m
Detected by Pingoru
Mar 03, 2025, 08:11 AM UTC

Affected components

Maritime 2.0Maritime TCP 2.0Sense Cloud - Terrestrial AIS Data

Update timeline

  1. investigating Mar 03, 2025, 08:11 AM UTC

    We are observing an issue with parts of our terrestrial AIS data. This will result in lower received message volume or update frequency for some customers and possibly varying by geographic area. This affects data only, all APIs are otherwise working nominally.

  2. investigating Mar 03, 2025, 09:07 AM UTC

    We took some steps to recover the situation and are seeing recovery at the moment. The affected data is catching up with realtime and latencies dropping. We are still investigating the root cause and ensuring stability.

  3. monitoring Mar 03, 2025, 09:40 AM UTC

    We caught up with realtime, so all data sources are fully nominal. We are still investigating the root cause and additional stability measures, but do not expect further interruptions.

  4. resolved Mar 03, 2025, 02:43 PM UTC

    This incident has been resolved.