Is Spire Global Down Right Now? Check if there is a current outage ongoing.

This incident has been resolved.

Last observable issue with real time satellite data volumes was around 11:30UTC today, it's been stable since.

Unfortunately the data flow is not stable yet, there are still interruptions and overall lower volumes. Also unfortunately still no information on any timeline until it's fully stable again. I'll continue monitoring and will only resolve once the feed was stable for a good while.

We are seeing real time satellite data come through again since approx. 13:20 UTC, and the volume is now roughly at nominal levels.

It's confirmed that the issue is being worked on, but unfortunately I do not have any information on a possible timeline to resolution.

Since 10:40 UTC no real time satellite AIS data is available. Currently we don't have any information on when this incident is expected to be resolved - we'll update this report once more is known. All APIs/data delivery mechanisms are otherwise working normally. Customers that are not subscribed to real time satellite AIS data are not affected. And affected customers still get data or API results based on other AIS data.

This incident has been resolved.

Last observable issue with real time satellite data volumes was around 11:30UTC today, it's been stable since.

Unfortunately the data flow is not stable yet, there are still interruptions and overall lower volumes. Also unfortunately still no information on any timeline until it's fully stable again. I'll continue monitoring and will only resolve once the feed was stable for a good while.

We are seeing real time satellite data come through again since approx. 13:20 UTC, and the volume is now roughly at nominal levels.

It's confirmed that the issue is being worked on, but unfortunately I do not have any information on a possible timeline to resolution.

Since 10:40 UTC no real time satellite AIS data is available. Currently we don't have any information on when this incident is expected to be resolved - we'll update this report once more is known.All APIs/data delivery mechanisms are otherwise working normally. Customers that are not subscribed to real time satellite AIS data are not affected. And affected customers still get data or API results based on other AIS data.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

Please be advised that we are currently experiencing a service interruption of the Real Time Satellite feed as of approximately 12:15 UTC.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Dear Maritime Data Platform User, As part of our ongoing commitment to provide quality data and superior products, the Spire Maritime Team have scheduled a maintenance cycle for the Geospatial Web Services (GWS) platform for Thursday, May 22. This maintenance process will only pertain to the clients who are subscribed to the Spire Lemur Satellite, Terrestrial and Dynamic AIS data sources via GWS API. Clients who subscribe to the Real Time Satellite services on GWS are not affected by this maintenance process. Maintenance Details: Spire Geospatial Web Services Scheduled Maintenance Start: Thursday, 22 May 2025 13:00 UTCEnd: Thursday, 22 May 2025 15:00 UTCPlease note: The full duration of the maintenance window will be Two (2) hours. While the maintenance process is underway, the GWS platform will remain online and responsive throughout as the maintenance process will be transparent to all users. However, for those users subscribed to the Spire Lemur Satellite, Terrestrial and Dynamic AIS data sources, there will be a period of several minutes when no new updates to the LVI/HVP/HVT databases will be available. What's Changing? Currently, all AIS data received via dynamic sources are categorized under the 'source' field as S-AIS. Starting May 22, 2025, we will begin returning a new value: V-AIS — to indicate AIS data received via dynamic sources S-AIS — will continue to represent satellite data T-AIS — will continue to represent terrestrial data This update corrects a previously misclassified data stream and will improve the accuracy and granularity of your tracking and analytics. Who’s Affected? This change may impact systems that: - Filter on the 'source' field - Rely on specific expected values in source What Do You Need to Do? Please review your implementation to ensure that your systems can handle the new 'V-AIS' value in the 'source' field. If you rely on hardcoded values or mappings, an update may be required to avoid any unexpected behavior. Please note once again that this maintenance process will only affect those customers who are subscribed to Spire Lemur, Terrestrial and Dynamic AIS data sources via GWS API. Clients with Real Time Satellite feeds will not be affected. All account types will remain accessible and operational during this maintenance process. All reasonable precautions have been taken to prevent additional data loss and to minimize impact to Maritime Data Platform Services. We sincerely apologize for any inconvenience this may cause and thank you in advance for your patience and understanding.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Please be advised that we are currently experiencing a service interruption of the Real Time Satellite feed as of approximately 19:23 UTC.

This incident has been resolved. Recap on impact (all times in UTC): - No updates happened starting 3:40 on the vessels and port-events APIs. Secondarily the routing and ETA APIs were also impacted by the out-of-date vessels API. Starting 6:20 all missing data was processed. Port Events was fully caught up by 6:35 and vessels by 7:00. - Data on the TCP 2.0 API was never impacted, despite the component being marked as impacted on this incident page. - All APIs remainended reachable and operational at all times.

