Lisk Outage History
9 incidents recorded over the last 365 days, 4 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Lisk Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 17, 2026 | Lisk Mainnet sequencer maintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jul 29, 2026 | Lisk Mainnet sequencer maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jul 14, 2026 | Lisk Mainnet infrastructure maintenanceThe 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. | 0 min | Resolved |
| May 15, 2026 | Lisk mainnet derivation gap bugA 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… | -1805 min | Resolved |
| Feb 4, 2026 | Update OP_NODE_P2P_STATICThe scheduled maintenance has been completed. | 6h 0m | Scheduled |
| Jan 19, 2026 | RedStone price feed oracle liveliness disruption on LiskThe liveliness on the RedStone price feed oracles on Lisk (https://docs.lisk.com/guides/using-oracle-data/redstone-push) was affected earlier due to the discontinuation of the mBTC_POR/BTC source feed. The cause of… | -236 min | Resolved |
| Dec 12, 2025 | LIsk Portal Service OutageThis incident has been resolved. | 181h 53m | Resolved |
| Dec 2, 2025 | Jovian hardfork on Lisk (Mainnet)The scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Nov 19, 2025 | Jovian hardfork on Lisk Sepolia (Testnet)The scheduled maintenance has been completed. | 1h 0m | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Lisk incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Lisk Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Lisk acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Lisk outage in this window ran 7d 13h, against a mean recovery of 1d 3h. If you depend on Lisk in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.