Monday, November 16, 2026

No, Sui is producing checkpoints

Its newest checkpoint, number 345,698,383, was made 3 s before our check at 02:16 UTC, by the chain's own clock. It normally makes one every 244 ms.

Read from the chain just now

Each mark is a minute of checkpoints; 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.

244 msnormal time between checkpoints
243 msaverage over the last hour
InstantfinalityBFT checkpoints
169days 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 Sui 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 Sui ourselves since 12 Nov 2026; anything earlier is from the public record.

Block production, hour by hour

Average time between checkpoints 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 ms244 ms487 ms12 Nov 21:00 UTC: 244 ms per checkpoint12 Nov 22:00 UTC: 244 ms per checkpoint12 Nov 23:00 UTC: 244 ms per checkpointFri 1313 Nov 00:00 UTC: 240 ms per checkpoint13 Nov 01:00 UTC: 243 ms per checkpoint13 Nov 02:00 UTC: 244 ms per checkpoint13 Nov 03:00 UTC: 243 ms per checkpoint13 Nov 04:00 UTC: 244 ms per checkpoint13 Nov 05:00 UTC: 244 ms per checkpoint13 Nov 06:00 UTC: 243 ms per checkpoint13 Nov 07:00 UTC: 244 ms per checkpoint13 Nov 08:00 UTC: 244 ms per checkpoint13 Nov 09:00 UTC: 244 ms per checkpoint13 Nov 10:00 UTC: 244 ms per checkpoint13 Nov 11:00 UTC: 245 ms per checkpoint13 Nov 12:00 UTC: 244 ms per checkpoint13 Nov 13:00 UTC: 243 ms per checkpoint13 Nov 14:00 UTC: 243 ms per checkpoint13 Nov 15:00 UTC: 242 ms per checkpoint13 Nov 16:00 UTC: 243 ms per checkpoint13 Nov 17:00 UTC: 243 ms per checkpoint13 Nov 18:00 UTC: 244 ms per checkpoint13 Nov 19:00 UTC: 241 ms per checkpoint13 Nov 20:00 UTC: 243 ms per checkpoint13 Nov 21:00 UTC: 239 ms per checkpoint13 Nov 22:00 UTC: 243 ms per checkpoint13 Nov 23:00 UTC: 244 ms per checkpointSat 1414 Nov 00:00 UTC: 241 ms per checkpoint14 Nov 01:00 UTC: 244 ms per checkpoint14 Nov 02:00 UTC: 243 ms per checkpoint14 Nov 03:00 UTC: 243 ms per checkpoint14 Nov 04:00 UTC: 243 ms per checkpoint14 Nov 05:00 UTC: 242 ms per checkpoint14 Nov 06:00 UTC: 244 ms per checkpoint14 Nov 07:00 UTC: 244 ms per checkpoint14 Nov 08:00 UTC: 244 ms per checkpoint14 Nov 09:00 UTC: 244 ms per checkpoint14 Nov 10:00 UTC: 244 ms per checkpoint14 Nov 11:00 UTC: 244 ms per checkpoint14 Nov 12:00 UTC: 244 ms per checkpoint14 Nov 13:00 UTC: 243 ms per checkpoint14 Nov 14:00 UTC: 243 ms per checkpoint14 Nov 15:00 UTC: 243 ms per checkpoint14 Nov 16:00 UTC: 243 ms per checkpoint14 Nov 17:00 UTC: 243 ms per checkpoint14 Nov 18:00 UTC: 244 ms per checkpoint14 Nov 19:00 UTC: 244 ms per checkpoint14 Nov 20:00 UTC: 244 ms per checkpoint14 Nov 21:00 UTC: 240 ms per checkpoint14 Nov 22:00 UTC: 241 ms per checkpoint14 Nov 23:00 UTC: 243 ms per checkpointSun 1515 Nov 00:00 UTC: 239 ms per checkpoint15 Nov 01:00 UTC: 240 ms per checkpoint15 Nov 02:00 UTC: 241 ms per checkpoint15 Nov 03:00 UTC: 243 ms per checkpoint15 Nov 04:00 UTC: 243 ms per checkpoint15 Nov 05:00 UTC: 244 ms per checkpoint15 Nov 06:00 UTC: 246 ms per checkpoint15 Nov 07:00 UTC: 247 ms per checkpoint15 Nov 08:00 UTC: 247 ms per checkpoint15 Nov 09:00 UTC: 247 ms per checkpoint15 Nov 10:00 UTC: 247 ms per checkpoint15 Nov 11:00 UTC: 245 ms per checkpoint15 Nov 12:00 UTC: 244 ms per checkpoint15 Nov 13:00 UTC: 244 ms per checkpoint15 Nov 14:00 UTC: 242 ms per checkpoint15 Nov 15:00 UTC: 243 ms per checkpoint15 Nov 16:00 UTC: 244 ms per checkpoint15 Nov 17:00 UTC: 244 ms per checkpoint15 Nov 18:00 UTC: 244 ms per checkpoint15 Nov 19:00 UTC: 230 ms per checkpoint15 Nov 20:00 UTC: 242 ms per checkpoint15 Nov 21:00 UTC: 244 ms per checkpoint15 Nov 22:00 UTC: 246 ms per checkpoint15 Nov 23:00 UTC: 243 ms per checkpointMon 1616 Nov 00:00 UTC: 238 ms per checkpoint16 Nov 01:00 UTC: 243 ms per checkpoint16 Nov 02:00 UTC: 242 ms per checkpointnormal 244 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.

