OpenGamma Outage History

OpenGamma is up right now

There were 12 OpenGamma outages since February 13, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.opengamma.com

Minor May 1, 2026

LCH Market Data Outage

Detected by Pingoru
May 01, 2026, 11:09 AM UTC
Resolved
May 01, 2026, 11:09 AM UTC
Duration
Timeline · 2 updates
  1. 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)

  2. 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 →

Minor April 24, 2026

Delayed scheduled calculations

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 Margin
Timeline · 2 updates
  1. investigating Apr 24, 2026, 11:23 AM UTC

    Status: Investigating Status: e.g. We have identified an issue with our scheduled calculations and we are urgently working on identifying the root cause. We will keep this page updated. Problem/Impact: Some scheduled calculations that kicked off from around 10am London are stuck in "running" status. Affected components CFaR - Stressed Margin (Partial outage) Rebalance - Risk (Partial outage) SFTP Reporting (Any Module/Screen) (Partial outage) Rebalance - Scenarios (Partial outage) What-If - Risk (Partial outage) Treasury Call Management - Workflows (Partial outage) Track - Change (Partial outage) Forecast - Margin at Risk (Partial outage) Validate - OTE/PV (Partial outage) Treasury Call Management - Static Data (Partial outage) Monitor - AANA (Partial outage) What-If - Trades (Partial outage) Track - Accounts (Partial outage) Validate - Positions (Partial outage) Treasury Call Management - Reporting (Partial outage) Access and Authentication (Partial outage) Forecast - Fixed Price Shocks (Partial outage) Monitor - SIMM (Partial outage) Forecast - T+1 (Partial outage) Track - Attribution (Partial outage) Validate - Overview (Partial outage)

  2. resolved Apr 24, 2026, 01:14 PM UTC

    Status: Resolved Status: We have confirmed that the underlying issue is now resolved and that all stuck calculations have been retriggered around 50mins ago. BAU service is restored. This incident is now closed. Affected components Rebalance - Risk (Operational) What-If - Trades (Operational) Forecast - Margin at Risk (Operational) Forecast - T+1 (Operational) Treasury Call Management - Static Data (Operational) CFaR - Stressed Margin (Operational) Monitor - AANA (Operational) SFTP Reporting (Any Module/Screen) (Operational) Rebalance - Scenarios (Operational) What-If - Risk (Operational) Forecast - Fixed Price Shocks (Operational) Treasury Call Management - Workflows (Operational) Monitor - SIMM (Operational) Track - Change (Operational) Validate - Positions (Operational) Track - Attribution (Operational) Treasury Call Management - Reporting (Operational) Validate - OTE/PV (Operational) Access and Authentication (Operational) Track - Accounts (Operational) Validate - Overview (Operational)

Read the full incident report →

Minor April 21, 2026

LCH Calculations Failing COB April 20th

Detected by Pingoru
Apr 21, 2026, 09:23 AM UTC
Resolved
Apr 21, 2026, 09:23 AM UTC
Duration
Timeline · 2 updates
  1. 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)

  2. 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 →

Minor April 20, 2026

Late ICE Market Data

Detected by Pingoru
Apr 20, 2026, 02:03 PM UTC
Resolved
Apr 20, 2026, 02:03 PM UTC
Duration
Timeline · 2 updates
  1. 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)

  2. 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 →

Minor April 10, 2026

CME ETD IM attribution calculations

Detected by Pingoru
Apr 10, 2026, 01:52 PM UTC
Resolved
Apr 10, 2026, 01:52 PM UTC
Duration
Affected: CME
Timeline · 2 updates
  1. 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)

  2. 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 →

Minor April 2, 2026

OGP Calculation Performance Degraded

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 Margin
Timeline · 3 updates
  1. 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)

  2. 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)

  3. 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 →

Minor March 24, 2026

CME Direct issue impacting OpenGamma margin calculations

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
  1. 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)

  2. 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 →

Minor March 12, 2026

OGP UI Access Disrupted

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
  1. 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)

  2. monitoring Mar 12, 2026, 05:21 PM UTC

    Status: Monitoring Update: Service restored Fix Status: Live Affected components Access and Authentication (Partial outage)

  3. 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 →

Minor March 12, 2026

ICE IRM2 late market data files impacting morning calculations

