SherwoodPulse
Not affiliated with any operator
Loading
chain data…
Three signals kept apart on purpose: is the chain alive, is the read path alive, and do transactions go through.
Is the chain alive?
Evidence that the sequencer is producing blocks and committing them to Ethereum.
Is the read path alive?
What users and explorers see. A frozen head here with a healthy chain is an RPC or indexer problem, not an outage.
| Endpoint | Head | Head age | Latency | Status |
|---|
Do transactions go through?
A zero-value self-transfer from a public test address, sent every few minutes and followed from submission to inclusion to being posted on Ethereum. The only check here that uses the chain the way a user does.
| Sent (UTC) | Included in | Inclusion | On Ethereum | Result |
|---|
Last 24 hours
Per-minute view. Each bar is the worst pause in block production that minute (from block timestamps, not from any RPC's opinion). Hover for values.
Last 90 days
One cell per UTC day from the monitor's evaluations every 5 seconds. Grey is time the monitor was not watching; it is never counted as healthy.
Recent status changes
Incidents
Opened and closed automatically from the signals above. Each one says which kind of failure the evidence supports, and each has a permanent page with the evidence as the monitor saw it. Full archive.
How to read this
A frozen block number on an explorer proves nothing by itself. Every chain here runs one sequencer. It produces blocks, pushes them out over a feed to RPC nodes and indexers, and posts batches to Ethereum. Any of those three can stall independently.
Chain halt: the sequencer stops. The next block it produces carries a timestamp that jumps by the length of the outage. That gap is permanent, on-chain evidence. Batches to L1 also stop.
Read-path stall: the sequencer keeps going, but the public RPC or the explorer indexer falls behind. Users see a stuck head. Block timestamps stay continuous and L1 batches keep landing. Annoying, but funds and state are fine.
Batch delay: blocks keep coming but nothing reaches Ethereum. State is soft until it lands. Watch this one.
Transactions stuck: every read-only signal looks fine but our own test transactions stop getting included. Only chains with a funded test address show this check.
This page shows all three signals so you can tell which one is happening instead of guessing from a screenshot.
Sherwood Pulse is independent and reads the chains and Ethereum directly. Updates and incident notices: @sherwoodpulse on X.