Spire Outage History

Spire is up right now

Spire had 28 outages in the last 2 years totaling 151h 38m of downtime — averaging 1.2 incidents per month.

There were 28 Spire outages since January 15, 2025 totaling 151h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.spire.com

Major May 1, 2026

Real Time Satellite Data Service Interruption

Detected by Pingoru
May 01, 2026, 09:10 PM UTC
Resolved
May 01, 2026, 10:41 PM UTC
Duration
1h 30m
Affected: Maritime TCP 2.0Realtime Satellite AIS (evRT)Uniproxy Feed
Timeline · 3 updates
  1. investigating May 01, 2026, 09:10 PM UTC

    Please be advised that we are currently experiencing an unplanned service interruption of the Real Time Satellite feed. All other data sources - Terrestrial and Dynamic/Roaming are operating as expected.

  2. identified May 01, 2026, 09:42 PM UTC

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

  3. resolved May 01, 2026, 10:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 27, 2026

Performance degradation in GWS API

Detected by Pingoru
Apr 27, 2026, 09:56 AM UTC
Resolved
Apr 27, 2026, 03:13 PM UTC
Duration
5h 16m
Affected: Latest Vessel Information (LVI) API
Timeline · 2 updates
  1. investigating Apr 27, 2026, 09:56 AM UTC

    We are currently investigating a performance degradation affecting the GWS LVI API. Response times are temporarily increased. HVP/HVT are unaffected.

  2. resolved Apr 27, 2026, 03:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 23, 2026

Uniproxy Platform Service Interruption

Detected by Pingoru
Apr 23, 2026, 08:04 PM UTC
Resolved
Apr 24, 2026, 12:23 AM UTC
Duration
4h 19m
Affected: Uniproxy Feed
Timeline · 4 updates
  1. investigating Apr 23, 2026, 08:04 PM UTC

    Please be advised that we are currently experiencing an unplanned service interruption of the Uniproxy platform at this time. Our Spire/Kpler Team is currently investigating the issue.

  2. identified Apr 23, 2026, 09:10 PM UTC

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

  3. monitoring Apr 23, 2026, 09:44 PM UTC

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

  4. resolved Apr 24, 2026, 12:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 30, 2026

Reduced volume of Real Time Satellite data - March 30, 2026 - 16:00 UTC - 18:00 UTC

Detected by Pingoru
Mar 30, 2026, 03:54 PM UTC
Resolved
Mar 30, 2026, 06:00 PM UTC
Duration
2h 6m
Affected: Maritime TCP 2.0Realtime Satellite AIS (evRT)Uniproxy Feed
Timeline · 2 updates
  1. investigating Mar 30, 2026, 03:54 PM UTC

    Please be advised that a reduced volume of Real Time Satellite data will be delivered during the 16:00 UTC to 18:00 UTC time frame.

  2. resolved Mar 30, 2026, 06:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 9, 2026

Service Interruption for Uniproxy, Geospatial WebServices (GWS) API Platform - LVI and HVP/HVT Layers includes ShipView

Detected by Pingoru
Mar 09, 2026, 12:02 PM UTC
Resolved
Mar 09, 2026, 01:49 PM UTC
Duration
1h 46m
Affected: Latest Vessel Information (LVI) APIUniproxy FeedHistorical Vessel Points (HVP) APIHistorical Vessel Tracks (HVT) API
Timeline · 4 updates
  1. investigating Mar 09, 2026, 12:02 PM UTC

    Please be advised that we are currently experiencing a service interruption of the legacy exactEarth/Spire Uniproxy and Geospatial Web Services (GWS) API Platform. This is affecting all GWS live and historical data layers. This includes all ShipView users. GWS Latest Vessel Information (LVI) Historical Vessel Points (HVP) Historical Vessel Tracks (HVT) This applies to clients who access the GWS Platform through the following endpoints: https://services.exactearth.com/ https://services.spire.com/ Uniproxy Service endpoints affected as as follows: uniproxy-1.exactearth.com uniproxy-2.exactearth.com All other services are unaffected.

  2. investigating Mar 09, 2026, 12:17 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 09, 2026, 12:29 PM UTC

    A solution has been implemented to address the issue, and we are currently monitoring the results of this action.

  4. resolved Mar 09, 2026, 01:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 4, 2026

Kpler Scheduled Monthly Maintenance Notification - Wednesday, 04 March, 2026 - Extended

Detected by Pingoru
Mar 04, 2026, 08:04 PM UTC
Resolved
Mar 04, 2026, 11:29 PM UTC
Duration
3h 25m
Affected: Maritime TCP 2.0Realtime Satellite AIS (evRT)Uniproxy Feed
Timeline · 3 updates
  1. identified Mar 04, 2026, 08:04 PM UTC

    Due to an abundance of caution, the previously scheduled Maintenance cycle for the Real Time Satellite constellation has been extended for several hours. As a result, Real Time Satellite data will subject to further intermittent periods of duration loss during this extension. We do apologize for this inconvenience.

  2. monitoring Mar 04, 2026, 10:58 PM UTC

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

  3. resolved Mar 04, 2026, 11:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2026

