Spire Outage History
Spire is up right nowPingoru has recorded 50 incidents for Spire: 22 in the last 12 months and 4 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 10 of 720 (1%) |
| May 2026 | 1 | 2 of 744 (0%) |
| June 2026 | 4 | 13 of 720 (2%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 2 | 10 of 744 (1%) |
| September 2026 | 2 | 6 of 720 (1%) |
| October 2026 | 0 | 0 of 587 (0%) |
Incidents, newest first
Minor July 13, 2025 Reduced volume of dynamic AIS data 6h 29m Maritime 2.0, Maritime TCP 2.0, Sense Cloud - Messages API, Sense Cloud - Dynamic AIS Data and 1 more
Started Jul 13, 2025, 01:19 AM UTC· resolved Jul 13, 2025, 07:48 AM UTC
- investigating Jul 13, 2025, 01:19 AM UTC
We are currently investigating this issue.
- investigating Jul 13, 2025, 01:19 AM UTC
We are continuing to investigate this issue.
- monitoring Jul 13, 2025, 05:03 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 13, 2025, 07:48 AM UTC
This incident has been resolved.
Major July 11, 2025 Partial outage in TCP Server and Uniproxy 1h 31m Maritime TCP 2.0, Uniproxy Feed
Started Jul 11, 2025, 04:45 AM UTC· resolved Jul 11, 2025, 06:17 AM UTC
- identified Jul 11, 2025, 05:40 AM UTC
We are currently investigating reports of increased latency and a spike in broken connections affecting our TCP stream and Uniproxy services. Our engineering team is actively working to identify and resolve the root cause. Further updates will be provided as more information becomes available.
- monitoring Jul 11, 2025, 05:52 AM UTC
The issue causing increased latency and broken connections on TCP stream and Uniproxy has been resolved. A fix was successfully applied and services are now operational. We will continue to monitor to ensure stability.
- monitoring Jul 11, 2025, 05:55 AM UTC
We are continuing to monitor for any further issues.
- resolved Jul 11, 2025, 06:17 AM UTC
This incident has been resolved.
Major May 12, 2025 Maritime 2.0 API outage 5h 57m Maritime 2.0, Maritime 2.0 Port Events, Maritime 2.0 Vessel To Port ETA, Maritime 2.0 Routing and 1 more
Started May 12, 2025, 03:39 AM UTC· resolved May 12, 2025, 09:37 AM UTC
- 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.
Minor April 10, 2025 Geospatial Web Services (GWS) Latest Vessel Information (LVI) Layer Service Interruption 2h 2m Latest Vessel Information (LVI) API
Started Apr 10, 2025, 08:35 PM UTC· resolved Apr 10, 2025, 10:38 PM UTC
- investigating Apr 10, 2025, 10:35 PM UTC
Please be advised that we are currently experiencing a service interruption with the LVI layers of the Geospatial Web Services (GWS) platform. Historical Vessel Points (HVP) and Historical Vessel Tracks (HVT) are not affected and operating as normal.
- resolved Apr 10, 2025, 10:38 PM UTC
This incident has been resolved.
Minor April 10, 2025 Reduced Volume of Dynamic AIS Data 1h 31m Maritime 2.0, Maritime TCP 2.0, Sense Cloud - Dynamic AIS Data
Started Apr 10, 2025, 03:23 PM UTC· resolved Apr 10, 2025, 04:54 PM UTC
- investigating Apr 10, 2025, 03:23 PM UTC
We are observing lower AIS message volume on part of our dynamic data. This only affects customers who have access to dynamic data. All other data (terrestrial, satellite) is not affected, and all our APIs are operating nominally.
- resolved Apr 10, 2025, 04:54 PM UTC
This incident has been resolved.