Intercontinental Exchange Outage History

Intercontinental Exchange partial outage · 3 active incidents View live status →

Intercontinental Exchange had 226 outages in the last 2 years totaling 440h 49m of downtime — averaging 9.3 incidents per month.

There were 226 Intercontinental Exchange outages since April 25, 2026 totaling 440h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.ice.com/status

Major May 29, 2026

Latency and Failed Partner Connect Submissions

Detected by Pingoru
May 29, 2026, 05:00 PM UTC
Resolved
May 29, 2026, 05:37 PM UTC
Duration
36m
Affected: Encompass Services and Partner Network
Timeline · 1 update
  1. identified May 29, 2026, 05:00 PM UTC

    ICE is aware of an issue impacting some integrations through Encompass Partner Connect. Our team is actively investigating now.

Read the full incident report →

Major May 29, 2026

Service Advisory: INC29737786: Service Impact: Wireless Degradation: Frankfurt, Germany [FR2] <-> Slough, UK [LD4]

Detected by Pingoru
May 29, 2026, 07:39 AM UTC
Resolved
May 30, 2026, 03:50 AM UTC
Duration
20h 10m
Affected: Wireless: EMEA
Timeline · 5 updates
  1. identified May 28, 2026, 08:33 PM UTC

    UPDATE: Service remains impacted due to weather. Further updates will be provided as they are received.

  2. identified May 28, 2026, 08:33 PM UTC

    UPDATE: Service remains impacted due to weather. Further updates will be provided as they are received.

  3. identified May 29, 2026, 07:39 AM UTC

    UPDATE: Service remains impacted due to weather. Further updates will be provided as they are received.

  4. identified May 29, 2026, 07:39 AM UTC

    UPDATE: Service remains impacted due to weather. Further updates will be provided as they are received.

  5. identified May 29, 2026, 07:39 AM UTC

    UPDATE: Service remains impacted due to weather. Further updates will be provided as they are received.

Read the full incident report →

Major May 28, 2026

Alert Advisory: ICE Invoicing Invoice Submission Exception Setup - Update

Detected by Pingoru
May 28, 2026, 07:53 PM UTC
Resolved
Jun 04, 2026, 07:51 PM UTC
Duration
6d 23h
Affected: Invoicing
Timeline · 4 updates
  1. identified May 28, 2026, 07:53 PM UTC

    ICE Invoicing is currently experiencing an issue with the Business Rules for the Invoice and Line Item Submission Exception. As a result, exceptions may be incorrectly created on invoices when the rule contains a condition for BK Status Code. If there is an Auto Deny Rule in place, invoices will be prevented for submission. All appropriate levels of support are engaged. We will advise you once the issue is resolved. Please communicate this alert internally within your organization.

  2. identified May 28, 2026, 07:53 PM UTC

    The issue previously communicated with advisory A26-0528151054, which has impacted ICE Invoicing Business Rules is currently targeted for a fix on Monday, June 1, 2026, at 8:00 PM ET. We will communicate any updates or changes to this timeline as they occur. Please communicate this alert internally within your organization.

  3. identified May 28, 2026, 07:53 PM UTC

    The issue previously communicated under advisory A26-0529081202, which has impacted ICE Invoicing Business Rules, has been rescheduled. While we continue working toward resolution, Business Rules for the Invoice and Line Item Submission Exception may require manual review. Additionally, if you are currently using the Auto Deny feature and would like ICE to temporarily disable it, please contact Client Support directly for assistance. We will provide further updates as they become available. Please ensure this alert is communicated internally within your organization.

  4. identified May 28, 2026, 07:53 PM UTC

    The issue previously communicated under advisory A26-0601160640, which has impacted ICE Invoicing Business Rules, is now scheduled for resolution today, Wednesday, June 3, 2026, between 8:00 PM through 11:00 PM ET. We will advise you once the issue is resolved. Please communicate this alert internally within your organization.

Read the full incident report →