Problems with callHandlers on Ropsten
Incident Report for The Graph
Investigating
We are currently seeing problems with callHandlers on Ropsten. Given the uncertainty about the support of Ethereum testnets we highly advise developers to migrate their contracts and subgraphs to Goerli as soon as possible.

Affected subgraphs show the following logs:

```
Trying again after trace_filter RPC call for block range: [12326064..12326064] failed (attempt #10) with result Err(RPC error: Error { code: ServerError(-32000), message: "could not find block 0000000000000000000000000000000000000000000000000000000000000000 12326064", data: None } Caused by: Server error: could not find block 0000000000000000000000000000000000000000000000000000000000000000 12326064), component: BlockStream
```

And

```
Trying again after trace_filter RPC call for block range: [12326066..12326066] failed (attempt #10) with result Err(RPC error: Error { code: InternalError, message: "hash 4dd5bd7e4dc3a95da925384c3bc45efcd37f3c75d6f2d99f7f2d34ca9a8c99e8 is not currently canonical", data: None } Caused by: Internal error: hash 4dd5bd7e4dc3a95da925384c3bc45efcd37f3c75d6f2d99f7f2d34ca9a8c99e8 is not currently canonical), component: BlockStream
```
Posted Jun 03, 2022 - 01:48 UTC
This incident affects: Hosted Service - Indexing (Ropsten).