Wrong transaction count/nonce returned from RPC.

Incident Report for Aurora

Resolved

This incident has been resolved.

Posted Sep 16, 2022 - 01:05 UTC

Update

Data re-indexing has been completed.

Posted Sep 16, 2022 - 01:04 UTC

Update

We are continuing to monitor for any further issues.

Posted Sep 05, 2022 - 13:39 UTC

Monitoring

Some small amount of EOAs will receive wrong transaction count from the RPC and not be able to make transactions using the derived nonce.
The root cause of this is an indexing error that has been identified and fixed, but re-indexing of the chain will take until Sept 9th.
Until then, users can manually set the nonce to a correct value for one transaction, after which the RPC will return the correct value going forward.

Posted Sep 05, 2022 - 13:38 UTC

This incident affected: Mainnet RPC.