Spire incident

Service interruption of Realtime satellite data

Major Resolved View vendor source →

Spire experienced a major incident on July 4, 2025 affecting Maritime 2.0 and Maritime TCP 2.0 and 1 more component, lasting 4h 54m. The incident has been resolved; the full update timeline is below.

Started
Jul 04, 2025, 08:00 PM UTC
Resolved
Jul 05, 2025, 12:55 AM UTC
Duration
4h 54m
Detected by Pingoru
Jul 04, 2025, 08:00 PM UTC

Affected components

Maritime 2.0Maritime TCP 2.0Sense Cloud - Messages APIRealtime Satellite AIS (evRT)Uniproxy Feed

Update timeline

  1. investigating Jul 04, 2025, 08:00 PM UTC

    We are currently investigating this issue.

  2. identified Jul 04, 2025, 08:16 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 04, 2025, 11:07 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Jul 04, 2025, 11:11 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jul 05, 2025, 12:55 AM UTC

    This incident has been resolved.