All Systems Operational
Maritime 2.0
Operational
GraphQL API with all queries
Sense Cloud - Messages API
Operational
Sense Cloud - Messages TCP Server (Legacy)
Operational
Sense Cloud - Messages Data Pipeline
Operational
Sense Cloud - Vessels API
Operational
Sense Cloud - Historical Positions API
Operational
Sense Cloud - Satellite AIS Data
Operational
Sense Cloud - Dynamic AIS Data
Operational
Sense Cloud - Terrestrial AIS Data
Operational
Maritime TCP 2.0
Operational
Maritime 2.0 Routing
Operational
Maritime 2.0 Port Events
Operational
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 End of Life for Vessels API 2023-09-30
Oct 1, 2023 00:00-01:00 UTC
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
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
Spire Messages API. Removal of Satellite Name From API Response
Apr 30, 2024 08:00-09:00 UTC
Spire Maritime are removing the satellite Name information from Messages API responses by the 1st May 2024.
We are writing to give you notice about the removal of the satellite IDs from the Messages API. Satellite ID values are currently returned as the source value in the AIS message records returned by the Messages API. Satellite ID values will be replaced with the label satellite.
This is demonstrated in the sample message below from the Messages API.
This message shows the satellite ID FM88
"data": [
{
"id": "5ecad38c-76b1-30a3-9f96-787eaf5d55fe",
"nmea": "!AIVDM,1,1,,C,Kp15B=@=MpjiUT?t,0*6D",
"timestamp": "2023-05-08T07:26:57Z",
"msg_id": "1683530817_538006069",
"msg_type": 27,
"created_at": "2023-05-08T10:00:46.468499284Z",
"mmsi": 538006069,
"collection_type": "satellite",
"source": "FM88",
"flag": "Marshall Is",
"flag_short_code": "MH",
"longitude": -69.16833333333334,
"latitude": 37.885,
The new message format would be
"data": [
{
"id": "5ecad38c-76b1-30a3-9f96-787eaf5d55fe",
"nmea": "!AIVDM,1,1,,C,Kp15B=@=MpjiUT?t,0*6D",
"timestamp": "2023-05-08T07:26:57Z",
"msg_id": "1683530817_538006069",
"msg_type": 27,
"created_at": "2023-05-08T10:00:46.468499284Z",
"mmsi": 538006069,
"collection_type": "satellite",
"source": "satellite",
"flag": "Marshall Is",
"flag_short_code": "MH",
"longitude": -69.16833333333334,
"latitude": 37.885,
The source value changing from a satellite ID value FM88 to the label satellite.
The deadline for this change is 1st May 2024
In the coming weeks we will be issuing new tokens to use with the Messages API that hide satellite ID and can be used to test before swapping to the new configuration. Please prepare to make this change as soon as possible and in plenty time to prevent disruption to your data supply.
In case you would like to discuss how this will impact your service then please reply to this email and we can investigate it further with you
Customer Support
If you have any questions about the change, please reach out to the Spire Technical support team using our Support Portal https://faq.spire.com/support/new or by sending an email to sales.engineering@spire.com
Thanks!
Spire Maritime Support Team
Posted on May 17, 2023 - 11:51 UTC
We are writing to give you notice about the removal of the satellite IDs from the Messages API. Satellite ID values are currently returned as the source value in the AIS message records returned by the Messages API. Satellite ID values will be replaced with the label satellite.
This is demonstrated in the sample message below from the Messages API.
This message shows the satellite ID FM88
"data": [
{
"id": "5ecad38c-76b1-30a3-9f96-787eaf5d55fe",
"nmea": "!AIVDM,1,1,,C,Kp15B=@=MpjiUT?t,0*6D",
"timestamp": "2023-05-08T07:26:57Z",
"msg_id": "1683530817_538006069",
"msg_type": 27,
"created_at": "2023-05-08T10:00:46.468499284Z",
"mmsi": 538006069,
"collection_type": "satellite",
"source": "FM88",
"flag": "Marshall Is",
"flag_short_code": "MH",
"longitude": -69.16833333333334,
"latitude": 37.885,
The new message format would be
"data": [
{
"id": "5ecad38c-76b1-30a3-9f96-787eaf5d55fe",
"nmea": "!AIVDM,1,1,,C,Kp15B=@=MpjiUT?t,0*6D",
"timestamp": "2023-05-08T07:26:57Z",
"msg_id": "1683530817_538006069",
"msg_type": 27,
"created_at": "2023-05-08T10:00:46.468499284Z",
"mmsi": 538006069,
"collection_type": "satellite",
"source": "satellite",
"flag": "Marshall Is",
"flag_short_code": "MH",
"longitude": -69.16833333333334,
"latitude": 37.885,
The source value changing from a satellite ID value FM88 to the label satellite.
The deadline for this change is 1st May 2024
In the coming weeks we will be issuing new tokens to use with the Messages API that hide satellite ID and can be used to test before swapping to the new configuration. Please prepare to make this change as soon as possible and in plenty time to prevent disruption to your data supply.
In case you would like to discuss how this will impact your service then please reply to this email and we can investigate it further with you
Customer Support
If you have any questions about the change, please reach out to the Spire Technical support team using our Support Portal https://faq.spire.com/support/new or by sending an email to sales.engineering@spire.com
Thanks!
Spire Maritime Support Team
Posted on May 17, 2023 - 11:51 UTC