Subscan incident

Subscan Network Outdated

Critical Resolved View vendor source →

Subscan experienced a critical incident on February 3, 2025, lasting —. The incident has been resolved; the full update timeline is below.

Started
Feb 03, 2025, 02:40 AM UTC
Resolved
Feb 02, 2025, 04:30 AM UTC
Duration
—
Detected by Pingoru
Feb 03, 2025, 02:40 AM UTC

Update timeline

  1. resolved Feb 03, 2025, 02:40 AM UTC

    Due to the node issues of Elastic, there are delays in the blocks of our network.