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
Messages API Upgrade
Oct 17, 2022 09:00-10:00 UTC
2022-10-17 Spire Maritime will release an upgraded version of the Messages API.
Following the recent DNS update routing Messages API traffic via the new server cluster, we will release a new implementation of the Messages API.
This will look like the current implementation, but has been coded to perform better in a new computing environment. All users of the Messages API will be automatically switched to the new implementation at this time.
What does not change?
Tokens, URL and API parameters & format of API results will not change.
What will change?
As part of the new API platform, as well as improved performance there will also be an improved version of Dynamic AIS and an additional source of terrestrial AIS that adds coverage mainly in the Gulf of Mexico and US waterways.
For subscribers to Dynamic AIS the volume of messages will increase 2-3 times.
For subscribers to Spire global terrestrial AIS the volume will increase about 10%
The response from the new implementation will match the response from the old Messages API in format, value ranges and how filters work. Internal system values may change which would be values in fields id, msg_id, since and after values. When the swap to the new implementation is made any requests made to the new implementation using pagination values from the old API will still work.
Anyone wishing to test the new system should contact Spire support to request Beta testing access. Otherwise we expect the new Messages API implementation to go live by mid November.
Below are examples of responses from the old and new implementations of Messages API to illustrate the backward compatibility of the system.
API call used:
https://ais.spire.com/messages?fields=decoded&msg_type=1&limit=1
Current API result returned:
{ "paging": {
"since": "GjQKJDRmYmQ0OTI2LWVhMjYtNTI5Yy04YmQ2LTY3YmE2M2VhZjMwNRIMCKDL6ZkGEPjukOEC",
"actual": "1+", "limit": 1 },
"data": [
{ "id": "4fbd4926-ea26-529c-8bd6-67ba63eaf305",
"nmea": "!AIVDM,1,1,,A,17WK5ggP0242RUH>QFK`
}
]
}
If you have any questions concerning this update to the Messages API system then please log a support ticket requesting further guidance in the Spire Maritime support portal here https://faq.spire.com/kb-tickets/new
Posted on Oct 03, 2022 - 14:34 UTC
Following the recent DNS update routing Messages API traffic via the new server cluster, we will release a new implementation of the Messages API.
This will look like the current implementation, but has been coded to perform better in a new computing environment. All users of the Messages API will be automatically switched to the new implementation at this time.
What does not change?
Tokens, URL and API parameters & format of API results will not change.
What will change?
As part of the new API platform, as well as improved performance there will also be an improved version of Dynamic AIS and an additional source of terrestrial AIS that adds coverage mainly in the Gulf of Mexico and US waterways.
For subscribers to Dynamic AIS the volume of messages will increase 2-3 times.
For subscribers to Spire global terrestrial AIS the volume will increase about 10%
The response from the new implementation will match the response from the old Messages API in format, value ranges and how filters work. Internal system values may change which would be values in fields id, msg_id, since and after values. When the swap to the new implementation is made any requests made to the new implementation using pagination values from the old API will still work.
Anyone wishing to test the new system should contact Spire support to request Beta testing access. Otherwise we expect the new Messages API implementation to go live by mid November.
Below are examples of responses from the old and new implementations of Messages API to illustrate the backward compatibility of the system.
API call used:
https://ais.spire.com/messages?fields=decoded&msg_type=1&limit=1
Current API result returned:
{ "paging": {
"since": "GjQKJDRmYmQ0OTI2LWVhMjYtNTI5Yy04YmQ2LTY3YmE2M2VhZjMwNRIMCKDL6ZkGEPjukOEC",
"actual": "1+", "limit": 1 },
"data": [
{ "id": "4fbd4926-ea26-529c-8bd6-67ba63eaf305",
"nmea": "!AIVDM,1,1,,A,17WK5ggP0242RUH>QFK`
}
]
}
If you have any questions concerning this update to the Messages API system then please log a support ticket requesting further guidance in the Spire Maritime support portal here https://faq.spire.com/kb-tickets/new
Posted on Oct 03, 2022 - 14:34 UTC