Related Alerts

• l1-replica-divergence

Alert Severity

Severity depends on user impact. See ‣ for the appropriate severity level.

Alert Summary

This alert means that an L1 replica has diverged from the reference. The reference is usually an L1 infrastructure provider like Alchemy or Infura. This alert will fire when the L1 replica’s canonical chain does not match the reference for more than 5 minutes.

Investigation

1. View the Replica Healthcheck dashboard to check if the replica is currently diverged. The red band on the graph below indicates a divergence.

   

2. View the Geth dashboard to check if a reorg occurred. Spikes in the following graphs indicate a reorg:

   

Check for this: Possible rollup config divergence

A node (op-node) with a different rollup config can potentially diverge especially when wrongfully configured with incorrect hardfork times

• Clearly because it’s common for the block derivation logic to change with hardforks, therefore drifting hardfork times can cause diverging block derivations.

Use the optimism_rollupConfig RPC against the op-node URL of the diverged node and the reference node to get their rollupConfig details, and compare them.

• SCR or any k8s config individually aren’t reliable depictions of the rollupConfig of an op-node because rollupConfig tends to be a combination of SCR, certain env vars as well as the rollupConfig field override.

For example

cast rpc --rpc-url=https://arena-z-opn-geth-a-rpc-1-op-node.primary.sepolia.prod.oplabs.cloud optimism_rollupConfig