Lisk logo

Is Lisk Down?

SaaSLive status, outages, and incident history

No. Lisk is up right now.

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

OperationalChecked 2m agoLive · 60s while moving

Know the moment Lisk breaks

Lisk is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

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

How we know: the official Lisk status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Lisk Component Status

The main Lisk systems on this page. All 7 are operational right now.

7operational
Lisk App
Operational
Mainnet » Batcher
Operational
Mainnet » RPC
Operational

4 more components tracked

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

Also tracking Mainnet » Sequencer, Website » Documentation, Website » Forum, Website » Website.

See all of them free

Component statuses may change independently during partial outages.

Recent Lisk Outages & Incidents

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

Lisk Mainnet sequencer maintenanceScheduled for Aug 17, 2026 · 2h 0mScheduled

The scheduled maintenance has been completed. --- [2026-08-17T14:00:11.244Z] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-08-17T12:43:06.694Z] (scheduled) Scheduled maintenance — 17 Aug 2026, 14:00–16:00 UTC (16:00–18:00 CEST) We're upgrading the Lisk Mainnet sequencer to the latest recommended client release. Block production will pause only for the restart; RPC endpoints, deposits and withdrawals should remain unaffected and no action is required from users. Node operators: upgrade to lisk-node v0.4.26 (https://github.com/LiskHQ/lisk-node/releases/tag/v0.4.26), which also carries the recommended op-reth bump from v0.4.25. Snap-sync operators on Mainnet — action required: the trusted-peer node keys have rotated. Replace OP_RETH_TRUSTED_PEERS in your .env.mainnet with the value in the v0.4.26 notes and restart; git pull will not overwrite your local edit. Endpoints are unchanged — only the keys. Full-sync operators are unaffected.

Lisk Mainnet sequencer maintenanceScheduled for Jul 29, 2026 · 1h 0mScheduled

The scheduled maintenance has been completed. --- [2026-07-29T15:00:07.814Z] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-07-29T14:40:40.748Z] (scheduled) We will be undergoing scheduled maintenance during this time.

Lisk Mainnet infrastructure maintenanceResolved Jul 14, 2026 · 0 minResolved

The sequencer node was being upgraded, because of which no new blocks were being produced for a short period of time. The upgrade was performed successfully and the chain is progressing normally.

Lisk Uptime History

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

Uptime history49 days observed
Aug 8100.00% averageSep 25

Live Lisk Outage Reports

Problems reported by engineers using Lisk. 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 Lisk problems reported yet.

Something wrong with Lisk on your end?

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

About Lisk

Lisk publishes a public status page at status.lisk.com covering 13 components, including Website, RPC and Sequencer. PulsAPI tracks Lisk outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Lisk uptime at 100.00%. Response times, incident history, and SLA tracking for Lisk are available on the PulsAPI dashboard.

Lisk Status FAQ

Is Lisk down right now?

The verdict at the top of this page comes from the latest poll of the official Lisk status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Lisk 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 Lisk recovers.

How do I check Lisk uptime history?

PulsAPI tracks Lisk uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Lisk changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Lisk outages?

PulsAPI reads the official Lisk status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Lisk components?

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

Can I get alerts when Lisk goes down?

Yes. Create a free account and subscribe to Lisk: 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 Lisk 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 Lisk problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Lisk?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Lisk 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 Lisk with the rest of your stack

2463+ 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