It's often an issue that a specific DP cannot serve an asset because their QN is out of sync and doesn't know about certain storage object. This is a bit hard to debug from DP lead perspective though, as the only way to notice is to get QN logs. For this reason, we've concluded that it would be nice for the Argus /status endpoint to expose:

1. Last indexed QN block, or some other indication whether QN is "up-to-date"
2. URL of used QN, so that it's easy to tell whether that's remote or local node.