For QQQ the below was the last data feed received (time in UTC) today
[{‘T’: ‘b’, ‘S’: ‘QQQ’, ‘o’: 502.36, ‘h’: 502.36, ‘l’: 502.36, ‘c’: 502.36, ‘v’: 279, ‘t’: ‘2025-03-03T18:32:00Z’, ‘n’: 13, ‘vw’: 502.36}]
I believe this was an issue with IEX? Did anyone else experience this issue?
Hi 
It doesn’t look like there’s an issue with IEX. You can check it both on the latest endpoint:
$ curl -s -H "APCA-API-KEY-ID: ${APCA_API_KEY_ID}" -H "APCA-API-SECRET-KEY: ${APCA_API_SECRET_KEY}" "${APCA_API_DATA_URL}/v2/stocks/bars/latest?symbols=QQQ&feed=iex" | jq .
{
"bars": {
"QQQ": {
"c": 497.35,
"h": 497.39,
"l": 496.865,
"n": 390,
"o": 497.13,
"t": "2025-03-03T20:59:00Z",
"v": 61194,
"vw": 497.10626
}
}
}
and on the historical one:
$ curl -s -H "APCA-API-KEY-ID: ${APCA_API_KEY_ID}" -H "APCA-API-SECRET-KEY: ${APCA_API_SECRET_KEY}" "${APCA_API_DATA_URL}/v2/stocks/bars?symbols=QQQ&feed=iex&timeframe=10Min&start=2025-03-03T18:30:00Z" | jq -r '.bars.QQQ[] | .t'
2025-03-03T18:30:00Z
2025-03-03T18:40:00Z
2025-03-03T18:50:00Z
2025-03-03T19:00:00Z
2025-03-03T19:10:00Z
2025-03-03T19:20:00Z
2025-03-03T19:30:00Z
2025-03-03T19:40:00Z
2025-03-03T19:50:00Z
2025-03-03T20:00:00Z
2025-03-03T20:10:00Z
2025-03-03T20:20:00Z
2025-03-03T20:30:00Z
2025-03-03T20:40:00Z
2025-03-03T20:50:00Z
This suggests that the issue must have been on your end.