All Systems Operational

Maritime 2.0 ? Operational
90 days ago
99.95 % uptime
Today
Maritime 2.0 Port Events Operational
90 days ago
99.95 % uptime
Today
Maritime 2.0 Vessel To Port ETA ? Operational
90 days ago
99.95 % uptime
Today
Maritime 2.0 Routing Operational
90 days ago
99.95 % uptime
Today
Maritime TCP 2.0 Operational
90 days ago
99.99 % uptime
Today
Sense Cloud - Messages API Operational
90 days ago
100.0 % uptime
Today
Sense Cloud - Messages TCP Server (Legacy) Operational
90 days ago
100.0 % uptime
Today
Sense Cloud - Messages Data Pipeline Operational
90 days ago
100.0 % uptime
Today
Sense Cloud - Vessels API Operational
90 days ago
100.0 % uptime
Today
Sense Cloud - Historical Positions API Operational
90 days ago
99.85 % uptime
Today
Sense Cloud - Satellite AIS Data Operational
90 days ago
100.0 % uptime
Today
Sense Cloud - Dynamic AIS Data Operational
90 days ago
100.0 % uptime
Today
Sense Cloud - Terrestrial AIS Data Operational
90 days ago
100.0 % uptime
Today
Realtime Satellite AIS (evRT) ? Operational
90 days ago
98.72 % uptime
Today
Latest Vessel Information (LVI) API ? Operational
90 days ago
100.0 % uptime
Today
Uniproxy Feed ? Operational
90 days ago
99.99 % uptime
Today
Historical Vessel Points (HVP) API ? Operational
90 days ago
100.0 % uptime
Today
Historical Vessel Tracks (HVT) API ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Jul 19, 2025

No incidents reported today.

Jul 18, 2025
Resolved - This incident has been resolved.
Jul 18, 12:48 UTC
Update - We are continuing to investigate this issue.
Jul 18, 12:13 UTC
Investigating - We are currently investigating this issue.
Jul 18, 11:15 UTC
Jul 17, 2025

No incidents reported.

Jul 16, 2025

No incidents reported.

Jul 15, 2025
Resolved - This incident has been resolved.
Jul 15, 17:37 UTC
Update - The backfill just finished and all systems metrics are nominal since recovery.
We expect no further issues and thus updates to this incident. We will continue monitoring the systems actively for a while.

Jul 15, 15:32 UTC
Monitoring - The API is working again and we are backfilling data. Current estimates are that backfilling will take 1-2h.
Jul 15, 14:12 UTC
Update - We are having an avenue to recovery now, if it works out we expect starting to backfill data within the hour.
Jul 15, 14:00 UTC
Update - We are still working on recovery, during which the historical positions API is fully unavailable. There is no certain timeline to recovery, we are doing our best to make it as soon as possible and will update as soon as we know more on the timeline.
Jul 15, 12:06 UTC
Update - The original assessment of the scale of the issue was incorret: All historical position data is missing since roughly Saturday midnight.
Jul 15, 08:33 UTC
Identified - There is an ongoing issue where parts of the data in the historical positions API is not available. We are working on recovering it. In the process full interruptions to API access and delayed data updates are to be expected.
Jul 15, 08:27 UTC
Jul 14, 2025

No incidents reported.

Jul 13, 2025
Resolved - This incident has been resolved.
Jul 13, 07:48 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 13, 05:03 UTC
Update - We are continuing to investigate this issue.
Jul 13, 01:19 UTC
Investigating - We are currently investigating this issue.
Jul 13, 01:19 UTC
Jul 12, 2025

No incidents reported.

Jul 11, 2025
Resolved - This incident has been resolved.
Jul 11, 06:17 UTC
Update - We are continuing to monitor for any further issues.
Jul 11, 05:55 UTC
Monitoring - 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.
Jul 11, 05:15 UTC
Identified - 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.
Jul 11, 04:45 UTC
Jul 10, 2025

No incidents reported.

Jul 9, 2025
Resolved - This incident has been resolved.
Jul 9, 11:26 UTC
Identified - The issue has been identified and a fix is being implemented.
Jul 9, 06:47 UTC
Jul 8, 2025
Completed - The scheduled maintenance has been completed.
Jul 8, 19:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 8, 13:00 UTC
Scheduled - As part of our ongoing commitment to provide quality data and superior products, the Spire Maritime Team have scheduled a maintenance cycle for the Real Time Satellite Constellation for Tuesday, 08 July 2025.

Maintenance Details: Spire Scheduled Maintenance Window

Start: Tuesday, 08 July 2025, 13:00 UTC

End: Tuesday, 08 July 2025, 19:00 UTC

Please note: The full duration of the maintenance window will be Six (6) Hours.

Intermittent periods of duration loss of Real Time (RT) Satellite data will occur during the maintenance period. The majority of the connectivity disruptions will occur between 13:00UTC – 16:00UTC. However, there is a possibility of impact until the work concludes at 19:00 UTC. Standard Satellite data, Terrestrial data, and Dynamic data are unaffected by this process.

All account types will remain accessible and operational during this maintenance process.

All reasonable precautions have been taken to prevent additional data loss and minimize the impact to Maritime Data Platform services.

We sincerely apologize for any inconvenience this may cause and thank you in advance for your patience and understanding. Should you encounter any issues or have any questions or concerns, please do not hesitate to contact your Spire Maritime support team at cx@maritimeais.com.

Jun 26, 18:12 UTC
Jul 7, 2025

No incidents reported.

Jul 6, 2025

No incidents reported.

Jul 5, 2025
Resolved - This incident has been resolved.
Jul 5, 00:55 UTC
Update - We are continuing to monitor for any further issues.
Jul 4, 23:11 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 4, 23:07 UTC
Identified - The issue has been identified and a fix is being implemented.
Jul 4, 20:16 UTC
Investigating - We are currently investigating this issue.
Jul 4, 20:00 UTC