The layer 2 is down. What do you check first?
Sometimes transactions on a layer 2 rollup stop going through and an official notice says the sequencer is under maintenance. The obvious questions follow: what happened to the transactions already sent, are the funds safe, and is there a way to get them back to Ethereum?
This post looks at what a sequencer does and the difference between inclusion on L2 and settlement on L1. It walks through the user impact of an outage and the forced-inclusion and withdrawal routes through L1 using a hypothetical incident, and lists what to check about operator powers and official channels.
What a sequencer does
The sequencer receives L2 transactions, orders them, packages them into blocks, and posts the results and data to Ethereum. Most rollups still run a single sequencer operated by one entity, so when it stops, new L2 transactions are not processed promptly.
The OP Stack specification describes the protocol as designed to be resilient to sequencer censorship: users can submit transactions directly to a contract on Ethereum (L1), and the sequencer must include them on L2 within a defined window. That route is the emergency exit when the sequencer fails.
Inclusion versus settlement
A transaction shown as complete in an L2 wallet has been accepted and ordered by the sequencer. It is final in L1 terms only after its data is posted to Ethereum and, for an optimistic rollup, after the challenge period passes. When the sequencer stops, what happens to a transaction depends on how far it had progressed.
Transactions whose data the sequencer has already posted to L1 remain on record even if the sequencer stops. Those received but not yet posted may be processed when the sequencer recovers or, in some cases, may need to be resent.
A hypothetical outage
The table follows a user through a hypothetical six-hour sequencer outage on an optimistic rollup.
| Time | What happens | What the user can do |
|---|---|---|
| Immediately | New L2 transactions are not processed | Check the official status page; avoid resending the same transaction |
| 1–2 hours | Pending transactions pile up; on-chain price updates lag | Review liquidation risk on L2 loans |
| If needed | Submit a transaction directly to the L1 contract (forced inclusion) | Pay L1 gas to send an L2 transaction or withdrawal request |
| Recovery at 6 hours | Pending transactions process in order; forced transactions included | Check transaction status in a block explorer |
| L1 withdrawal complete | After the challenge period (about 7 days) | Finalize the withdrawal on L1 |
Forced inclusion is for prolonged outages or censorship of specific transactions. For a short maintenance window, waiting may be cheaper.
Impact on users
Time-sensitive positions are hit first. If you have collateral in an L2 lending protocol, you cannot top it up or repay during the outage, and liquidations can fire all at once when the sequencer resumes.
Price oracles may stall too. Outside markets keep moving while L2 prices stop updating, so a large price gap can be applied in one jump at recovery. If you use leverage on an L2, treat sequencer outages as a real risk.
Forced withdrawal routes
Forced inclusion and withdrawal through L1 let users protect their assets without the sequencer's cooperation. They require paying Ethereum gas, involve more steps than a button in an L2 app, and for optimistic rollups still require waiting out the roughly seven-day challenge period that Ethereum.org describes.
Rollups differ in the maximum delay before forced transactions are included, what kinds of transactions are supported, and what tools exist to use the route in practice. Without checking the official documentation in advance, an outage is a bad time to learn.
Ethereum.org's layer 2 overview also notes that rollups are at different stages of decentralization. Knowing whether your rollup's escape hatch is fully operational, or still being built, is part of understanding the risk you take on.
Checking operator powers and channels
Prepare for sequencer outages by checking these items for any rollup you use.
- Find out who operates the sequencer and whether one operator or several share the role.
- Check whether forced inclusion and forced withdrawal through L1 exist and how long they take.
- Bookmark the official status page and announcement channels, and do not follow unofficial links during an outage.
- If you borrow or use leverage on the L2, keep extra margin to absorb liquidation risk during an outage.
- Look up past outages and how long recovery took.
Limits of sequencer safeguards
Even where forced inclusion exists, using it takes technical understanding and money, and not every rollup has the route fully in place. Plans to decentralize sequencing across multiple operators are still in progress for many networks.
The outage and timings here are hypothetical. When using a rollup, check Ethereum.org and the rollup's own documentation, paying attention to publication dates, and look over the emergency route once while things are calm.