All Systems Operational
Maritime 2.0 ? Operational
90 days ago
100.0 % 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
100.0 % 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
Maritime TCP 2.0 Operational
90 days ago
100.0 % uptime
Today
Maritime 2.0 Routing Operational
90 days ago
100.0 % uptime
Today
Maritime 2.0 Port Events Operational
90 days ago
99.98 % 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.
Scheduled Maintenance
Spire Maritime announces end of life for the Vessels API from 2023-10-01

Since early 2022, users of Vessels API have been advised to migrate to the Maritime 2.0 Vessels 2.0 GraphQL API.
All product enhancements & bug fixes now only occur in the Maritime 2.0 GraphQL API. There are no reasons to continue to use the Vessels API and customers are now expected to migrate to the newer product.

All clients using the Vessels API available on

https://ais.spire.com/vessels or https://api.sense.spire.com/vessels

are requested to switch to using the Maritime 2.0 Vessels 2.0 GraphQL API by 2023-09-30

From 2023-10-01 the Vessels API will be turned off.

Maritime 2.0 GraphQL API is the future of Vessels Data API Services

Spire Maritime are continually working to improve the performance of our API services and to scale the systems to perform well with the continually growing volumes of data and clients. Maritime 2.0 GraphQL is the API platform that provides stable, scalable, performant vessels data services going forward.

The benefits of the Maritime 2.0 GraphQL API:

Improved scalability & performance of API platform
New more flexible and easy to use APIs using GraphQL.
Improved and more accurate vessel identification mechanism:
Recognizing and resolving where possible duplicate vessels reporting using the same MMSI number.
Recognizing and resolving where possible duplicate vessels reporting using the same IMO number.
Improved Terrestrial AIS with additional data not available in Vessels API
Option to subscribe to real time satellite AIS.
Extended coverage of Vessel Characteristics data, twice as many fields and vessels as reported by EVD data in Vessels API.
Additional feature options:
port, terminal, anchorage and canal events through graphQL query endpoints portEventsByShipType, portEventsByShipVessel or portEventsByShipLocation
Future new features all released through graphQL.

Supporting customer migration
Spire Maritime are happy to offer online technical training in use of the Maritime 2.0 GraphQL API to each client migrating from the Vessels API.

If you think this would be useful then please request such training by emailing sales.engineering@spire.com

In March 2022 we held a webinar demonstrating the differences between the Vessels API and Maritime 2.0 Vessels GraphQL API, and information necessary for customers to migrate from the REST API to Maritime 2.0 Vessels 2.0 GraphQL API.
This webinar is still very relevant and can be found on the link below
Watch the Maritime 2.0 GraphQL Migration Tips & Tricks Webinar
https://t.sidekickopen84.com/s3t/c/5/f18dQhb0S7kF8bWLVzW1K7Z1759hl3kW7_k2841CXdp3VP1dmG2P38NBW2dykgs7Rc1Rc101?te=W3R5hFj4cm2zwW3KbsMT4fdK0KW1S31XX43T4PcW3F5m_C1L6_DSW22VXkV1L5M1sW1QbMdy1S2DD9W2310DZ2nFrxGW2qDPq21N4k1tn22XChB123&si=8000000004525033&pi=be78f528-c021-4ef1-bdfe-8aae56522472

Posted on Feb 24, 2023 - 10:17 UTC
Past Incidents
Mar 21, 2023

No incidents reported today.

Mar 20, 2023

No incidents reported.

Mar 19, 2023

No incidents reported.

Mar 18, 2023

No incidents reported.

Mar 17, 2023

No incidents reported.

Mar 16, 2023

No incidents reported.

Mar 15, 2023

No incidents reported.

Mar 14, 2023
Resolved - Data latencies and volumes for dynamic AIS are back to normal.
Mar 14, 16:19 UTC
Update - While data volumes are back to normal, we're still seeing higher latencies for dynamic AIS data. Investigating.
Mar 14, 14:22 UTC
Update - Dynamic data is flowing up-to-date again - we are still monitoring the situation.
Mar 14, 13:39 UTC
Monitoring - A fix has been implemented and we are monitoring status to ensure stability.
Mar 14, 13:37 UTC
Investigating - Dynamic data is delayed since ~12:30 UTC. All APIs are affected: Maritime 2.0 GQL and TCP as well as legacy APIs (vessels, messages and historical positions). Customers on those APIs who do not use dynamic data are not affected.
Mar 14, 13:03 UTC
Mar 13, 2023
Completed - The scheduled maintenance has been completed.
Mar 13, 10:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 13, 09:00 UTC
Scheduled - Another try to incorporate additional data source will be on 13th of March 2023 9:00 UTC. The previous maintenance was canceled due to the external dependency outage. The change affects Maritime 2.0 and TCP service. However, we don't expect disruptions or change in data volume as this is an optional data source but we want users to be aware should anything unexpected occur.

You can follow the updates on progress on this status page.

Should you however have any concerns about this change, then please raise an issue for support at https://faq.spire.com/support

Mar 9, 14:19 UTC
Mar 12, 2023

No incidents reported.

Mar 11, 2023
Resolved - This incident has been resolved.
Mar 11, 14:44 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 11, 10:31 UTC
Identified - We are facing sporadic high error rates in port events functionality.
Mar 10, 21:51 UTC
Mar 10, 2023
Resolved - This incident has been resolved.
Mar 10, 16:31 UTC
Monitoring - Valid results are returned again.
Mar 10, 14:38 UTC
Investigating - Since 13:20 UTC most requests for port events are failing. Investigations are ongoing.
Mar 10, 14:01 UTC
Mar 9, 2023
Resolved - The root cause is resolved, and port-events service is back to normal.
Mar 9, 19:52 UTC
Monitoring - Port-events service quality is back to normal for the past 45 minutes. We will continue to monitor to make sure it's fully operational.
Mar 9, 18:59 UTC
Investigating - We are observing a very high number of errors in requests for port events since 15:45 UTC. Investigation ongoing.
Mar 9, 17:11 UTC
Mar 8, 2023
Completed - The scheduled maintenance has been completed.
Mar 8, 10:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 8, 09:00 UTC
Scheduled - We will incorporate additional data source on 8th of March 2023 9:00 UTC. The change affects Maritime 2.0 and TCP service. However, we don't expect disruptions or change in data volume as this is an optional data source but we want users to be aware should anything unexpected occur.

You can follow the updates on progress on this status page.

Should you however have any concerns about this change, then please raise an issue for support at https://faq.spire.com/support

Mar 7, 15:47 UTC
Mar 7, 2023

No incidents reported.