What Happens if a Rollup's Sequencer Goes Offline?
A centralized sequencer going offline halts new transactions on a rollup — here's what actually happens, and why most rollups have a fallback for it.
Because many current rollups depend on a single sequencer to process transactions, that sequencer becoming unavailable — whether through a technical failure, an attack, or simple downtime — raises a specific, practical question about what happens to activity on that rollup in the meantime.
Why a Single Point of Failure Exists in Many Current Designs
Many rollups currently operate with one centralized sequencer handling all transaction ordering and processing — this concentration means an outage affecting that one entity's infrastructure can affect the entire rollup's normal operation, unlike a more distributed system with many independent participants.
What Typically Happens to New Transactions During an Outage
While a centralized sequencer is offline, new transactions generally can't be processed and included in new batches through the normal path — users attempting routine activity on the rollup during this window may find transactions simply don't go through until the sequencer comes back online.
Why Existing, Already-Processed Transactions Aren't Directly at Risk
A sequencer outage affecting new transaction processing doesn't retroactively affect transactions that were already processed and settled before the outage began — the specific risk is to activity attempted during the downtime window, not to previously confirmed balances or transaction history.
Why Most Rollups Include a Fallback Mechanism for Exactly This Scenario
Recognizing this single-point-of-failure risk, many rollup designs include a mechanism allowing users to eventually submit transactions or withdraw funds directly through Layer 1, bypassing the sequencer entirely if it remains unavailable for an extended period — though this fallback path is typically slower and more involved than routine sequencer-processed activity.
Why Outage Duration Matters More Than the Outage Itself
A brief outage lasting minutes carries different practical impact than an extended one lasting days — checking how quickly a specific rollup's documented fallback mechanisms actually allow users to exit or transact if the outage extends beyond a short window provides more useful context than the mere possibility of an outage happening.
Why This Connects Directly to Sequencer Decentralization Progress
Rollups actively working toward more decentralized sequencer operation are addressing this exact single-point-of-failure risk directly — checking a specific rollup's progress and roadmap on this front provides insight into how much this risk is likely to persist for that particular platform going forward.
What to Check Before Relying Heavily on a Specific Rollup
The rollup's documented history of sequencer outages, if any, how those were handled and how long they lasted, and the specific fallback mechanism available to users if the sequencer becomes unavailable again in the future.
Check a rollup's sequencer uptime history and fallback mechanisms before relying on it for time-sensitive activity — a centralized sequencer going offline is a real, if generally temporary, risk.