We are continuing to monitor for any further issues.

We have fixed the issue and we are currently monitoring.

We are currently experiencing an issue with our Maritime 2.0 systems and the users may encounter issues. The team is investigating the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Please be advised that we are currently experiencing an unplanned service interruption to our Real Time Satellite feed. Only customers subscribed to the real-time data source are affected. All APIs and any other AIS data sources are nominal.

This incident has been resolved.

Please be advised that we are currently experiencing a service interruption with the LVI layers of the Geospatial Web Services (GWS) platform. Historical Vessel Points (HVP) and Historical Vessel Tracks (HVT) are not affected and operating as normal.

This incident has been resolved.

We are observing lower AIS message volume on part of our dynamic data. This only affects customers who have access to dynamic data. All other data (terrestrial, satellite) is not affected, and all our APIs are operating nominally.

This incident has been resolved.

The volume of dynamic AIS messages is nominal again since 10:45 UTC. Between 08:45 and 10:05 the volume was reduced, and between 10:05 and 10:45 it was increased, likely catching up with delayed messages.

We are observing lower AIS message volume on part of our dynamic data. This only affects customers who have access to dynamic data. All other data (terrestrial, satellite) is not affected, and all our APIs are operating nominally.

This incident has been resolved.

Please be advised that we are currently experiencing a service interruption with the LVI layers of the Geospatial Web Services (GWS) platform. Historical Vessel Points (HVP) and Historical Vessel Tracks (HVT) are not affected and operating as normal.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Please be advised that we are currently experiencing a service interruption with the LVI layers of the Geospatial Web Services (GWS) platform. Historical Vessel Points (HVP) and Historical Vessel Tracks (HVT) are not affected and operating as normal.

This incident has been resolved.

We are continuing to investigate this issue.

We are observing an issue with parts of our Dynamic AIS data. This will result in lower received message volume or update frequency for some customers and possibly varying by geographic area. This affects Dynamic AIS data volumes only, all API services are available and functioning as expected.

This incident has been resolved.

Please be advised that we are currently experiencing a planned service interruption to our Real Time Satellite feed. Only customers subscribed to the real-time data source are affected. All APIs and any other AIS data sources are nominal.

This incident has been resolved.

We caught up with realtime, so all data sources are fully nominal. We are still investigating the root cause and additional stability measures, but do not expect further interruptions.

We took some steps to recover the situation and are seeing recovery at the moment. The affected data is catching up with realtime and latencies dropping. We are still investigating the root cause and ensuring stability.

We are observing an issue with parts of our terrestrial AIS data. This will result in lower received message volume or update frequency for some customers and possibly varying by geographic area. This affects data only, all APIs are otherwise working nominally.

The realtime feed is back in normal service.

We are sorry to report that the real time satellite AIS feed is down since 13:00 CET.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are sorry to report that the real time satellite AIS feed is down since 05:07 UTC We are advised by our partner that it is due to weather related issues in the area of the centre for satellite data reception.

This incident has been resolved.

Please be advised that we are currently experiencing a planned service interruption to our Real Time Satellite feed. Only customers subscribed to the real-time data source are affected. All APIs and any other AIS data sources are nominal.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Please be advised that we are currently experiencing a service interruption with the LVI layers of the Geospatial Web Services (GWS) platform. Historical Vessel Points (HVP) and Historical Vessel Tracks (HVT) are not affected and operating as normal.

This incident has been resolved.

Please be advised that we are currently experiencing an unplanned service interruption to our Real Time Satellite feed. Only customers subscribed to the real-time data source are affected. All APIs and any other AIS data sources are nominal.

This incident has been resolved.

Please be advised that we are currently experiencing an unplanned service interruption to our Real Time Satellite feed. Only customers subscribed to the real-time data source are affected. All APIs and any other AIS data sources are nominal.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently experiencing issues with our data pipeline that are resulting in prolonged latencies for vessel updates and triggering port events. Our engineering team is actively investigating the root cause and is working diligently to resolve the issue as quickly as possible. During this time, users may experience delays in receiving the latest vessel information and event triggers. We apologize for any inconvenience this may cause and appreciate your patience as we work to restore normal operations. Further updates will be provided as more information becomes available.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating a partial outage affecting the GWS HVT/HVP/LVI API. This is impacting all the products containing Lemur Satellite data.

This incident has been resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

