Monday, November 16, 2026

No, Arbitrum One is producing blocks

Its newest block, number 524,623,474, was made 2 s before our check at 02:16 UTC, by the chain's own clock. It normally makes one every 296 ms.

Read from the chain just now

Each mark is a minute of blocks; a shorter mark means fewer than normal. Hatched stretches are halts we confirmed. Point at the rail or use the arrow keys to read it.

296 msnormal time between blocks
307 msaverage over the last hour
20 min behindfinalityFinal once settled on Ethereum
1,067days since the last halt
100%uptime we measured, last 3 days
100%on one client, single implementation

Halts over time

Every halt and finality stall on record for Arbitrum One since 2024: from postmortems, status pages and news reports, plus the ones we measured ourselves. Point at a dot, or focus the rail and use the arrow keys; Enter opens the incident.

No halt or finality stall on record for Arbitrum One since 1 January 2024.

We have measured Arbitrum One ourselves since 12 Nov 2026; anything earlier is from the public record.

Block production, hour by hour

Average time between blocks for each hour over the last 7 days, or since we started measuring on 12 Nov 2026. The dashed line is the normal pace. Red hours contain a halt; empty hours are gaps in our sampling.

0 ms296 ms592 ms12 Nov 21:00 UTC: 341 ms per block12 Nov 22:00 UTC: 335 ms per block12 Nov 23:00 UTC: 336 ms per blockFri 1313 Nov 00:00 UTC: 318 ms per block13 Nov 01:00 UTC: 305 ms per block13 Nov 02:00 UTC: 289 ms per block13 Nov 03:00 UTC: 269 ms per block13 Nov 04:00 UTC: 278 ms per block13 Nov 05:00 UTC: 279 ms per block13 Nov 06:00 UTC: 274 ms per block13 Nov 07:00 UTC: 284 ms per block13 Nov 08:00 UTC: 282 ms per block13 Nov 09:00 UTC: 278 ms per block13 Nov 10:00 UTC: 276 ms per block13 Nov 11:00 UTC: 294 ms per block13 Nov 12:00 UTC: 300 ms per block13 Nov 13:00 UTC: 275 ms per block13 Nov 14:00 UTC: 263 ms per block13 Nov 15:00 UTC: 262 ms per block13 Nov 16:00 UTC: 276 ms per block13 Nov 17:00 UTC: 287 ms per block13 Nov 18:00 UTC: 301 ms per block13 Nov 19:00 UTC: 309 ms per block13 Nov 20:00 UTC: 315 ms per block13 Nov 21:00 UTC: 297 ms per block13 Nov 22:00 UTC: 315 ms per block13 Nov 23:00 UTC: 311 ms per blockSat 1414 Nov 00:00 UTC: 310 ms per block14 Nov 01:00 UTC: 300 ms per block14 Nov 02:00 UTC: 285 ms per block14 Nov 03:00 UTC: 285 ms per block14 Nov 04:00 UTC: 296 ms per block14 Nov 05:00 UTC: 324 ms per block14 Nov 06:00 UTC: 318 ms per block14 Nov 07:00 UTC: 310 ms per block14 Nov 08:00 UTC: 313 ms per block14 Nov 09:00 UTC: 306 ms per block14 Nov 10:00 UTC: 316 ms per block14 Nov 11:00 UTC: 310 ms per block14 Nov 12:00 UTC: 308 ms per block14 Nov 13:00 UTC: 279 ms per block14 Nov 14:00 UTC: 260 ms per block14 Nov 15:00 UTC: 261 ms per block14 Nov 16:00 UTC: 264 ms per block14 Nov 17:00 UTC: 269 ms per block14 Nov 18:00 UTC: 285 ms per block14 Nov 19:00 UTC: 296 ms per block14 Nov 20:00 UTC: 279 ms per block14 Nov 21:00 UTC: 260 ms per block14 Nov 22:00 UTC: 265 ms per block14 Nov 23:00 UTC: 269 ms per blockSun 1515 Nov 00:00 UTC: 281 ms per block15 Nov 01:00 UTC: 265 ms per block15 Nov 02:00 UTC: 267 ms per block15 Nov 03:00 UTC: 288 ms per block15 Nov 04:00 UTC: 317 ms per block15 Nov 05:00 UTC: 323 ms per block15 Nov 06:00 UTC: 304 ms per block15 Nov 07:00 UTC: 311 ms per block15 Nov 08:00 UTC: 292 ms per block15 Nov 09:00 UTC: 282 ms per block15 Nov 10:00 UTC: 305 ms per block15 Nov 11:00 UTC: 300 ms per block15 Nov 12:00 UTC: 253 ms per block15 Nov 13:00 UTC: 278 ms per block15 Nov 14:00 UTC: 272 ms per block15 Nov 15:00 UTC: 293 ms per block15 Nov 16:00 UTC: 301 ms per block15 Nov 17:00 UTC: 309 ms per block15 Nov 18:00 UTC: 318 ms per block15 Nov 19:00 UTC: 307 ms per block15 Nov 20:00 UTC: 323 ms per block15 Nov 21:00 UTC: 320 ms per block15 Nov 22:00 UTC: 334 ms per block15 Nov 23:00 UTC: 303 ms per blockMon 1616 Nov 00:00 UTC: 309 ms per block16 Nov 01:00 UTC: 304 ms per block16 Nov 02:00 UTC: 310 ms per blocknormal 296 ms

