All Systems Operational
Uptime over the past 90 days. View historical uptime.
Maritime 2.0 ? Operational
90 days ago
99.36 % uptime
Today
Sense Cloud - Messages API Operational
90 days ago
99.98 % 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
99.68 % 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
98.59 % uptime
Today
Maritime 2.0 Routing Operational
90 days ago
99.89 % 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.

No incidents or maintenance related to this downtime.

Scheduled Maintenance
Maritme TCP V2 - Service Update 2022-05-23 11:00-12:00 UTC May 23, 11:00-12:00 UTC
Spire Maritime will deploy server configuration updates to the TCP V2 service.
These are expected to be seamless changes, deployed one server at a time to address necessary system performance improvements.
Connections to the TCP service will be dropped as each server is updated and new connections will cycle to the other servers in the service.
Posted on May 19, 16:41 UTC
Past Incidents
May 20, 2022

No incidents reported today.

May 19, 2022
Maritime 2.0 GraphQL - Backend Maintenance
Update - The scheduled maintenance has been completed.
May 19, 12:03 UTC
Completed - The scheduled maintenance has been completed.
May 19, 12:01 UTC
Verifying - Verification is currently underway for the maintenance items.
May 19, 11:56 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 19, 11:00 UTC
Scheduled - Maritime 2.0 GraphQL API service will be updated for bug fixes .
These changes have been tested and are waiting for release.
The switch will be non disruptive to users

Should you however have any concerns about this change, then please raise an issue for support at https://faq.spire.com/support
May 18, 14:36 UTC
May 18, 2022
Maritime 2.0 GraphQL - Dynamic AIS Upgrade
Completed - The scheduled maintenance has been completed.
May 18, 12:17 UTC
Verifying - Verification is currently underway for the maintenance items.
May 18, 12:13 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 18, 12:00 UTC
Scheduled - Spire Maritime is pleased to announce an upgrade to the Dynamic AIS service for clients who subscribe to either class A or class B Dynamic AIS through the Maritime 2.0 graphQL API.

The feed of Dynamic AIS has been updated for increased data volume and data quality and the following changes are made to the Dynamic AIS service in this API.

300% increase in source messages from Dynamic AIS
10% increase in the number of unique MMSI reported by Dynamic AIS.
Consistency of all fields of data in messages from Dynamic AIS. Previously Dynamic AIS did not provide navigational status, or repeating values for eta, destination and draft. This behaviour is now improved.

There should be no interruption to service when this change is made but should you have any concerns about this change, then please raise an issue for support at https://faq.spire.com/support
May 17, 16:23 UTC
May 17, 2022
Partial Performance Degradation in Historical Endpoint
Resolved - This incident has been resolved.
May 17, 07:33 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 16, 18:04 UTC
Identified - We are experiencing partial performance degradation in historical positions API (vessels v1). The data from period of 13-05 to 15-05 isn't being returned by the API. We have identified the issue and are working to fix the gap.
May 16, 14:56 UTC
May 16, 2022
Maritime 2.0 GraphQL - Backend Maintenance
Completed - The scheduled maintenance has been completed.
May 16, 12:49 UTC
Update - All systems are are operational. There was a ~5min delay in new updates between 12:26 and 12:31 UTC.
May 16, 12:47 UTC
Verifying - The maintenance tasks are done. We are monitoring the effects.
May 16, 12:29 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 16, 11:00 UTC
Scheduled - Maritime 2.0 GraphQL API service will be updated for a bug fix and also a cluster upgrade.
These changes have been tested and are waiting for release.
The switch will be non disruptive to users

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

No incidents reported.

May 14, 2022

No incidents reported.

May 13, 2022
Degradation on the Endpoint Serving Historical Data
Resolved - Degradation in returning the historical data, i.e. the queries for data after the 13th of May 2022 were failing.
May 13, 10:30 UTC
May 12, 2022
Maritime 2.0 GraphQL - Backend Maintenance
Completed - The maintenance is finished.
May 12, 11:39 UTC
Update - Scheduled maintenance is still in progress. We will provide updates as necessary.
May 12, 11:37 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 12, 11:00 UTC
Scheduled - Maritime 2.0 GraphQL API service will be upgraded for some minor bug fixes.
This is a software version switch that has been in place waiting for release since testing sign off last week.
The switch will be non disruptive to users

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

No incidents reported.

May 10, 2022
Maritme TCP V2 - Service Update 2022-05-10 11:00-12:00 UTC
Completed - The scheduled maintenance has been completed.
May 10, 11:22 UTC
Verifying - Verification is currently underway for the maintenance items.
May 10, 11:15 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 10, 11:00 UTC
Scheduled - Spire Maritime will deploy server configuration updates to the TCP V2 service.
These are expected to be seamless changes, deployed one server at a time to address improvements identified as part of a resolution to previous system interruptions
Connections to the TCP service will be dropped as each server is updated and new connections will cycle to the other servers in the service.
May 6, 14:16 UTC
Maritime TCP 2.0 - Degraded performance
Resolved - Metrics are now nominal, resolving incident.
May 10, 08:24 UTC
Monitoring - A fix has been implemented and we're monitoring metrics.
May 10, 08:05 UTC
Investigating - We're observing anomalous metrics in the TCP server. Investigation is ongoing.
May 10, 07:54 UTC
May 9, 2022
Maritime TCP 2.0 - Data degradation
Resolved - Volume of messages sent is back to normal, meaning all consumers have caught up with any delayed data and are receiving new messages immediately again.
May 9, 21:18 UTC
Monitoring - A fix was rolled out at 9pm UTC. Consumers were reconnected as a consqueuence. Throughput is nominal and consumers are catching up with any delayed messages.
May 9, 21:06 UTC
Investigating - The Maritime TCP 2.0 service experience partial interruption starting 8pm UTC with lower message throughput for some consumers. If a consumer was affected, messages may have been delayed up to 1h before recovery started.
May 9, 21:04 UTC
May 8, 2022

No incidents reported.

May 7, 2022

No incidents reported.

May 6, 2022

No incidents reported.

← Incident History Powered by Atlassian Statuspage