Paradex Experiences Service Disruption Following Chain State Rollback

NftDeepBreather · 2026-03-05T19:14:32+00:00

In mid-January, Paradex faced a significant outage requiring a rollback to block 1604710, affecting key services and user access. The team restored accounts to pre-incident status and is investigating the cause to prevent future issues.

NftDeepBreather

2026-03-05 19:14:32

Abstract generation in progress

Paradex encountered a significant technical incident in mid-January, forcing the platform to take all services offline while executing a comprehensive chain state rollback. The disruption affected multiple critical infrastructure layers simultaneously, leaving users unable to access the platform’s core functionality.

What Services Were Impacted

The outage extended across the entire Paradex ecosystem, with the Cloud/API infrastructure, web UI, blockchain components, bridge functionality, block explorer, and RPC proxy all rendered unavailable. This broad-based disruption underscored the interconnected nature of the platform’s technical architecture, making simultaneous recovery essential for restoring normal operations.

The Rollback Mechanism: Block 1604710

To address the underlying issue, the Paradex team executed a chain state rollback to block height 1604710, timestamped at 04:27:54 UTC. This represented the most recent confirmed stable state prior to the database maintenance event that triggered the malfunction. By reverting to this earlier block state, the platform effectively erased any corrupted data or inconsistent entries introduced during the maintenance window.

Account Recovery and Status

All user accounts were systematically restored to their pre-maintenance status, ensuring that holdings, positions, and transaction histories remained intact. The rollback mechanism, while disruptive in the short term, protected the integrity of user assets by eliminating any anomalous state changes that occurred during the problematic period.

Investigation and Resolution Progress

At the time of the announcement, Paradex officials indicated the root cause had been identified and containment measures were underway. However, the complete resolution remained under active investigation, with the team working to implement fixes and prevent similar occurrences through enhanced database management protocols and system monitoring.

This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.