Operational Availability

Service Performance

As the UK bond CT progresses, we will be updating this page with relevant incident details and Root Cause Analyses.

Our incident classification outlines how ETS Connect UK responds to security and operational incidents to reduce disruption, recover quickly, maintain regulatory compliance, and continuously improve our processes.

Service Notice – ETS Connect Plus – API Disruption

14 July 17:00

On 13 July 2026, ETS Connect Plus experienced a disruption to one of its API services, affecting the period between 00:00 UTC and 14:51 UTC. The disruption was resolved at 14:51 UTC, and the data feed has operated normally since that time.

ETS Connect UK has confirmed that its own service continued to operate as normal throughout the period.

Resolved live market data issues relating to ETS Connect UK data

7 July 14:30

Bloomberg’s redistribution of UK consolidated tape trade data has recommenced for trades dated 6 July 2026 onward. Historical data for affected trades dated 1-3 July 2026 is being restored and will be added as it becomes available.

In case of questions please reach out to Bloomberg directly.

6 July 13:30

Bloomberg has identified a potential remaining issue that could affect some UK CT trade prints on the consolidated tape redistributed by Bloomberg. As a precaution, Bloomberg has temporarily suspended redistribution of UK CT trade data while this issue is being resolved.

Bloomberg has asked that any client queries on this topic be directed to Bloomberg support.

This notice will be updated again when Bloomberg’s redistribution of the UK consolidated tape has recommenced.

6 July 2026, 11:00

As of UK market open on Monday, 6 July 2026, Bloomberg has confirmed that the underlying issue has been resolved, and that their redistribution of the UK consolidated tape has recommenced with correct trade sizes showing.

Bloomberg has asked that any client queries on this topic be directed to Bloomberg support.

3 July 2026, 18:00

On 2 July 2026, a market participant raised a query regarding the notional values of a number of emerging market credit trade prints on the consolidated tape redistributed by Bloomberg, which appeared larger than expected.

ETS Connect UK initiated an investigation. Validation against the CTP GUI, API, and CSV outputs confirmed that the notional values held and published by the CTP were correct. The values queried on Bloomberg were observed to be approximately 100 times the corresponding CTP-published figures, indicating that the discrepancy arose outside the CTP’s own data holding and dissemination processes, which have been verified as accurate.

ETS Connect UK is in contact with Bloomberg. Bloomberg has temporarily stopped distributing UK CTP trade data for trades dated 1 July 2026 onward, and will restore corrected data as soon as possible.

Bloomberg has asked that any client queries on this topic be directed to Bloomberg support.

Incident Details and Root Cause Analyses

Date of Incident	Name of Incident	Severity	Duration	Root Cause Analysis (RCA)

Incident Classification

Incidents are categorised based on severity, impact, and regulatory implications.

Incident Level	Description	Time to resolution
“Priority 1 Incident“	means an Incident which, in the reasonable opinion of the Authority has caused, or may cause: (a) a complete loss or severe disruption to a Service; (b) a complete loss or server disruption of business-critical functionality in any part of the Core Services; (c) 50% or more Licensees affected; (d) a high level of reputational damage impacting public confidence in the Authority; (e) the publication (by suppliers or the media) of security vulnerabilities that could severely impact Services; (f) the Authority otherwise determines the Incident has an ‘Impact’ of 1; or (g) no workaround is available.	[Resolved within 2 hours]
“Priority 2 Incident” (or “High Priority Incident“)	means an Incident which, in the reasonable opinion of the Authority, has caused or has the potential to cause: (a) a complete loss of, or severe disruption to, the Core Services; (h) between 20% and 49% of Licensees are affected; (i) a high level of reputational damage impacting public confidence in the Authority; (j) numerous (more than 35) Licensee reports of viruses, phishing emails or other security concerns; or (k) alerts from security systems (including but not limited to firewalls, intrusion detection systems and Internet gateways) that, in the opinion of the Authority, require further investigation; (l) the Authority otherwise determines the Incident has an ‘Impact’ of 2; or (m) no workaround is available or is difficult to implement.	[Resolved within 4 hours]
“Priority 3 Incident“	means an Incident which, in the reasonable opinion of the Authority, has caused or has the potential to cause: (a) between 5% and 19% of Licensees to be impacted; (n) reputational damage to the Authority (but not a high level of reputational damage); or (o) several (between 2 and 35) Licensee reports of viruses, phishing emails or other security concerns reported as individual Incidents of as a collective group; (p) the Authority otherwise determines the Incident has an ‘Impact’ of 3; or (q) a workaround is available.	[Resolved within 10 hours]
“Priority 4 Incident“	means an Incident which, in the reasonable opinion of the Authority has the potential to have a minor adverse impact on the provision of the Services to Licensees, including: (a) a minor issue which, whilst inconvenient, has an agreed workaround to alleviate the impact to the Licensees; (b) where less than 5% of Licensees are impacted; or (c) where a single Licensee reports viruses, phishing emails or other security concerns, (d) which in each case will not cause any reputational damage to the Authority; (e) the Authority otherwise determines the Incident has an ‘Impact’ of 4; or (f) all users have workarounds.	[Resolved within 20 hours]