Spire incident

Maritime 2.0 API outage

Major Resolved View vendor source →

Spire experienced a major incident on May 12, 2025 affecting Maritime 2.0 and Maritime 2.0 Port Events and 1 more component, lasting 5h 57m. The incident has been resolved; the full update timeline is below.

Started
May 12, 2025, 03:39 AM UTC
Resolved
May 12, 2025, 09:37 AM UTC
Duration
5h 57m
Detected by Pingoru
May 12, 2025, 03:39 AM UTC

Affected components

Maritime 2.0Maritime 2.0 Port EventsMaritime 2.0 Vessel To Port ETAMaritime 2.0 RoutingMaritime TCP 2.0

Update timeline

  1. investigating May 12, 2025, 03:39 AM UTC

    We are currently experiencing an issue with our Maritime 2.0 systems and the users may encounter issues. The team is investigating the issue.

  2. monitoring May 12, 2025, 05:20 AM UTC

    We have fixed the issue and we are currently monitoring.

  3. monitoring May 12, 2025, 06:48 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved May 12, 2025, 09:37 AM UTC

    This incident has been resolved. Recap on impact (all times in UTC): - No updates happened starting 3:40 on the vessels and port-events APIs. Secondarily the routing and ETA APIs were also impacted by the out-of-date vessels API. Starting 6:20 all missing data was processed. Port Events was fully caught up by 6:35 and vessels by 7:00. - Data on the TCP 2.0 API was never impacted, despite the component being marked as impacted on this incident page. - All APIs remainended reachable and operational at all times.