Zilliqa network has recently experienced a number of operational disruptions, impacting block production on its mainnet. However, as of May 10, full network functionality has been restored — though the cause is still under investigation.

The Zilliqa team notified the community that the network was now online following “temporary disruptions to block production on mainnet.” With network functionality restored, the infrastructure team is continuing to “monitor the stability of the network as it works to diagnose the underlying cause of the recent disruptions.”

Source: https://twitter.com/zilliqa/status/1788860703492727290

Since the initial signs of disruption on May 8, when a slowdown in block generation was identified, the Zilliqa network technical team has remained active for almost 48 hours, aiming to prevent further disruptions.

On May 9 at around 9:30 am UTC, the Zilliqa technical team discovered a malfunction that returned a null value “instead of a node’s RLP following a possible invalid database lookup.”

“The team has created internal rehearsal networks to recreate this issue and trial bug fixes, allowing for possible solutions to be tested within an isolated environment before progressing to Testnet and mainnet deployments.”

By around 2:30 pm UTC on May 9, the team had restored full functionality through a fix, alongside the rollout of the Zilliqa version 9.3.4 network upgrade. The team noted that the upgrade would include “a number of enhancements to EVM compatibility” and apologized for the inconvenience caused to users and the Zilliqa community.

However, despite the fix and upgrade rollout, a further disruption to block production hit the Zilliqa mainnet again on May 9 around 7:05PM UTC. At this point the team enhanced debugging processes to better diagnose the issue and address the root cause of the disruption.

This is not the first time Zilliqa block production has been hit with disruptions due to technical issues. In December 2023, an “interruption to block production” saw daily Zilliqa blockchain transactions plunge roughly 50% — from around 61,000 to 30,906.

The Zilliqa team is continuing to investigate the underlying cause of the recent network disruptions and thanks the community for their “patience and support during the course of resolving” the issue.