Subscan incident

Subscan Service Down

Notice Resolved View vendor source →

Subscan experienced a notice incident on May 9, 2026 affecting Subscan Polkadot API and Subscan Kusama API and 1 more component, lasting 2h 21m. The incident has been resolved; the full update timeline is below.

Started
May 09, 2026, 06:28 AM UTC
Resolved
May 09, 2026, 08:50 AM UTC
Duration
2h 21m
Detected by Pingoru
May 09, 2026, 06:28 AM UTC

Affected components

Subscan Polkadot APISubscan Kusama APISubscan Karura APISubscan Moonbeam APISubscan Westend APISubscan Moonriver APISubscan Canary-Matrix APISubscan Altair APISubscan Acala APISubscan Manta API

Update timeline

  1. identified May 09, 2026, 06:28 AM UTC

    The issue has been identified and a fix is being implemented.

  2. identified May 09, 2026, 07:40 AM UTC

    Subscan is currently conducting routine maintenance on historical block data. During this maintenance period, your user experience may be affected as follows: 1. You will temporarily be unable to view or search historical block data (including details of past blocks, historical transaction records, and other non-real-time block-related information); 2. Latest block data (such as real-time block information and latest transaction records) will remain unaffected, and you can view and access it normally. Once the maintenance is completed, the query function for historical block data will be automatically restored without requiring any additional actions from you. Any updates on the maintenance progress or special adjustments will be synced via the Subscan Status Page as soon as possible. We recommend you follow the page for the latest updates.

  3. monitoring May 09, 2026, 08:38 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 09, 2026, 08:50 AM UTC

    This incident has been resolved.