Dear Support Team,
I am reporting a significant performance degradation and intermittent service failures when using the Refinitiv Data Library for Python, which began on January 15, 2026, and persists as of today, January 16.
Context
Prior to January 15, the system performed optimally. Our current workflow processes 42 financial assets (RICs) with 3 time points each (Today, Yesterday, -5 business days), totaling 126 queries per cycle.
Technical Issues Identified
1. Batch Call Failures (Error Code -1)The method rd.get_history() consistently fails when querying multiple RICs in a single batch.
- Error Message: "Error code -1 | Unable to collect data for the field '[FIELD]' and some specific identifier(s)"
- Highly Affected RICs: *
*Indices: .FTEMUSDGBIUSDT, .TRXFLDARP, .TRXFLDBRP, .TRXFLDMXP, .TRXFLDCLP, .TRXFLDCCP, .TRXFLDINP, .DXY
* Bonds: US10YT=RR, US2YT=RR, GB2YT=RR (intermittent)
* CDS: Full batches fail randomly.
* Currencies: EUR=, JPY=
2. Intermittent Latency Response times have become highly volatile, ranging from 0.2s to several minutes. We are experiencing hangs without triggering standard timeouts.
3. Data Inconsistency We have observed that individual queries often succeed for a specific RIC while the same RIC fails within a batch call. Furthermore, the data remains available via Eikon/Workspace Desktop, confirming the issue is isolated to the API layer.
Metrics & Impact
- Success Rate: Dropped from ~100% to ~76%.
- Processing Time: Increased from ~1 minute to over 4 minutes.
- Data Integrity: Approximately 24% of historical values are currently unrecoverable via API.
Environment & Troubleshooting
- Library: Refinitiv Data Library (Python) - Latest version.
- Methods:
rd.get_history(), rd.get_data(). - Platform: Windows 10, Python 3.x.
- Session: Active and authenticated via Eikon/Refinitiv Workspace.
- Temporary Workaround: We have transitioned to one-by-one processing with 100ms delays, which is inefficient for our production requirements.
Request
Please investigate if there is a known service degradation, infrastructure issues on historical data servers, or recent changes to rate-limiting/throttling policies that might be affecting our AppKey/Session.
I look forward to your technical assessment.
Best regards,