Resolved after 5 hours 57 minutes, affecting Maritime 2.0 and Maritime 2.0 Port Events and 1 more, on May 12, 2025.
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.
Affected components
Update timeline
- 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.
- monitoring May 12, 2025, 05:20 AM UTC
We have fixed the issue and we are currently monitoring.
- monitoring May 12, 2025, 06:48 AM UTC
We are continuing to monitor for any further issues.
- 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.
Your product runs on more than Spire
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services