Please be advised that we are currently experiencing a service interruption with the HVP and HVT layers of the Geospatial Web Services (GWS) platform.

This incident has been resolved.

The HVP/HVT API is returning to service and we will continue to monitor the situation.

A fix has been implemented and we are monitoring the results.

Please be advised that we are currently experiencing a service interruption with the HVP and HVT layers of the Geospatial Web Services (GWS) platform.

The incident has now been resolved. RT Data Volumes have returned to regular levels.

There is an unexpected issue with the real-time AIS data supply. Corrective measures are already being executed. Only customer subscribed to the real-time data source are affected. All APIs and any other AIS data sources are nominal.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are currently investigating a partial outage affecting the GWS HVT/HVP API. Some customers may experience difficulties connecting to the API, resulting in 504 timeout errors. We understand this issue may be impacting business activities and we are treating it with high priority.

This incident has been resolved.

Since ~7am CEST we observe nominal data flows again.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

We are currently investigating this issue.

The data volume of dynamic is back to normal.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Please be advised that we are currently experiencing an unplanned service interruption with our Real Time Satellite feed.

This incident has been resolved.

Outage related to Spire Sense products.

This incident has been resolved.

The data feed is back to latest messages, still monitoring.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

The Messages API is not being updated with new messages. We are investigating.

This incident has been resolved.

Please be advised that we are currently experiencing a reduction in volume from our Real Time Satellite Constellation. We are currently working with our Real Time Satellite data partner to restore service levels.

This incident has been resolved.

Real Time Satellite data has now returned to service. We will continue to monitor data volumes.

Please be advised that we are now experiencing an unplanned service interruption with Real Time Satellite data.

Please be advised that we are currently experiencing a decrease in Real Time Satellite Data volumes.

A solution has been applied to the GWS production platform and the issue has been resolved as of approximately 05:45 UTC August 15, 2024.

Please be advised that Speed Over Ground (SOG) and Course Over Ground (COG) values in the Latest Vessel Information (LVI) layer are currently showing as incorrect values. This applies to Message Type 27 positional messages only. Positional message types 1,2,3,4 and 18 have the correct SOG and COG values. Our Team has identified the issue and is currently working on a resolution.

This incident has been resolved.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

We are continuing to investigate this issue.

We see a reduction in incoming data from some of our terrestrial sources. Work ongoing to restore.

The incident is resolved but will still be monitored

We believe a fix has now been deployed and all requests should be returning data as normal. We will continue to monitor for a while.

We are having to perform emergency maintenance on the LVI and ShipView applications back end. Some data set combinations are not returning data and this is being investigated. Problems started intermittently from about 13:20 UTC. If you have any related problems please send details including your token to the Spire support team on cx@spire.com

RT Data Volumes have returned to regular levels.

RT Data Volumes are slowly returning to anticipated levels. We will continue to monitor the situation.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

Please be advised that we are currently experiencing a lower volume of Real Time Satellite data.

This incident has been resolved.

Performance seems to be restored and we are monitoring

Issues have been identified where by the Maritime Port Events API sometimes fails to return data, but still returns a success code. It seems that repeated requests will return data and users are encouraged to repeat the requests until data is returned. This is being investigated.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

The feed is recovering. Monitoring.

We are currently investigating this issue.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

Please be advised that there is currently a processing delay in the historical data layers HVP/HVT for several but not all of the Geospatial Web Services databases. The Latest Vessel Information (LVI) layer is not affected and functioning as expected.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

Please be advised that we are currently experiencing intermittent data latency issues with certain layers on the Geospatial Web Services and ShipView platforms. Our Team has identified the issue and is currently monitoring the situation.

This incident has been resolved.

Please be advised that we are currently experiencing data latency issues with certain layers on the Geospatial Web Services and ShipView platforms. Our Team is currently investigating the issues.

This incident has been resolved.

The data feed is back to nominal levels since approx 7:30 UTC.

The issue has been identified and a fix is being implemented.

Since 06:10 UTC we are seeing very little data for our realtime AIS feed. This only affects customers of realtime data - other AIS sources (terrestrial, dynamic, non-real-time satellite) are not affected. All APIs are operational. Investigating.

This incident has been resolved.

We are continuing to investigate this issue.

Please Note that we are currently experiencing issues with the following address on the Geospatial Web Services (GWS) Platform: services.exactearth.com Please use the following address as a solution moving forward: services.spire.com We are currently investigating the issues with exactearth.spire.com and will post updates accordingly.

This incident has been resolved.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

We are continuing to investigate this issue.

We are currently investigating this issue.