Digital Asset
Intelligence
Security Incident · zkSync Ecosystem

zkSync Downtime

·Historical incident record

Incident Overview

According to official news, the zkSync team announced the cause of the downtime on Twitter. Block generation stopped due to a block queue database failure. Despite this, the server API was not affected. Transactions continue to be added to the mempool, and queries are served normally. Although all components had comprehensive monitoring, logging, and alerting, no alerts were triggered because the API was functioning properly.

Sources & References

This record presents information attributed to the linked sources. Incident dates describe the original event, not a new report. Reported loss figures reflect the source record and are not current market valuations.

More Security Incidents

View All →
  1. Incident date
    Target

    ZkSync

    Attack methodAccount Compromise
    Reported lossNot disclosed
  2. Incident date
    Target

    ZKsync

    Attack methodPrivate Key Leakage
    Reported loss$ 5,000,000
  3. Incident date
    Target

    ZKsync

    Attack methodAccount Compromise
    Reported lossNot disclosed
  4. Incident date
    Target

    Degen Zoo

    Attack methodUnknown
    Reported lossNot disclosed
  5. Incident date
    Attack methodPhishing Attack
    Reported loss$ 3,830,000