What happened
At 22:57 UTC on 12 November 2026, Osmosis stopped producing blocks. QuickNode's status page logged a "Network-Wide Stall" at block 74,955,152 and marked the incident resolved at 16:31 UTC on 13 November, with no cause given.
Exchanges handled it per network. Upbit paused Osmosis deposits and withdrawals and kept OSMO trading open, according to crypto.news and Analytics Insight. Coinbase's status page showed "Osmosis (OSMO) - Delayed Sends and Receives" from 16:20 PST on 12 November until 15:19 PST on 16 November, and said buys and sells were not affected.
The bug this exposes
Transfer code often asks one question, "is this asset enabled?", and gets one boolean back. The stall needed two answers:
- Is the chain writing blocks right now?
- Is the venue processing this coin on this chain right now?
For about four days the answers differed. The chain was back within a day by QuickNode's account, and Coinbase's notice stayed open until the 16th.
The check
export function chainState({ latestBlockTime, now, maxAgeSeconds }) { const age = Math.round((new Date(now) - new Date(latestBlockTime)) / 1000); return { stalled: age > maxAgeSeconds, ageSeconds: age }; } export function canSend({ chain, venue }) { if (chain.stalled) return { ok: false, reason: `chain stalled: last block ${fmt(chain.ageSeconds)} ago` }; if (!venue.transfersOpen) return { ok: false, reason: `chain is moving, venue still has transfers paused (${venue.note})` }; return { ok: true, reason: 'chain is moving and the venue has transfers open' }; } const fmt = (s) => (s >= 3600 ? `${Math.floor(s / 3600)} h ${Math.floor((s % 3600) / 60)} min` : `${Math.floor(s / 60)} min`); latestBlockTime comes from any node or explorer API for the chain. venue comes from the exchange's status feed. Keep them as two inputs so neither can stand in for the other.
Three moments from the incident:
const LAST_BLOCK = '2026-11-12T22:57:00Z'; // block 74,955,152 const cases = [ ['13 Nov 01:21 UTC', { now: '2026-11-13T01:21:00Z', latestBlockTime: LAST_BLOCK }, { transfersOpen: false, note: 'delayed sends and receives' }], ['14 Nov 12:00 UTC', { now: '2026-11-14T12:00:00Z', latestBlockTime: '2026-11-14T11:59:54Z' }, { transfersOpen: false, note: 'delayed sends and receives' }], ['17 Nov 00:00 UTC', { now: '2026-11-17T00:00:00Z', latestBlockTime: '2026-11-16T23:59:55Z' }, { transfersOpen: true, note: '' }], ]; for (const [label, block, venue] of cases) { const chain = chainState({ ...block, maxAgeSeconds: 60 }); console.log(label, '->', canSend({ chain, venue })); } Output from node can-send.mjs:
13 Nov 01:21 UTC -> { ok: false, reason: 'chain stalled: last block 2 h 24 min ago' } 14 Nov 12:00 UTC -> { ok: false, reason: 'chain is moving, venue still has transfers paused (delayed sends and receives)' } 17 Nov 00:00 UTC -> { ok: true, reason: 'chain is moving and the venue has transfers open' } The stall time and block height in the first case are from QuickNode's page, and the venue states follow Coinbase's notice. The block times in the second and third cases are sample inputs I picked to show a chain that is moving again. They are not readings from Osmosis.
Notes
-
maxAgeSecondsis yours to set per chain. Take it from the chain's normal block interval with a wide margin, or a slow block will page you at night. - Compare against your own clock in UTC. Block timestamps are set by validators and can drift a little.
- A resolved incident on a node provider's page describes that provider. Read the venue's status as well, and read the receiving side's too if the transfer ends at another service.
- Show the user which of the two checks failed. "Chain stalled" and "venue paused" call for different waits.
Sources: QuickNode status page (incident of 12 to 13 Nov 2026), Coinbase status page (12 to 16 Nov 2026), crypto.news (13 Nov 2026), Analytics Insight (13 Nov 2026).