Around 8:00 Kyiv time (9:00 MSK), the L2-solution zkSync Era halted block production at height #22 364 805 due to an unforeseen error.
Around 14:00 the protocol resumed operation. Developers said the outage was caused by an error on one of the servers, triggering the security protocols.
The zkSync Era network is now fully operational. At 05:50 UTC, one of the network’s automated safety protocols was triggered by a bug in the server. This issue required teams to inspect and is now fully resolved.
We will share a full post-mortem report soon. Thank you for your…
— zkSync Developers (∎, ∆) (@zkSyncDevs) December 25, 2023
As of writing, the protocol has been non-operational for more than four hours. The project developers confirmed ‘network issues’.
zkSync Era is currently encountering network issues.
Teams are actively addressing the situation and are committed to resolving it as swiftly as possible.
We will share a post-mortem report once the issue has been fully addressed and analyzed.
For updates:…
— zkSync Developers (∎, ∆) (@zkSyncDevs) December 25, 2023
“The team is actively looking into the situation and strives to resolve it as quickly as possible. We will publish a report once the error is fully fixed and analyzed,” the statement says.
ZkSync Era faced a similar issue on December 16. In the wake of the launch of the Ordinals analogue, the number of transactions per second exceeded 150, which caused congestion and a 15-minute network outage.
On December 16, an inscription event on zkSync Era caused a large increase in transactions over a period of 38 hours. For nearly 14 hours straight, the network handled ~150 TPS — peaking at 187 TPS — with an average tx cost of ~$0.12.
Here are the details and our learnings ⬇️… pic.twitter.com/6m957bl96Q
— zkSync Developers (∎, ∆) (@zkSyncDevs) December 19, 2023
The protocol’s operability was restored after a restart. At the time the developers identified three main problems:
- low database throughput, which hampered monitoring during periods of heightened load;
- UI errors where completed transactions were displayed as pending;
- a lagging block explorer.
On December 15, the Arbitrum One L2-solution stopped processing transactions due to a significant surge in network traffic. The network’s operability was restored in under two hours.
Earlier in the month, The Open Network’s throughput slowed to one transaction per second due to a fault triggered by the popularity of the Ordinals analogue.