DateTypeDurationWhat happenedSources
29 May 2026, 20:30 UTCHalt≈5.8 hWhen validators restarted for the fix, a latent bug that never persisted a failed DKG (randomness) status across restarts stalled the epoch change.
Note on timesAbout 13:30-19:20 PT. Triggered by the restart for the v1.72 fix, not by address balances directly.
sui.io
theblock.co
29 May 2026, 12:00 UTCHalt≈3.5 hThe same v1.72 underflow recurred because a different cancellation reason masked InsufficientFundsForWithdraw and bypassed the interim fix.
Note on timesAbout 5:00-8:30 PT per the postmortem timeline. Elsewhere it says ~9:40 PT (16:40 UTC), so the duration may be up to ~280 min.
sui.io
coindesk.com
28 May 2026, 14:00 UTCHalt≈6.5 hThe v1.72 address-balances feature exposed a gas-charging edge case: hybrid-gas transactions cancelled for insufficient funds still spent funds, creating a negative balance that crashed validators.
Note on timesAbout 7:00-13:30 PT (PDT = UTC-7). Approximate.
sui.io
theblock.co
14 Jan 2026, 14:22 UTCHalt≈6.4 hAn edge case in consensus-commit logic under garbage-collection conditions made validators compute different commits, so more than 1/3 of stake signed a different checkpoint and certification stopped.
Note on timesThe start is the last processed transaction (Suiscan via The Block); some reports say 14:52 UTC. The ~20:44 UTC end is from secondary reports in search results. The Sui postmortem says only 'about 6 hours'.
sui.io
theblock.co
21 Nov 2024, 09:15 UTCHalt≈2.5 hAn assert in congestion-control (transaction scheduling) code crashed every validator when the estimated execution cost was zero, leaving them in a crash loop until v1.37.4 shipped.
Note on timesThe postmortem gives about 1:15-3:45 am PT (PST = UTC-8). Times are approximate.
sui.io
theblock.co

Client software

sui-node Single implementation

All validators run the same sui-node software from Mysten Labs, so a bug in one release can stop the whole network. That is what happened in the 2024–2026 halts listed below.

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

Compare

Embed this status

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

Is Sui down? Live status by ChainReport

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

Links

We read Sui from two places: first source Sui GraphQL (Mysten Labs).

Other chains

Also on the Network Desk for Sui

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: Sui GraphQL (Mysten Labs); 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.