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
99.89 % 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
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
Past Incidents
Oct 7, 2022

No incidents reported today.

Oct 6, 2022

No incidents reported.

Oct 5, 2022

No incidents reported.

Oct 4, 2022

No incidents reported.

Oct 3, 2022

No incidents reported.

Oct 2, 2022

No incidents reported.

Oct 1, 2022

No incidents reported.

Sep 30, 2022
Resolved - Our monitoring shows a reduced inflow of dynamic AIS between Sep 30, 22:00-23:05 UTC. Metrics are now stable at normal levels again.
Sep 30, 22:53 UTC
Monitoring - System performance appears to be back to normal.
Sep 30, 22:36 UTC
Investigating - We have seen degraded performance for dynamic AIS data for the past hour. Investigating.
Sep 30, 22:34 UTC
Sep 29, 2022

No incidents reported.

Sep 28, 2022

No incidents reported.

Sep 27, 2022
Resolved - This incident has been resolved.
Sep 27, 18:44 UTC
Update - Impact seems to be limited to M2.0.
Sep 27, 18:04 UTC
Investigating - We are currently investigating this issue.
Sep 27, 17:57 UTC
Sep 26, 2022
Resolved - Setting the incident as resolved. The API is operating at normal capacity and clients are observed catching up or receiving live data again.
Sep 26, 09:54 UTC
Monitoring - The fix has been implemented and we are monitoring the results. It might take a couple of hours for the clients to catch up with the real-time.
We apologize for any inconvenience this may have caused.

Sep 25, 22:21 UTC
Update - This incident has been escalated to level 2 support as several clients are seeing a % of API calls returning timeout errors which slows down getting data
Sep 25, 20:53 UTC
Investigating - We are currently investigating this issue.
Sep 24, 11:38 UTC
Sep 25, 2022
Sep 24, 2022
Resolved - This incident has been resolved.
Sep 24, 13:13 UTC
Investigating - We are currently investigating this issue.
Sep 24, 12:51 UTC
Sep 23, 2022

No incidents reported.