All Systems Operational
Maritime 2.0
?
Operational
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
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 Vessels API & Maritime 2.0 GraphQL API update for Vessel ID Values 2023-01-09
Jan 9, 2023 10:00-11:00 UTC
Spire Maritime Vessels API & Maritime 2.0 GraphQL API will be updated on 2023-01-09 at 10:00 UTC
This release implements stable Vessel ID values.
Since launch of the Maritime 2.0 graphQL API in Oct 2021 each new iteration of vessel processing logic has caused the vessel ID values to change. We recognise that this is undesirable behaviour that can cause disruption to some processes.
This is the last time we expect the vessel ID values to change and after this release we expect these to be stable.
The exception being vessels which change MMSI, the new instance of the vessel will still get a new vessel ID value, allowing the history of MMSI values reported by a vessel to be retrieved via different vessel ID values.
For customers with systems based around the use of vessel ID values returned by the APIs, we can provide files of OLD and NEW ID value combinations to prepare for the data transition. If this is something that would be helpful to you then please let us know by emailing sales.engineering@spire.com
Kind Regards
Spire Maritime, Customer Support
Posted on Dec 02, 2022 - 15:11 UTC
This release implements stable Vessel ID values.
Since launch of the Maritime 2.0 graphQL API in Oct 2021 each new iteration of vessel processing logic has caused the vessel ID values to change. We recognise that this is undesirable behaviour that can cause disruption to some processes.
This is the last time we expect the vessel ID values to change and after this release we expect these to be stable.
The exception being vessels which change MMSI, the new instance of the vessel will still get a new vessel ID value, allowing the history of MMSI values reported by a vessel to be retrieved via different vessel ID values.
For customers with systems based around the use of vessel ID values returned by the APIs, we can provide files of OLD and NEW ID value combinations to prepare for the data transition. If this is something that would be helpful to you then please let us know by emailing sales.engineering@spire.com
Kind Regards
Spire Maritime, Customer Support
Posted on Dec 02, 2022 - 15:11 UTC