[Bug] Indexer Status Endpoint Returns Empty Array 0.41.0 #6208
Description
Bug report
After upgrading to 0.41.0, the status endpoint no longer returns a list of deployed subgraphs and their statuses. Downgrading to 0.40.1 fixes the issue right away. This doesn't seem to affect the gateway, which may be using another method of gathering the status of a subgraph, but this does affect other tools built by the community.
Relevant log output
$ curl -i -H 'Content-Type: application/json' -X POST -d '{"query": "{ indexingStatuses { subgraph synced health entityCount fatalError{ message deterministic block{ hash number } } node chains{ latestBlock{number} chainHeadBlock{number} earliestBlock{number} } } }"}' http://graph-mainnet-node-graph-node-index:8030/graphql
HTTP/1.1 200 OK
access-control-allow-origin: *
content-type: application/json
content-type: application/json
access-control-allow-headers: Content-Type, User-Agent
access-control-allow-methods: GET, OPTIONS, POST
graph-attestable: true
graph-indexed: null
content-length: 32
date: Tue, 04 Nov 2025 20:01:47 GMT
{"data":{"indexingStatuses":[]}}IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out
- Tick this box if this bug is caused by a regression found in the latest release.
- Tick this box if this bug is specific to the hosted service.
- I have searched the issue tracker to make sure this issue is not a duplicate.
OS information
Linux