Partial infrastructure outage

Detected by Pingoru
Mar 02, 2026, 06:21 PM UTC
Resolved
Mar 02, 2026, 08:30 PM UTC
Duration
2h 8m
Affected: Realtime Satellite AIS (evRT)Latest Vessel Information (LVI) APIUniproxy FeedHistorical Vessel Points (HVP) APIHistorical Vessel Tracks (HVT) API
Timeline · 3 updates
  1. investigating Mar 02, 2026, 06:21 PM UTC

    Part of our infrastructure used to serve Uniproxy, SFTP and selected feeds of LVI/HVP/HVT is having problems. We're working to restore service.

  2. monitoring Mar 02, 2026, 07:46 PM UTC

    The infrastructure component has recovered, and we're monitoring to make sure all data flows are active again.

  3. resolved Mar 02, 2026, 08:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2026

Reduced satellite data volumes

Detected by Pingoru
Mar 02, 2026, 09:04 AM UTC
Resolved
Mar 02, 2026, 07:47 PM UTC
Duration
10h 43m
Affected: Maritime 2.0Maritime TCP 2.0Sense Cloud - Messages API
Timeline · 2 updates
  1. investigating Mar 02, 2026, 09:04 AM UTC

    We are currently investigating this issue.

  2. resolved Mar 02, 2026, 07:47 PM UTC

    The satellite feed is back to normal levels.

Read the full incident report →

Minor February 13, 2026

Maritime 2.0 Vessel To Port ETA increased latencies

Detected by Pingoru
Feb 13, 2026, 08:30 AM UTC
Resolved
Feb 16, 2026, 08:11 AM UTC
Duration
2d 23h
Affected: Maritime 2.0 Vessel To Port ETA
Timeline · 2 updates
  1. identified Feb 13, 2026, 08:30 AM UTC

    The Vessel To Port ETA API is currently delivering outdated data for some routes. Work is ongoing to get back to normal latencies.

  2. resolved Feb 16, 2026, 08:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 30, 2026

Reduced volume of satellite AIS data

Detected by Pingoru
Jan 30, 2026, 08:25 AM UTC
Resolved
Jan 30, 2026, 11:53 AM UTC
Duration
3h 28m
Affected: Maritime 2.0Sense Cloud - Satellite AIS Data
Timeline · 3 updates
  1. investigating Jan 30, 2026, 08:25 AM UTC

    There is an outage on one of our satellite feeds. We are working to identify the problem and restore the ingestion.

  2. monitoring Jan 30, 2026, 09:13 AM UTC

    The feed is recovering and data is coming back. Monitoring.

  3. resolved Jan 30, 2026, 11:53 AM UTC

    Data is back at nominal levels. Messages during the outage were queued and backfilled.

Read the full incident report →

Major January 21, 2026

Service Interruption of Real Time Satellite Data

Detected by Pingoru
Jan 21, 2026, 07:02 PM UTC
Resolved
Jan 21, 2026, 07:45 PM UTC
Duration
42m
Affected: Maritime TCP 2.0Realtime Satellite AIS (evRT)Uniproxy Feed
Timeline · 3 updates
  1. investigating Jan 21, 2026, 07:02 PM UTC

    Please be advised that we are currently experiencing an unplanned service interruption of the Real Time Satellite feed as of approximately 18:34 UTC. Standard satellite, Terrestrial and Dynamic data are unaffected by this interruption.

  2. monitoring Jan 21, 2026, 07:28 PM UTC

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

  3. resolved Jan 21, 2026, 07:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 27, 2025

Realtime satellite data interruption

Detected by Pingoru
Dec 27, 2025, 12:08 PM UTC
Resolved
Dec 27, 2025, 01:00 PM UTC
Duration
51m
Affected: Realtime Satellite AIS (evRT)
Timeline · 4 updates
  1. investigating Dec 27, 2025, 12:08 PM UTC

    Realtime satellite data is unavailable since approx 11:00 UTC.

  2. identified Dec 27, 2025, 12:20 PM UTC

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

  3. monitoring Dec 27, 2025, 12:24 PM UTC

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

  4. resolved Dec 27, 2025, 01:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 5, 2025

Real time Satellite AIS Feed experiencing outage

