- Detected by Pingoru
- Aug 27, 2026, 07:34 AM UTC
- Resolved
- Aug 27, 2026, 03:06 PM UTC
- Duration
- 7h 32m
Timeline · 2 updates
-
investigating Aug 27, 2026, 07:34 AM UTC
Status: Investigating Status: We are experiencing a delay in ICE IRM2 market data for COB 26/08/2026 - Actively working to resolve Impact: ICE IRM2 reverted to calculations using T-2 market data (COB 25/08/2026) Affected components ICE (IRM2) (Partial outage)
-
resolved Aug 27, 2026, 03:06 PM UTC
Status: Resolved Resolved: ICE IRM2 market data for COB 26 August is now fully available. All data has been validated and services are operating normally. Affected components ICE (IRM2) (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 26, 2026, 11:50 AM UTC
- Resolved
- Aug 27, 2026, 10:43 AM UTC
- Duration
- 22h 52m
Affected: CME
Timeline · 4 updates
-
investigating Aug 26, 2026, 11:50 AM UTC
Status: Investigating We have identified an issue with CME calculations and we are urgently working on identifying the root cause. We will keep this page updated. Impact: No results or 0's returned in outputs Affected components CME (Partial outage)
-
identified Aug 26, 2026, 03:04 PM UTC
Status: Identified Status: Impacted calculation re-runs now in progress using latest functioning market data valuation date. Problem: We've identified the issue to be originating from CME market data files for valuation date 25/08/2026. Fix: CME SPAN2 calculations have been reverted to running on valuation date 24/08/2026 market data. Affected components CME (Partial outage)
-
monitoring Aug 27, 2026, 07:41 AM UTC
Status: Monitoring Update: Valuation date 26/08/2026 market data confirmed not affected - We are actively out to CME to resolve val date 25/08/2026 Status: CME SPAN2 calculations for COB 25/08/2026 ran on valuation date 24/08/2026 market data Problem: Issue with CME market data files for valuation date 25/08/2026. Affected components CME (Partial outage)
-
resolved Aug 27, 2026, 10:43 AM UTC
Status: Resolved Resolved: Workaround implemented allowing for successful margin calculation. Affected components CME (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 12, 2026, 07:49 AM UTC
- Resolved
- Aug 12, 2026, 11:00 AM UTC
- Duration
- 3h 10m
Affected: CME
Timeline · 3 updates
-
investigating Aug 12, 2026, 07:49 AM UTC
Status: Investigating Status: We have identified an issue with the CME CORE Margin API and we are urgently working on identifying the root cause. We will keep this page updated. Problem/Impact: We query the CME CORE Margin API directly for our cross margin optimisation, used across What If Trades, Rebalance, and CME optimisation reporting. We are receiving back bad requests, resulting in no cross margin optimisation at this time. Affected components CME (Partial outage)
-
investigating Aug 12, 2026, 08:53 AM UTC
Status: Investigating Status: We have identified an issue with the CME CORE Margin API and we are urgently working on identifying the root cause. We will keep this page updated. Problem/Impact: We query the CME CORE Margin API directly for our cross margin optimisation, used across What If Trades, Rebalance, and CME optimisation reporting. We are receiving back bad requests, resulting in no cross margin optimisation at this time. Update: CME have published a circular confirming they are aware of an outage impacting their CME CORE API service and they are investigating. Affected components CME (Partial outage)
-
resolved Aug 12, 2026, 11:00 AM UTC
Status: Resolved Status: We have confirmed that the underlying issue is now resolved. This incident is now closed. Cause: This was a CME outage which appeared driven by recent maintenance work on their side. Affected components CME (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2026, 08:42 AM UTC
- Resolved
- Jun 26, 2026, 08:42 AM UTC
- Duration
- —
Timeline · 2 updates
-
investigating Jun 26, 2026, 07:28 AM UTC
Status: Investigating Problem/Impact: We have identified an issue with processing market data for LCH IRS and SIMM calculations for COB June 25th. Calculations in the interim will be falling back to COB June 24th market data. We will confirm here as soon as we have a further update. Affected components LCH (Cleared IRS) (Partial outage) SIMM (UMR) (Partial outage)
-
resolved Jun 26, 2026, 08:42 AM UTC
Status: Resolved The market data for COB June 25th has been processed and the latest valuation date is now available for the LCH and SIMM calculators. Affected components SIMM (UMR) (Operational) LCH (Cleared IRS) (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 25, 2026, 08:33 AM UTC
- Resolved
- Jun 25, 2026, 08:33 AM UTC
- Duration
- —
Timeline · 2 updates
-
investigating Jun 25, 2026, 07:28 AM UTC
Status: Investigating Status: We have identified an issue with processing market data for LCH IRS and SIMM calculations for COB June 24th. Calculations in the interim will be falling back to COB June 23rd market data. We will confirm here as soon as we have a further update. Affected components SIMM (UMR) (Degraded performance) LCH (Cleared IRS) (Degraded performance)
-
resolved Jun 25, 2026, 08:33 AM UTC
Status: Resolved Status: The market data for COB June 24th has been processed and the latest valuation date is now available for the LCH and SIMM calculators. Affected components SIMM (UMR) (Operational) LCH (Cleared IRS) (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 25, 2026, 07:30 AM UTC
- Resolved
- Jun 25, 2026, 07:30 AM UTC
- Duration
- —
Timeline · 2 updates
-
identified Jun 18, 2026, 06:30 AM UTC
Status: Identified Status: We have identified an issue with missing market data impacting Eurex and LCH calculators. This will mean Eurex and LCH calculations will be falling back to COB June 16th data. We will update this page as soon as there is further information. Affected components LCH (Cleared IRS) (Degraded performance) Eurex (Cleared OTC) (Degraded performance)
-
resolved Jun 25, 2026, 07:30 AM UTC
Status: Resolved Status: Market data for COB June 17th is available for Eurex and LCH calculations. Affected components Eurex (Cleared OTC) (Operational) LCH (Cleared IRS) (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 02:06 PM UTC
- Resolved
- Jun 18, 2026, 02:06 PM UTC
- Duration
- —
Affected: Track - AccountsWhat-If - RiskWhat-If - TradesTrack - ChangeForecast - T+1Validate - PositionsAccess and AuthenticationValidate - OTE/PVTrack - AttributionRebalance - ScenariosMonitor - AANARebalance - RiskForecast - Fixed Price ShocksForecast - Margin at RiskValidate - OverviewMonitor - SIMMValidate - PositionsAccess and AuthenticationTrack - AccountsTrack - AttributionTrack - ChangeRebalance - ScenariosRebalance - RiskForecast - Fixed Price ShocksForecast - Margin at RiskValidate - OverviewValidate - OTE/PVMonitor - SIMMMonitor - AANA
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Jun 16, 2026, 07:00 AM UTC
- Resolved
- Jun 16, 2026, 07:00 AM UTC
- Duration
- —
Affected: EurexEurex
Timeline · 2 updates
-
identified Jun 16, 2026, 06:33 AM UTC
Status: Identified Status: There was a delay in receiving some Eurex market data required for COB June 15th, which means the calculator will be falling back to COB June 12th this morning. However, we have now received the necessary data and this data should be processed in the next half hour. Will provide an update here as soon as this is complete. Affected components Eurex (Degraded performance) Eurex (Cleared OTC) (Degraded performance)
-
resolved Jun 16, 2026, 07:00 AM UTC
Status: Resolved Status: We have finished processing the latest market data and COB June 15th is now available on the Eurex calculator. Affected components Eurex (Cleared OTC) (Operational) Eurex (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 04:02 PM UTC
- Resolved
- Jun 05, 2026, 04:02 PM UTC
- Duration
- —
Affected: Track - AccountsWhat-If - RiskWhat-If - TradesTrack - ChangeForecast - T+1Validate - PositionsTreasury Call Management - Static DataAccess and AuthenticationValidate - OTE/PVTreasury Call Management - WorkflowsTreasury Call Management - ReportingTrack - AttributionRebalance - ScenariosMonitor - AANARebalance - RiskForecast - Fixed Price ShocksForecast - Margin at RiskValidate - OverviewMonitor - SIMMCFaR - Stressed MarginValidate - PositionsCFaR - Stressed MarginAccess and AuthenticationTrack - AccountsTrack - AttributionTrack - ChangeRebalance - ScenariosRebalance - RiskForecast - Fixed Price ShocksForecast - Margin at RiskValidate - OverviewValidate - OTE/PVMonitor - SIMMMonitor - AANATreasury Call Management - WorkflowsTreasury Call Management - Static DataTreasury Call Management - Reporting
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 12:19 PM UTC
- Resolved
- May 28, 2026, 12:19 PM UTC
- Duration
- —
Affected: CMECME
Timeline · 2 updates
-
investigating May 28, 2026, 10:40 AM UTC
Status: Investigating Status: We have identified an issue with CME SPAN 2 market data and we are urgently working on identifying the root cause. Problem/Impact: This is impacting calculations which use CME SPAN 2 data meaning errors are being thrown and "0" IM results are being returned. This appears to be impacting calculations that have ran later in the morning today. Once resolved, any impacted calculations can be re-run. Affected components CME (Cleared OTC) (Degraded performance) CME (Degraded performance)
-
resolved May 28, 2026, 12:19 PM UTC
Status: Resolved Status: We identified an issue with CME SPAN 2 market data which has now been resolved. Problem/Impact: This was impacting calculations using CME SPAN 2 data meaning that calculation errors were thrown and "0" IM was calculated. Impacted calculations have now been re-run after the resolution. Cause: We identified and resolved an issue in our data processing workflow that could intermittently affect the consistency of data being retrieved. We are implementing an improvement to ensure that repeated processing runs remain stable and continue to produce reliable results going forward. Affected components CME (Cleared OTC) (Operational) CME (Operational)
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 10:08 AM UTC
- Resolved
- May 28, 2026, 10:08 AM UTC
- Duration
- —
Affected: CMECME
Timeline · 2 updates
-
investigating May 27, 2026, 09:15 AM UTC
Status: Investigating Status: We have identified an issue with CME Cross Margin savings reports this morning and we are working on identifying the root cause. We will provide further updates ASAP. Problem/Impact: We are currently experiencing issues retrieving the necessary data from CME Core to accurately calculate CME cross margin savings. As a result OpenGamma published CME Cross Margin savings reports are incorrectly displaying "0" savings figures. Our Product Delivery team is currently investigating. Affected components CME (Cleared OTC) (Degraded performance) CME (Degraded performance)
-
resolved May 28, 2026, 10:08 AM UTC
Status: Resolved Status: We have confirmed that the underlying issue is now resolved as of EOD 27th May. Affected components CME (Cleared OTC) (Operational) CME (Operational)
Read the full incident report →
- Detected by Pingoru
- May 15, 2026, 11:30 AM UTC
- Resolved
- May 15, 2026, 11:30 AM UTC
- Duration
- —
Affected: Access and AuthenticationAccess and Authentication
Timeline · 2 updates
-
investigating May 15, 2026, 11:05 AM UTC
Status: Investigating Status: We have identified an issue preventing our UI screen functionality from loading and causing a failure when connecting to our APIs. Our dev team is urgently investigating and we will provide an update here as soon as possible. Affected components Access and Authentication (Full outage) Authentication (Any API) (Full outage)
-
resolved May 15, 2026, 11:30 AM UTC
Status: Resolved Status: Our dev team has identified the issue and a fix has been made to address the problem. UI screens in the OpenGamma platform are now loading and the OpenGamma APIs should be functioning as expected now. Affected components Access and Authentication (Operational) Authentication (Any API) (Operational)
Read the full incident report →
- Detected by Pingoru
- May 13, 2026, 09:07 PM UTC
- Resolved
- May 13, 2026, 09:07 PM UTC
- Duration
- —
Affected: CMECME
Timeline · 2 updates
-
identified May 13, 2026, 08:35 AM UTC
Status: Identified Status: We have identified a CME issue related to market data for new CME contracts. Our Product team has identified a fix which will be implemented to resolve the issue. Problem/Impact: CME data will default to T-2 as a result. Once the fix is implemented, any calculations with T-2 data can be re-run to refresh the results. Affected components CME (Degraded performance)
-
resolved May 13, 2026, 09:07 PM UTC
Status: Resolved Status: We have confirmed that the underlying issue is now resolved. This incident is now closed. Affected components CME (Operational)
Read the full incident report →
- Detected by Pingoru
- May 07, 2026, 09:55 AM UTC
- Resolved
- May 07, 2026, 09:55 AM UTC
- Duration
- —
Timeline · 2 updates
-
investigating May 07, 2026, 06:49 AM UTC
Status: Investigating Status: Under Investigation Problem/Impact: Currently ICE IRM2 calculations are not available for CoB 6th May 2026. Other valuation dates are unaffected. Affected components ICE (IRM2) (Partial outage)
-
resolved May 07, 2026, 09:55 AM UTC
Status: Resolved Status: Resolved Please contact [email protected] for any reruns on impacted calculations Affected components ICE (IRM2) (Operational)
Read the full incident report →
- Detected by Pingoru
- May 07, 2026, 09:54 AM UTC
- Resolved
- May 07, 2026, 09:54 AM UTC
- Duration
- —
Affected: Nasdaq OMXNasdaq OMX
Timeline · 2 updates
-
investigating May 06, 2026, 07:25 AM UTC
Status: Investigating Status: Under investigation Problem/Impact: Early calculation results possibly impacted - TBC Affected components Nasdaq OMX (Partial outage)
-
resolved May 07, 2026, 09:54 AM UTC
Status: Resolved Status: Resolved Affected components Nasdaq OMX (Operational)
Read the full incident report →
- Detected by Pingoru
- May 01, 2026, 11:09 AM UTC
- Resolved
- May 01, 2026, 11:09 AM UTC
- Duration
- —
Timeline · 2 updates
-
investigating Apr 30, 2026, 10:47 AM UTC
Status: Investigating Status: We have identified an issue with LCH market data today - Working actively to resolve Impact: Calculation accuracy Affected components LCH (Cleared IRS) (Partial outage) LCH (Cleared CDS) (Partial outage)
-
resolved May 01, 2026, 11:09 AM UTC
Status: Resolved Status: Resolved Problem/Impact: LCH Calculations returning 0's or unexpected results Cause: Change on LCH side publishing Market Data files Solution: OpenGamma adjusted LCH Market Data file consumption logic Affected components LCH (Cleared IRS) (Operational) LCH (Cleared CDS) (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 01:14 PM UTC
- Resolved
- Apr 24, 2026, 01:14 PM UTC
- Duration
- —
Affected: Track - AccountsWhat-If - RiskWhat-If - TradesTrack - ChangeForecast - T+1Validate - PositionsTreasury Call Management - Static DataAccess and AuthenticationValidate - OTE/PVTreasury Call Management - WorkflowsTreasury Call Management - ReportingTrack - AttributionRebalance - ScenariosMonitor - AANARebalance - RiskForecast - Fixed Price ShocksForecast - Margin at RiskValidate - OverviewMonitor - SIMMCFaR - Stressed MarginValidate - PositionsCFaR - Stressed MarginAccess and AuthenticationTrack - AccountsTrack - AttributionTrack - ChangeRebalance - ScenariosRebalance - RiskForecast - Fixed Price ShocksForecast - Margin at RiskValidate - OverviewValidate - OTE/PVMonitor - SIMMMonitor - AANATreasury Call Management - WorkflowsTreasury Call Management - Static DataTreasury Call Management - Reporting
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 09:23 AM UTC
- Resolved
- Apr 21, 2026, 09:23 AM UTC
- Duration
- —
Timeline · 2 updates
-
investigating Apr 21, 2026, 07:52 AM UTC
Status: Investigating Status: We have identified an issue that is causing LCH calculations to fail for COB April 20th. Our dev team is urgently investigating and we will provide an update here as soon as possible. Affected components LCH (Cleared IRS) (Full outage)
-
resolved Apr 21, 2026, 09:23 AM UTC
Status: Resolved Status: We have confirmed that the underlying issue is now resolved. This incident is now closed. Problem/Impact: LCH calculations for COB April 20th were failing to calculate IM. Cause: We identified an issue with missing market data. Solution: LCH market data has been reprocessed and impacted calculations have all been retriggered now for the latest valuation date. Affected components LCH (Cleared IRS) (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 02:03 PM UTC
- Resolved
- Apr 20, 2026, 02:03 PM UTC
- Duration
- —
Timeline · 2 updates
-
identified Apr 15, 2026, 08:12 AM UTC
Status: Identified Status: ICE Market Data was made available late by the CCP today, which impacted any calculations triggered before 06:30 AM. Affected runs were processed on T-2 data rather than the most recent market data. Calculations initiated after 06:30 AM completed successfully using the latest available market data. If you require a rerun of any impacted calculations, please contact us at [email protected]: mailto:[email protected] and we will prioritise your request.. Affected components ICE (IRM2) (Partial outage) ICE (SPAN) (Partial outage)
-
resolved Apr 20, 2026, 02:03 PM UTC
Status: Resolved Issue Resolved Affected components ICE (IRM2) (Operational) ICE (SPAN) (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 10, 2026, 01:52 PM UTC
- Resolved
- Apr 10, 2026, 01:52 PM UTC
- Duration
- —
Affected: CMECME
Timeline · 2 updates
-
identified Apr 10, 2026, 09:23 AM UTC
Status: Identified Status: We have identified an issue causing CME ETD IM results to return a 0 value for COB dates 8th and 9th. This is related to a memory issue which has been investigated and appears to now be resolved. We re-running calculations for the impacted dates. Problem/Impact: IM for CME ETD positions calculated by OpenGamma for COB 8th and 9th may be incorrect. These should be corrected in calculation re-runs. Affected components CME (Degraded performance)
-
resolved Apr 10, 2026, 01:52 PM UTC
Status: Resolved Status: The earlier issue with CME ETD calculations has been resolved and re-runs have corrected the initial issue. Affected components CME (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 02, 2026, 03:22 PM UTC
- Resolved
- Apr 02, 2026, 03:22 PM UTC
- Duration
- —
Affected: Treasury Call Management - WorkflowsCFaR - Stressed MarginCFaR - Stressed MarginTreasury Call Management - Workflows
Timeline · 3 updates
-
identified Apr 02, 2026, 01:35 PM UTC
Status: Identified Status: Root cause identified, working on a resolution. Problem/Impact: Some OGP calculations may be failing to complete Affected components Treasury Call Management - Workflows (Degraded performance) CFaR - Stressed Margin (Degraded performance)
-
monitoring Apr 02, 2026, 02:26 PM UTC
Status: Monitoring Status: Fix released, rerunning impacted calculations Problem/Impact: OGP calculations failing to complete Affected components Treasury Call Management - Workflows (Degraded performance) CFaR - Stressed Margin (Degraded performance)
-
resolved Apr 02, 2026, 03:22 PM UTC
Status: Resolved Status: Issue now resolved - Some calculation may still be rerunning. Please contact OG Support at [email protected] if you see any issues with COB 1st Apr calculations. Affected components Treasury Call Management - Workflows (Operational) CFaR - Stressed Margin (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 06:54 PM UTC
- Resolved
- Mar 24, 2026, 06:54 PM UTC
- Duration
- —
Affected: What-If - TradesForecast - T+1
Timeline · 2 updates
-
investigating Mar 24, 2026, 05:42 PM UTC
Status: Investigating Status: We have identified an issue with CME Direct and our Dev team is urgently working on a resolution. We will provide further updates on this page where necessary. Problem/Impact: The issue with CME Direct is preventing OpenGamma calculations from running. This appears to have been occurring since 3pm this afternoon (UK time) and we are aware of it impacting our WhatIf and Forecast modules. Others calculations may also be impacted Affected components What-If - Trades (Partial outage) Forecast - T+1 (Partial outage)
-
resolved Mar 24, 2026, 06:54 PM UTC
Status: Resolved Status: We have confirmed that the issue is now resolved. This incident is now closed. Problem/Impact: Calculations with CME Direct were stuck in progress and unable to complete. This was impacting calculations in the What If Trades screen as well. Solution: A recent change was identified to have caused the issue and has been rolled back by our dev team. Impacted calculations have been rerun and What If server instances restarted. Affected components What-If - Trades (Operational) Forecast - T+1 (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 05:22 PM UTC
- Resolved
- Mar 12, 2026, 05:22 PM UTC
- Duration
- —
Affected: Access and Authentication
Timeline · 3 updates
-
investigating Mar 12, 2026, 05:13 PM UTC
Status: Investigating OGP/OGT UI access is currently disrupted, we are actively investigating root cause and remediation. Affected components Access and Authentication (Partial outage)
-
monitoring Mar 12, 2026, 05:21 PM UTC
Status: Monitoring Update: Service restored Fix Status: Live Affected components Access and Authentication (Partial outage)
-
resolved Mar 12, 2026, 05:22 PM UTC
Status: Resolved Access on OGP has been fully restored and is functioning as expected. Affected components Access and Authentication (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 05:18 PM UTC
- Resolved
- Mar 12, 2026, 05:18 PM UTC
- Duration
- —
Timeline · 2 updates
-
monitoring Mar 12, 2026, 08:15 AM UTC
Status: Monitoring Status: We received ICE IRM2 market data files later than normal this morning. The files have been received and were calibrated around 6.45am. Impacted calculations will be re-run to reflected the updated data. Problem/Impact: Morning calculations will have kicked off defaulting to T-2 data for the impacted IRM2 contracts. As a result IM figures will not be reflective of the latest ICE IRMS2 market data. Affected components ICE (IRM2) (Degraded performance)
-
resolved Mar 12, 2026, 05:18 PM UTC
Status: Resolved ICE Market Data issue resolved Affected components ICE (IRM2) (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 06:17 PM UTC
- Resolved
- Mar 10, 2026, 06:17 PM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →