No, Polygon PoS is producing blocks
Its newest block, number 97,393,215, was made 0 s before our check at 02:14 UTC, by the chain's own clock. It normally makes one every 1.5 s.
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.
Halts over time
Every halt and finality stall on record for Polygon PoS 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.
We have measured Polygon PoS 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.
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.
| Date | Type | Duration | What happened | Sources |
|---|---|---|---|---|
| 12 Jan 2026, 16:00 UTC | Finality stalled | ≈2.7 h | A PrepareProposal/ProcessProposal mismatch in Heimdall made validators repeatedly reject valid proposals, stalling finalization until validators rolled back Heimdall.Note on timesThe postmortem gives a ~16:00 UTC start. The status page lists 17:40 and shows 'finality caught up' at 18:43 (timezone presumed UTC). | status.polygon.technology |
| 17 Dec 2025, 18:00 UTC | Degraded | ≈14 h | Double-sealed blocks and span rotations with only two block producers online made lagging Bor nodes reject blocks, so many RPC nodes stalled while the chain itself stayed live.Note on times'Partial Bor Halt'. The hotfix was out by 22:00 UTC Dec 17 and most nodes were back in sync within hours; the end is the 'functionality restored' post. Block production continued. | status.polygon.technology |
| 10 Sep 2025, 07:11 UTC | Finality stalled | ≈10 h | A bug in Heimdall's milestone (finality-gadget) process and Bor/Erigon left some nodes unable to progress, delaying finality 10-15+ minutes; a Heimdall hard fork at ~15:00 UTC (Bor v2.2.11-beta2, Heimdall v0.3.1) restored it.Note on timesBlocks continued. The window runs from the first status post (07:11) to 'consensus finalization restored' (17:28, times presumed UTC). Finality was delayed rather than fully stopped for the whole window. Marked resolved Sep 11 07:00. | status.polygon.technology |
| 30 Jul 2025, 14:00 UTC | Finality stalled | ≈61 min | A validator exit triggered a Heimdall bug that halted consensus/chain progression for about an hour; Bor kept producing blocks but RPC providers had to resync.Note on timesSources conflict. The Block (citing Polygon) says Bor blocks continued, detected shortly before 10:00 ET and resolved 11:01 ET. Blocmates says new blocks halted ~50 min from about 12:07 UTC. | theblock.co blocmates.com |
Client software
Bor + Heimdall Single implementation
Validators run Polygon's Bor (a Geth fork) for blocks and Heimdall for checkpoints and milestones. There is no independent second client in production.
ChainReport review of official repositories and docs, 12 Nov 2026. Compare all chains
Compare
Embed this status
Show the live Polygon PoS status in your docs, dashboard or README.
The badge updates about once a minute and links back to this page. Feed for Polygon PoS incidents: Atom.
Links
We read Polygon PoS from two places: first source PublicNode and second source dRPC.
Other chains
Also on the Network Desk for Polygon
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; dRPC; 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.