Detected by Pingoru
Dec 05, 2025, 09:10 AM UTC
Resolved
Dec 05, 2025, 04:16 PM UTC
Duration
7h 5m
Affected: Realtime Satellite AIS (evRT)
Timeline · 4 updates
  1. investigating Dec 05, 2025, 09:10 AM UTC

    Real time Satellite AIS Feed experiencing outage since 4.00 AM UTC

  2. identified Dec 05, 2025, 03:15 PM UTC

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

  3. monitoring Dec 05, 2025, 03:23 PM UTC

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

  4. resolved Dec 05, 2025, 04:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 25, 2025

Service Interruption - Historical API HVP/HVT Layers

Detected by Pingoru
Nov 25, 2025, 03:28 PM UTC
Resolved
Nov 25, 2025, 04:19 PM UTC
Duration
50m
Affected: Historical Vessel Points (HVP) APIHistorical Vessel Tracks (HVT) API
Timeline · 3 updates
  1. investigating Nov 25, 2025, 03:28 PM UTC

    Please be advised that we are currently experiencing an issue with the Historical API on the Geospatial Web Services (GWS) platform. This is currently affecting the Historical Vessel Points (HVP) and Historical Vessel Tracks (HVT) layers. Live data on the LVI layer is not affected by this service interruption. Our Development Team is currently investigating.

  2. identified Nov 25, 2025, 04:00 PM UTC

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

  3. resolved Nov 25, 2025, 04:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 30, 2025

Service interruption: realtime satellite data

Detected by Pingoru
Aug 30, 2025, 06:20 PM UTC
Resolved
Aug 30, 2025, 08:28 PM UTC
Duration
2h 8m
Affected: Maritime 2.0Maritime 2.0 Port EventsMaritime TCP 2.0Sense Cloud - Messages APIRealtime Satellite AIS (evRT)
Timeline · 2 updates
  1. investigating Aug 30, 2025, 06:20 PM UTC

    The realtime satellite data feed is unavailable since approximately 17:30 UTC. Work ongoing to isolate a root cause.

  2. resolved Aug 30, 2025, 08:28 PM UTC

    Realtime data is fully recovered since 20:00 UTC.

Read the full incident report →

Notice August 20, 2025

Service Interruption on Positional Validation platform.

Detected by Pingoru
Aug 20, 2025, 12:05 PM UTC
Resolved
Aug 20, 2025, 12:55 PM UTC
Duration
50m
Timeline · 3 updates
  1. investigating Aug 20, 2025, 12:05 PM UTC

    Please be advised that we are currently experiencing a service interruption with our Positional Validation (PV) platform only. All other platforms and services are functioning as expected. We are currently investigating the issue.

  2. identified Aug 20, 2025, 12:54 PM UTC

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

  3. resolved Aug 20, 2025, 12:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 16, 2025

Reduced Volume on Dynamic data

Detected by Pingoru
Aug 16, 2025, 07:53 AM UTC
Resolved
Aug 16, 2025, 09:15 AM UTC
Duration
1h 22m
Affected: Maritime 2.0Maritime TCP 2.0Sense Cloud - Dynamic AIS Data
Timeline · 3 updates
  1. investigating Aug 16, 2025, 07:53 AM UTC

    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.

  2. investigating Aug 16, 2025, 09:14 AM UTC

    We are continuing to investigate this issue.

  3. resolved Aug 16, 2025, 09:15 AM UTC

    All data stream have been restored

Read the full incident report →

Major August 4, 2025

Service interruption of Realtime satellite data

Detected by Pingoru
Aug 04, 2025, 04:08 PM UTC
Resolved
Aug 04, 2025, 05:12 PM UTC
Duration
1h 4m
Affected: Maritime 2.0Maritime TCP 2.0Sense Cloud - Messages APIRealtime Satellite AIS (evRT)Historical Vessel Points (HVP) APIHistorical Vessel Tracks (HVT) API
Timeline · 3 updates
  1. investigating Aug 04, 2025, 04:08 PM UTC

    Since 15:20 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 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.

  2. monitoring Aug 04, 2025, 04:17 PM UTC

    The problem is solved, we are monitoring the data volumes

  3. resolved Aug 04, 2025, 05:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 1, 2025

Reduced volume of terrestrial AIS data

Detected by Pingoru
Aug 01, 2025, 08:41 AM UTC
Resolved
Aug 01, 2025, 12:44 PM UTC
Duration
4h 3m
Affected: Maritime 2.0Maritime TCP 2.0Sense Cloud - Messages APIUniproxy Feed
Timeline · 2 updates
  1. investigating Aug 01, 2025, 08:41 AM UTC

    We are currently investigating this issue

  2. resolved Aug 01, 2025, 12:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 21, 2025

Reduced volume of Real Time Satellite data

