Thank you for identifying and sharing the issue you were having with Archive data access in certain block ranges. Please retry your query now, we have identified the source of the issue and for the blocks we tested, have resolved it.
I’m getting the same error “Returned error: header not found” for any .call() with a blockNumber over websockets (archive add-on is on). If it helps, I’m calling with a n - 1 block number