GetBlockNumber randomly returns incorrect low block number

[stuartchris]

Describe the bug Method eth.getBlockNumber() randomly returns incorrect low block number on Polygon mainnet.

To Reproduce Steps to reproduce the behavior:

1. Connect web3 client to public poly-rpc.gateway.pokt.network or private poly-mainnet.gateway.pokt.network/v1/xxx node
2. Call eth.getBlockNumber() once per second monitoring block number returned.
3. Within a few minutes a block number will return that is far behind the current block number, it happens only for a single call, the prior and next call both return correct block numbers. Actual block number sequence returned from Pokt private node with a block number 66 blocks behind the previous block number within one minute of starting the test: 27413792, 27413726, 27413796, 27413799.
4. Incorrect block numbers occur randomly although consistently and the number of blocks it is behind the current block number is random from tens of blocks up to hundreds of blocks.
5. When testing against other RPC providers at the same time they were not observed displaying very low block numbers.

Expected behavior Method eth.getBlockNumber() should return block numbers near the current block number, not block numbers far lower than that.

Server (please complete the following information):

• OS: Ubuntu 18.04.6
• Node.js version: 12.22.12
• Web3 version: 1.7.0

Keep up the great work, truly appreciate all that you do!