Detected by Pingoru
Jul 21, 2025, 08:09 PM UTC
Resolved
Jul 21, 2025, 09:12 PM UTC
Duration
1h 3m
Affected: Maritime TCP 2.0Realtime Satellite AIS (evRT)Uniproxy Feed
Timeline · 4 updates
  1. investigating Jul 21, 2025, 08:09 PM UTC

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

  2. identified Jul 21, 2025, 08:09 PM UTC

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

  3. monitoring Jul 21, 2025, 09:06 PM UTC

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

  4. resolved Jul 21, 2025, 09:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 15, 2025

Service degradation on Historical Positions API

Detected by Pingoru
Jul 15, 2025, 08:27 AM UTC
Resolved
Jul 15, 2025, 05:37 PM UTC
Duration
9h 9m
Affected: Sense Cloud - Historical Positions API
Timeline · 7 updates
  1. identified Jul 15, 2025, 08:27 AM UTC

    There is an ongoing issue where parts of the data in the historical positions API is not available. We are working on recovering it. In the process full interruptions to API access and delayed data updates are to be expected.

  2. identified Jul 15, 2025, 08:33 AM UTC

    The original assessment of the scale of the issue was incorret: All historical position data is missing since roughly Saturday midnight.

  3. identified Jul 15, 2025, 12:06 PM UTC

    We are still working on recovery, during which the historical positions API is fully unavailable. There is no certain timeline to recovery, we are doing our best to make it as soon as possible and will update as soon as we know more on the timeline.

  4. identified Jul 15, 2025, 02:00 PM UTC

    We are having an avenue to recovery now, if it works out we expect starting to backfill data within the hour.

  5. monitoring Jul 15, 2025, 02:12 PM UTC

    The API is working again and we are backfilling data. Current estimates are that backfilling will take 1-2h.

  6. monitoring Jul 15, 2025, 03:32 PM UTC

    The backfill just finished and all systems metrics are nominal since recovery. We expect no further issues and thus updates to this incident. We will continue monitoring the systems actively for a while.

  7. resolved Jul 15, 2025, 05:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 13, 2025

Reduced volume of dynamic AIS data

Detected by Pingoru
Jul 13, 2025, 01:19 AM UTC
Resolved
Jul 13, 2025, 07:48 AM UTC
Duration
6h 29m
Affected: Maritime 2.0Maritime TCP 2.0Sense Cloud - Messages APISense Cloud - Dynamic AIS DataUniproxy Feed
Timeline · 4 updates
  1. investigating Jul 13, 2025, 01:19 AM UTC

    We are currently investigating this issue.

  2. investigating Jul 13, 2025, 01:19 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jul 13, 2025, 05:03 AM UTC

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

  4. resolved Jul 13, 2025, 07:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 11, 2025

Partial outage in TCP Server and Uniproxy

Detected by Pingoru
Jul 11, 2025, 04:45 AM UTC
Resolved
Jul 11, 2025, 06:17 AM UTC
Duration
1h 31m
Affected: Maritime TCP 2.0Uniproxy Feed
Timeline · 4 updates
  1. identified Jul 11, 2025, 05:40 AM UTC

    We are currently investigating reports of increased latency and a spike in broken connections affecting our TCP stream and Uniproxy services. Our engineering team is actively working to identify and resolve the root cause. Further updates will be provided as more information becomes available.

  2. monitoring Jul 11, 2025, 05:52 AM UTC

    The issue causing increased latency and broken connections on TCP stream and Uniproxy has been resolved. A fix was successfully applied and services are now operational. We will continue to monitor to ensure stability.

  3. monitoring Jul 11, 2025, 05:55 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jul 11, 2025, 06:17 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 12, 2025

Maritime 2.0 API outage

Detected by Pingoru
May 12, 2025, 03:39 AM UTC
Resolved
May 12, 2025, 09:37 AM UTC
Duration
5h 57m
Affected: Maritime 2.0Maritime 2.0 Port EventsMaritime 2.0 Vessel To Port ETAMaritime 2.0 RoutingMaritime TCP 2.0
Timeline · 4 updates
  1. investigating May 12, 2025, 03:39 AM UTC

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

  2. monitoring May 12, 2025, 05:20 AM UTC

    We have fixed the issue and we are currently monitoring.

  3. monitoring May 12, 2025, 06:48 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved May 12, 2025, 09:37 AM 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.

Read the full incident report →

Minor April 10, 2025

Geospatial Web Services (GWS) Latest Vessel Information (LVI) Layer Service Interruption

Detected by Pingoru
Apr 10, 2025, 08:35 PM UTC
Resolved
Apr 10, 2025, 10:38 PM UTC
Duration
2h 2m
Affected: Latest Vessel Information (LVI) API
Timeline · 2 updates
  1. investigating Apr 10, 2025, 10:35 PM UTC

    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.

  2. resolved Apr 10, 2025, 10:38 PM UTC

    This incident has been resolved.

Read the full incident report →