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 August 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 11m agoLive, rechecked every 60s
How we know: the official Lisk status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

Lisk Component Status

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

10operational
Mainnet » Batcher
Operational
Mainnet » RPC
Operational
Mainnet » Sequencer
Operational

7 more components tracked

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

Also tracking Portal, Sepolia » Batcher, Sepolia » RPC, Sepolia » Sequencer, Website » Documentation, Website » Forum, Website » Website.

Create a free account

Component statuses may change independently during partial outages.

Recent Lisk Outages & Incidents

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

Uptime history4 days observed
Aug 8100.00% averageAug 11
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 mainnet derivation gap bugResolved May 15, 2026 · -1805 minResolved

A combination of two bugs in our rollup stack caused L2 blocks 31997343..31999643 to be omitted from L1 batch submissions. As a result, L1-based verifier derivation cannot process the subsequent batch starting at  block 31999644. Current status  - The L2 chain remains live and continues to produce blocks; sequencer-facing transactions are unaffected.  - Full nodes are currently operational.  - Archival nodes are not operational at this time; recovery is in progress via EL sync.  - No user funds, balances, or transaction state are at risk. Root cause  1. op-node’s EL-sync completion path marked an unsafe block as safe/finalized prior to L1 confirmation.  2. The batcher trusted the resulting local safe label without cross-checking against the latest confirmed L1 batch range.

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?

PulsAPI checks Lisk every 60 seconds. 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.

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%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Lisk.

How fast does PulsAPI detect Lisk outages?

PulsAPI polls the official Lisk status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual Lisk components?

Yes. PulsAPI monitors 10 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 PulsAPI account and subscribe to Lisk. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Lisk status changes.

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. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor Lisk alongside up to 9 other services at pulsapi.com/signup.

Track Lisk with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when Lisk status changes.

Start free trial