Hi! Sergey from P2P.org here, I’m responsible for the operations of the indexer in question.
The allocation in question was closed using standard indexer-agent behaviour, POI was obtained automatically by indexer-agent. We are using official images of indexer stack (indexer-agent and graph-node). Database has not been tampered with and we do not do any modifications to the databases manually.
I’ve double checked the POI of the subgraph deployment and still received 0xcf490b576f194303816d691570c674a22c4632ccd978d2f31aa1b23a07f539a4 as the result.
We’ve raised issues with POI consistency in the past and we are not the only indexer experiencing issues with subgraphs suddenly starting to diverge in POIs. We’ve got confirmation from Ørjan on IOH that the closing of the allocations with diverging POI caused by graph-node issue should not be slashed.
I am happy to provide any additional information needed for further investigation.