Detected by Pingoru
Mar 12, 2026, 05:18 PM UTC
Resolved
Mar 12, 2026, 05:18 PM UTC
Duration
Timeline · 2 updates
  1. 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)

  2. 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 →

Minor March 10, 2026

Late ICE IRM2 market data publication

Detected by Pingoru
Mar 10, 2026, 06:17 PM UTC
Resolved
Mar 10, 2026, 06:17 PM UTC
Duration
Timeline · 2 updates
  1. monitoring Mar 10, 2026, 11:17 AM UTC

    Status: Monitoring Status: We have received ICE IRM2 market data files late this morning which has impacted the figures produced in our morning calculations. The file has now been received and we are re-running morning calculations again. Problem/Impact: ICE data in morning calculations has defaulted to T-2, so figures will not be reflective of latest market data. We are re-running calculations again to correct this which should resolve the issue and bring figures back in line. Affected components ICE (IRM2) (Degraded performance)

  2. resolved Mar 10, 2026, 06:17 PM UTC

    Status: Resolved Status: e.g. We have confirmed that the underlying issue is now resolved. This incident is now closed. Problem/Impact: [Describe what isn't working as expected and what the problem affects - be specific about the kind of problematic behaviour(s) clients will see if they are affected, and what determines whether they'd be affected or not] [IMPORTANT: Clarify if there is any persistent impact of the incident - e.g. if we have not received the necessary market data to re-run calculations for a given valuation date and historical calculation accuracy may still be affected] Cause: [Give a general explanation of what caused the issue e.g. a recent code change, missing or stale market data - avoid using internal OpenGamma jargon and don't provide unnecessary/meaningless detail] Solution: [Give a general explanation of how we resolved the issue (avoiding jargon/too much detail) and how robust the solution is - where possible, provide assurance that the problem will not resurface] Affected components ICE (IRM2) (Operational)

Read the full incident report →

Minor March 5, 2026

LCH CDS API Connectivity Issues

Detected by Pingoru
Mar 05, 2026, 09:16 AM UTC
Resolved
Mar 05, 2026, 09:16 AM UTC
Duration
Timeline · 2 updates
  1. investigating Mar 02, 2026, 09:36 AM UTC

    Status: Investigating Status: We have identified an issue with LCH CDS calculations and we are urgently working on identifying the root cause. We will keep this page updated. Problem/Impact: This is impacting overnight margin calculations for LCH CDS (results returning zero IM) & unsuccessful results for LCH CDS API queries. Affected components LCH (Cleared CDS) (Full outage)

  2. resolved Mar 05, 2026, 09:16 AM UTC

    Status: Resolved Status: We have confirmed that the underlying issue is now resolved. This incident is now closed. Problem/Impact: Authentication to the LCH CDS API was failing. Cause: Duplicate authentication logic in our backend post a code change. Solution: Code change required to fix the underlying issue. Affected components LCH (Cleared CDS) (Operational)

Read the full incident report →

Minor February 16, 2026

LCH MXN OIS Outage

Detected by Pingoru
Feb 16, 2026, 11:43 AM UTC
Resolved
Feb 16, 2026, 11:43 AM UTC
Duration
Timeline · 2 updates
  1. investigating Feb 13, 2026, 04:51 PM UTC

    Status: Investigating Status: An issue has been identified with LCH's MXN OIS market data, at present MXN OIS exposure at LCH is not being calculated. Cause: This is an upstream market data issue from the LCH which we are liaising directly with them to resolve. We will provide a further update when we have received confirmation from LCH. Affected components LCH (Cleared IRS) (Partial outage)

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

    Status: Resolved Status: An issue was identified on LCH's MXN OIS market data for business date 12th February. The CCP has now resolved this issue. Problem/Impact: The missing data caused margin calculation figures for these products to be 0/error. Cause: LCH market data did not contain the relevant information for these products. Solution: OpenGamma contacted LCH who have now implemented a fix and market data for COB 13th February now contains all necessary information. We have asked the LCH to re-publish for 12th. This is pending LCH to action. Affected components LCH (Cleared IRS) (Operational)

Read the full incident report →

Looking to track OpenGamma downtime and outages?

Pingoru polls OpenGamma's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when OpenGamma reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track OpenGamma alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring OpenGamma for free

5 free monitors · No credit card required