Is the chain down, or is it me?

Something is not working. Before you open a ticket, four checks tell you where the problem is, and they take about a minute in total. Often they also tell you it will fix itself.

1. Is the chain producing blocks?

Open l2pscan.com and look at chain head on the front page. Wait a few seconds and watch it. Blocks arrive about every one and a half seconds, so the number should visibly climb.

If it climbs, the chain is fine and the problem is somewhere between you and it. Skip to check 3.

You can ask the chain directly instead:

curl -s https://rpc.l2protocol.com \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

2. What do the nodes say?

l2stats.dev shows every node that reports in. If the network is genuinely in trouble it shows there first: nodes falling behind, block time rising, active nodes dropping.

If the chain head is stuck and the nodes agree it is stuck, it is not you. Open a ticket, and say what you saw here.

3. Is the site just catching up?

Our sites read the chain through an indexer, which follows a block or two behind. When it falls further behind, a coloured bar appears at the top of the explorer saying so.

That bar means recent things may not have appeared yet. It does not mean anything is lost, and it fixes itself. https://l2pscan.com/api/explorer/status gives you the exact gap:

curl -s 'https://l2pscan.com/api/explorer/status'

Compare indexedBlock with latestBlock. A gap of a few blocks is normal. A large gap explains a transaction you cannot find yet.

4. Is it your side?

If the chain is producing blocks and the explorer is current, the problem is between you and the chain. In rough order of likelihood:

The wrong network in your wallet. Everything fails in the same confusing way when your wallet is on another chain. It should say chain id 12216. See Connect to the network.

No L2P for gas. An address with a zero balance cannot do anything at all, including moving tokens it holds. See Gas and transaction fees.

A browser extension in the way. Ad blockers and privacy extensions break wallet connections and captchas more often than anything else. Try a private window with extensions off.

A stale page. A tab left open for hours holds old data and, on the voting site, a signature for yesterday's date. Reload before concluding anything.

Your own RPC or node. If you point your tooling somewhere other than rpc.l2protocol.com, check that first.

Still stuck

Open a ticket at support.l2protocol.com, and put in what these four checks told you. "The chain head was climbing, the explorer was current, my wallet is on 12216 and it still fails" turns a day of back and forth into one answer.

Bring a transaction hash or an address if there is one. With it we can see exactly what happened; without it we have to ask, and that costs a round trip. See Open a ticket.