Update: We have now published our complete post mortem with more details, available here.
On June 1, 2026, at around 15:00 UTC, the Hemi Engineering Team identified a critical Hemi Network issue that requires anyone running a Hemi Node to update in order to restore functionality.
The issue caused nodes to halt at block 4538215. We’ve fixed the issue and instructions are available below for anyone who is running a node. Users who are not running a node do not need to take any action.
All nodes operated by Hemi, including the primary public RPC node (https://rpc.hemi.network/rpc), have been updated and the network is continuing to progress as normal.
If you are using a third-party RPC node and experiencing issues, you may want to update your RPC endpoint to https://rpc.hemi.network/rpc temporarily while partners deploy the fix.
We have restored the network, and everything is now operating as normal. We are still verifying the root cause and will publish a full post mortem once our investigation is complete.
Node Operators
If you are a node operator, follow the steps below to restore full functionality:
If you are using hemilabs/hemi-node:
Update hemilabs/hemi-node repository to commit f517abbd80fa201ec70131b5403272139b234a77
Restart all containers with Docker compose down, then Docker compose up.
Other setups:
If you are running op-geth in a container, update your Hemi
op-gethimage to:ghcr.io/hemilabs/op-geth:05d4d8f@sha256:92d14f0b4b89947352d57743ce9e7f2d9c9e495f0bb861a24d21c49d391c7abfIf you are compiling directly from source, fetch commit
05d4d8ffrom GitHub and rebuild.
No changes to the op-geth configuration files or flags are required.
What Happens Next
We are continuing to investigate and verify the root cause. A full technical post mortem will be published once our investigation is complete.