Is there a current Eikon API outage?

I'm consistently receiving Error Code 500 and cannot retrieve any data, regardless of how many attempts I make. Has this issue been reported or acknowledged?

With thanks,

Find more posts tagged with

error-500

#technology

Accepted answers

All comments

Jirapongse

@capmworks

Thank you for reaching out to us.

I am using it and it works fine.

Can you share the runnable code that you are using?

capmworks

Hi Jirapongse,
Thanks for getting back so quickly.
I have issue fetching data using ek.get_data
data, err = ek.get_data(
instruments='AAPL.O',
fields=['TR.CLOSEPRICE'],
parameters={
'SDate': '2023-01-01',
'EDate': '2023-12-31',
'Frq': 'D'
}
)
[{'code': 500, 'col': 1, 'message': 'The unexpected error occurs during data collection.', 'row': 0}]

johnma99

Hi. I'm also encountering similar issues. I received "LDError: The unexpected error occurs during data collection."

Jirapongse

The same error happens in the LSEG Workspace Excel.

You need to contact the helpdesk team directly via LSEG Support to report this issue.

laurens

Confirmed partial outage – Eikon/Workspace Data API – West Europe region – 27 Nov 2025

Hi all,

I’m the author and maintainer of the refinitiv R package and have been using the Eikon/Workspace Data API daily for many years.What we’re experiencing right now in West Europe is unequivocally a backend outage – not a client-side or authentication issue.

Current status (as of ~11:00–13:00 UTC, 27 Nov 2025):

All DataGrid_StandardAsync requests (fundamentals, snapshots, symbology, etc.) are failing consistently with internal 5001/5002 errors during the data-collection phase, even for the smallest possible requests.

Example failing call via rd_GetData:

Refinitiv::rd_GetData(  rics = c("MMM", "III.L"),  Eikonformulas = c("TR.PE(Sdate=0D)", "TR.CompanyName"),  verbose = TRUE)

Exact JSON payload that is sent to the local proxy and then forwarded to the West Europe backend (200 OK from proxy, but backend explodes):

JSON

{  "E": "DataGrid_StandardAsync",  "W": {    "requests": [      {        "instruments": ["MMM", "III.L"],        "fields": [          { "name": "TR.PE(Sdate=0D)" },          { "name": "TR.CompanyName" }        ]      }    ]  }}

URL: http://localhost:9000/api/udf/ (or 9001 depending on your setup) → 200→ followed immediately by:

text

5001 The unexpected error occurs during data collection.035002 The unexpected error occurs during data collection.035001 The unexpected error occurs during data collection.135002 The unexpected error occurs during data collection.13

By contrast, timeseries requests via the dedicated TimeSeries endpoint are working perfectly (tested with 5+ years of daily data, chunked requests complete without error).

Will keep this thread updated as soon as I have an official acknowledgement or ETA.

Thanks, Laurens van der Burg Author & maintainer – refinitiv R package

Jirapongse

I tested it and it is working now.

laurens

RESOLVED – Eikon/Workspace Data API (West Europe) fully working again – 27 Nov 2025

Hi all,

Happy to report that as of right now, 11:17 CET (Zurich), the DataGrid_StandardAsync endpoint in West Europe is back to normal behaviour.All 5001/5002 internal errors have disappeared and data is being returned instantly again.

Just confirmed with a fresh call:

Eikon <- Refinitiv::EikonConnect()

ex1 <- Refinitiv::EikonGetData(  EikonObject = Eikon,  rics = c("MMM", "III.L"), 

 Eikonformulas = c("TR.PE(Sdate=0D)/*P/E (LTM) - Diluted Excl*/", "TR.CompanyName"),  verbose = TRUE)

Result (11:17 CET):

text

the operation you intend to perform will cost 4 data points

http://localhost:9001/api/udf/ → 200→ 

data returned immediately  

Instrument P/E.(Daily.Time.Series.Ratio) Company.Name1        

MMM                      27.29306        3M Co2      

III.L                       5.06041  3i Group PLC

Same success with rd_GetData on port 9000.

Summary:

TimeSeries and Symbology were never affected
DataGrid_StandardAsync (fundamentals, estimates, etc.) was completely down for several hours this morning in West Europe
As of ~11:15–11:17 CET everything is fully operational again

Still waiting for an official explanation from LSEG, but functionally we’re all good.

Thanks to everyone who raised tickets – the more reports, the faster these get fixed!

Back to work!

Cheers,Laurens
Author & maintainer – refinitiv R package
https://github.com/GreenGrassBlueOcean/RefinitivR

capmworks

Thank you all! Yes, it's working. Back to work!

EXPLORE OUR SITES