Asset Hub Polkadot RPC nodes failing chain_getHeader calls

Ecosystem
1

Given a curl request like this:

{"id":10,"jsonrpc":"2.0","method":"chain_getHeader","params":["0d01b491c11307c984a3d84cf7523df1e2c2a5021155f3f2976d8dbcdc3e0765"]}

I’m seeing either "result":null or the proper result which is:

{"jsonrpc":"2.0","id":10,"result":{"parentHash":"0x01a64ca06df2340739c779f3f0080ad4d209ecf0b5ac3ad17c21453fe8a6579b","number":"0x11b6f9c","stateRoot":"0x284d8f91b8666708f5641ad9b90fbd8b2d742859d7b4197e46a5dc55c3d7711a","extrinsicsRoot":"0x632e3d97bd304deb647f2720c44a62914680ce4e591f4c6372fe4d0c090ef160","digest":{"logs":["0x06434d4c53100100010c","0x06434d4c530c020001","0x066175726120b8c36e0400000000","0x0452505352901800e8e8d560bf81c5a85e3e2a9773a3cbb465d2f3b0be19d2861e237427c663c29baf07","0x05617572610101e375f636fcc7486ba0cf58781722e58d2fe613ae1dc273c3b1b504b6d427950839ec3d9ea68a0bff158d69966ec9db7e479f9b8a3c40fb3ae23e43fa5f516f0a"]}}}

This is using the endpoint: https://polkadot-asset-hub-rpc.polkadot.io

This is a very serious bug because a lot of wallet software will require this information when building stuff like the mortality period.

I hope this issue eventually reaches the correct people, so they can fix this.

This block provably exists here: Subscan | AssetHub Polkadot Block Details

2

I think the parity endpoint is hitting some rate limit:

# curl https://polkadot-asset-hub-rpc.polkadot.io

Too many connections. Please try again later

Its also not working on polkadot.js because of this.

Also posted this on the polkadot element room so hopefully some of the devs can pick it up.

3

Try Rotko, Gatotech and Luckyfriday RPCs depending on location, they seem to be resolving the limits more gracefully or having no limits altogether.

4

I also heard the stakeworld’s rpc’s are very good and without rate limiting (except for real misusage) :upside_down_face:

5

I got notice on the element room it should be fixed now.

6

correct, the connection cap on the two pods behind polkadot-asset-hub-rpc.polkadot.io has been raised significantly and the issue should be fixed.

—