Halts we detected

None so far. We have been measuring since 12 Nov 2026.

The public record since 2024

From postmortems, status pages and news reports.

No halts, finality stalls or major degradations on record since January 2024.

Before 2024: 15 Dec 2023. An Arbitrum One sequencer and feed stall during an inscription surge, a major outage of ~4 h (16:57-21:04 UTC per the status page). No Arbitrum One halt found for 2024-2026 (a Mar 23 2026 'block production halted' incident was Arbitrum Sepolia, a testnet). Source

Client software

Single sequencer (Nitro) Single implementation

Blocks come from one sequencer run by Offchain Labs. If that sequencer or its software fails, block production stops for everyone, as the historical record below shows. Users can still force transactions through Ethereum, slowly.

ChainReport review of official repositories and docs, 12 Nov 2026. Compare all chains

Compare

Embed this status

Show the live Arbitrum One status in your docs, dashboard or README.

Is Arbitrum One down? Live status by ChainReport

The badge updates about once a minute and links back to this page. Feed for Arbitrum One incidents: Atom.

Links

We read Arbitrum One from two places: first source PublicNode and second source Arbitrum public RPC.

Other chains

Also on the Network Desk for Arbitrum

How this works and where the data comes from

What we measure. Every minute a server job asks each chain for its newest block and reads the timestamp the chain itself put in that block. "Last block" is now minus that timestamp, so it is accurate even if our own checks run late. "Last hour" is the average spacing between blocks over the past hour, also from block timestamps.

When we call a halt. A chain counts as halted when no new block has appeared for much longer than normal. The limit is set per chain: 2 minutes for most fast chains, 5–7 minutes for Scroll, ZKsync and Cardano, 14 minutes for Dogecoin, 30 minutes for Litecoin and 2 hours for Bitcoin, where long gaps happen by chance. Before declaring a halt we ask a second, independent data provider. If one provider is stale and the other is fresh, the chain is fine and we log the provider as lagging. For Solana, Sui and Cardano we have only one free source, so we wait for three stale checks in a row. Start time is the last block before the stop; end time is the first new block, within about a minute.

Finality. For Ethereum we read the last finalized checkpoint from the beacon chain (normally 2 epochs, about 13–19 minutes behind). For other EVM chains and Polkadot we read the newest "finalized" block from the node. On rollups (Base, Arbitrum, OP, ZKsync, Scroll), "finalized" means settled on Ethereum, which takes longer by design: hours on ZKsync. Free Solana endpoints do not report commitment levels reliably, so we do not show Solana finality.

Limits. We have been measuring since 12 Nov 2026; uptime figures cover only that period and say so. If our job misses minutes, a halt that started and ended entirely inside that gap would show up only as a slow hour in the chart. The historical record before our measurements comes from postmortems and news reports, with approximate times marked "≈". Hyperliquid is measured through HyperEVM, which stops whenever the HyperCore L1 stops.

Sources: PublicNode; Arbitrum public RPC; Historical record: project postmortems, status pages, The Block, CoinDesk, Cointelegraph, Decrypt (linked per row)

Information only, not financial advice. Data comes from public sources and can be delayed or wrong; check the primary source before acting.

Scroll to Top
Chain Report
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.