Subscan logo

Is Subscan Down?

AnalyticsLive status, outages, and incident history

No. Subscan is up right now.

Every monitored Subscan system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 8m agoLive · every 60s

Know the moment Subscan breaks

Subscan is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Subscan status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Subscan Status Summary

As of 19:34 UTC on 14 November 2026, Subscan is operational. PulsAPI checked Subscan's official status page and found 102 of 102 components operational, with no active incidents.

Cite as: PulsAPI, “Subscan status”, checked 14 November 2026, 19:34 UTC. https://www.pulsapi.com/services/subscan

Subscan Component Status

The main Subscan systems on this page. All 102 are operational right now.

102operational
Other Networks » Subscan Acala API
Operational
Other Networks » Subscan Acala-Testnet API
Operational
Other Networks » Subscan Agung-Testnet API
Operational

99 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Other Networks » Subscan Alephzero API, Other Networks » Subscan Altair API, Other Networks » Subscan Assethub-Kusama API, Other Networks » Subscan Assethub-Paseo API, Other Networks » Subscan Assethub-Polkadot API, Other Networks » Subscan Assethub-Westend API, Other Networks » Subscan Astar API, Other Networks » Subscan Autonomys API, Other Networks » Subscan Autonomys-Chronos API, Other Networks » Subscan Avail API, Other Networks » Subscan Avail-Turing API, Other Networks » Subscan Basilisk API, and 87 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Subscan Outages & Incidents

Incident history from the official Subscan status page, including resolution updates.

No recent incidents reported by the vendor.

Subscan Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Subscan incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Subscan Outage Reports

Problems reported by engineers using Subscan. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Subscan problems reported yet.

Something wrong with Subscan on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Subscan

Is Subscan down? Its official status page at subscan.statuspage.io reports on 102 components, including Subscan Acala API, Subscan Acala-Testnet API and Subscan Agung-Testnet API. PulsAPI checks it every few minutes and can alert you when Subscan reports an incident.

Subscan Status FAQ

Is Subscan down right now?

The verdict at the top of this page comes from the latest poll of the official Subscan status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Subscan is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Subscan recovers.

How do I check Subscan uptime history?

PulsAPI tracks Subscan uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Subscan changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Subscan outages?

PulsAPI reads the official Subscan status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Subscan components?

Yes. PulsAPI monitors 102 individual Subscan components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Subscan goes down?

Yes. Create a free account and subscribe to Subscan: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Subscan to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Subscan problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Subscan?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Subscan plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Subscan with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services