Bitcoin YearsThe Atlas
Menu

The incident record

Bitcoin under stress

Every time Bitcoin broke, split by accident or came close to it, and how it held. Block by block, from primary sources, with no simulations: only what happened.

4incidents in depth
31Bitcoin Core vulnerabilities disclosed
4,194stale blocks on record
24 blockslongest accidental split (2013)
Stale blocks per month, 2011 to 2026, with the incidentsEach vertical stroke is one month; its height grows with the number of stale blocks recorded that month. Busy early years (2011–2015) settle into a quiet line after 2016, broken by spikes in March 2013, August 2017 and August 2026.201120132015201720192021202320252026January 2011: 3 stale blocksFebruary 2011: 8 stale blocksMarch 2011: 13 stale blocksApril 2011: 13 stale blocksMay 2011: 36 stale blocksJune 2011: 44 stale blocksJuly 2011: 27 stale blocksAugust 2011: 27 stale blocksSeptember 2011: 10 stale blocksOctober 2011: 14 stale blocksNovember 2011: 38 stale blocksDecember 2011: 29 stale blocksJanuary 2012: 63 stale blocksFebruary 2012: 71 stale blocksMarch 2012: 48 stale blocksApril 2012: 45 stale blocksMay 2012: 96 stale blocksJune 2012: 113 stale blocksJuly 2012: 70 stale blocksAugust 2012: 84 stale blocksSeptember 2012: 61 stale blocksOctober 2012: 41 stale blocksNovember 2012: 35 stale blocksDecember 2012: 29 stale blocksJanuary 2013: 43 stale blocksFebruary 2013: 32 stale blocksMarch 2013: 65 stale blocksApril 2013: 44 stale blocksMay 2013: 47 stale blocksJune 2013: 43 stale blocksJuly 2013: 26 stale blocksAugust 2013: 64 stale blocksSeptember 2013: 60 stale blocksOctober 2013: 58 stale blocksNovember 2013: 72 stale blocksDecember 2013: 69 stale blocksJanuary 2014: 72 stale blocksFebruary 2014: 56 stale blocksMarch 2014: 47 stale blocksApril 2014: 57 stale blocksMay 2014: 35 stale blocksJune 2014: 47 stale blocksJuly 2014: 57 stale blocksAugust 2014: 52 stale blocksSeptember 2014: 35 stale blocksOctober 2014: 48 stale blocksNovember 2014: 32 stale blocksDecember 2014: 51 stale blocksJanuary 2015: 62 stale blocksFebruary 2015: 54 stale blocksMarch 2015: 54 stale blocksApril 2015: 55 stale blocksMay 2015: 31 stale blocksJune 2015: 24 stale blocksJuly 2015: 55 stale blocksAugust 2015: 36 stale blocksSeptember 2015: 29 stale blocksOctober 2015: 60 stale blocksNovember 2015: 46 stale blocksDecember 2015: 66 stale blocksJanuary 2016: 32 stale blocksFebruary 2016: 29 stale blocksMarch 2016: 12 stale blocksApril 2016: 9 stale blocksMay 2016: 13 stale blocksJune 2016: 12 stale blocksJuly 2016: 11 stale blocksAugust 2016: 13 stale blocksSeptember 2016: 12 stale blocksOctober 2016: 11 stale blocksNovember 2016: 13 stale blocksDecember 2016: 8 stale blocksJanuary 2017: 31 stale blocksFebruary 2017: 14 stale blocksMarch 2017: 10 stale blocksApril 2017: 10 stale blocksMay 2017: 18 stale blocksJune 2017: 17 stale blocksJuly 2017: 3 stale blocksAugust 2017: 27 stale blocksSeptember 2017: 16 stale blocksOctober 2017: 11 stale blocksNovember 2017: 25 stale blocksDecember 2017: 13 stale blocksJanuary 2018: 15 stale blocksFebruary 2018: 13 stale blocksMarch 2018: 5 stale blocksApril 2018: 8 stale blocksMay 2018: 5 stale blocksJune 2018: 5 stale blocksJuly 2018: 9 stale blocksAugust 2018: 7 stale blocksSeptember 2018: 4 stale blocksOctober 2018: 7 stale blocksNovember 2018: 4 stale blocksDecember 2018: 7 stale blocksJanuary 2019: 6 stale blocksFebruary 2019: 7 stale blocksMarch 2019: 2 stale blocksApril 2019: 8 stale blocksMay 2019: 6 stale blocksJune 2019: 4 stale blocksJuly 2019: 8 stale blocksAugust 2019: 8 stale blocksSeptember 2019: 7 stale blocksOctober 2019: 7 stale blocksNovember 2019: 4 stale blocksDecember 2019: 1 stale blockJanuary 2020: 12 stale blocksFebruary 2020: 7 stale blocksMarch 2020: 7 stale blocksApril 2020: 4 stale blocksMay 2020: 4 stale blocksJune 2020: 9 stale blocksJuly 2020: 9 stale blocksAugust 2020: 14 stale blocksSeptember 2020: 8 stale blocksOctober 2020: 14 stale blocksNovember 2020: 16 stale blocksDecember 2020: 19 stale blocksJanuary 2021: 9 stale blocksFebruary 2021: 9 stale blocksMarch 2021: 13 stale blocksApril 2021: 5 stale blocksMay 2021: 4 stale blocksJune 2021: 7 stale blocksJuly 2021: 5 stale blocksAugust 2021: 7 stale blocksSeptember 2021: 3 stale blocksOctober 2021: 5 stale blocksNovember 2021: 10 stale blocksDecember 2021: 6 stale blocksFebruary 2022: 2 stale blocksMarch 2022: 4 stale blocksApril 2022: 2 stale blocksMay 2022: 6 stale blocksJune 2022: 2 stale blocksAugust 2022: 2 stale blocksSeptember 2022: 2 stale blocksOctober 2022: 2 stale blocksNovember 2022: 3 stale blocksDecember 2022: 3 stale blocksJanuary 2023: 5 stale blocksFebruary 2023: 6 stale blocksMarch 2023: 7 stale blocksApril 2023: 3 stale blocksMay 2023: 13 stale blocksJune 2023: 5 stale blocksJuly 2023: 5 stale blocksAugust 2023: 4 stale blocksSeptember 2023: 3 stale blocksOctober 2023: 5 stale blocksNovember 2023: 7 stale blocksDecember 2023: 7 stale blocksJanuary 2024: 5 stale blocksFebruary 2024: 3 stale blocksMarch 2024: 3 stale blocksApril 2024: 5 stale blocksMay 2024: 4 stale blocksJune 2024: 6 stale blocksJuly 2024: 5 stale blocksAugust 2024: 4 stale blocksSeptember 2024: 2 stale blocksOctober 2024: 7 stale blocksNovember 2024: 2 stale blocksDecember 2024: 3 stale blocksJanuary 2025: 6 stale blocksFebruary 2025: 11 stale blocksMarch 2025: 4 stale blocksApril 2025: 4 stale blocksMay 2025: 1 stale blockJune 2025: 9 stale blocksJuly 2025: 5 stale blocksAugust 2025: 4 stale blocksSeptember 2025: 25 stale blocksOctober 2025: 7 stale blocksNovember 2025: 6 stale blocksDecember 2025: 11 stale blocksJanuary 2026: 5 stale blocksFebruary 2026: 5 stale blocksMarch 2026: 6 stale blocksApril 2026: 7 stale blocksMay 2026: 6 stale blocksJune 2026: 2 stale blocksJuly 2026: 3 stale blocksAugust 2026: 19 stale blocksSeptember 2026: 4 stale blocksOctober 2026: 3 stale blocksNovember 2026: 1 stale blockValue overflow2013 chain splitBIP66 forksBitcoin CashCVE-2018-17144BIP-110 split off

Swipe the chart for 2018–2026 →

Stale blocks per month: valid blocks that lost a race or belonged to a chain that split off. The longer the stroke, the more were recorded (square-root scale). Coloured dots mark the incidents below. Busy early years reflect slow block propagation; after 2016 the line goes quiet. 358 of 4,194 records have no timestamp and are not drawn.

The incidents

Each dossier gives the block height, a timeline in UTC, what broke, how it was fixed and the price on Bitstamp at that minute. Contested splits, where people chose to leave, are told on the Bitcoin forks page and only linked here.

Consensus bug

The value overflow: 184 billion bitcoin out of nothing

Aug 15, 2010 · block 74,638

A transaction in block 74,638 created more than 184 billion bitcoin. A fix was out the same evening, and within a day the chain without the bad block had overtaken it.

Read the dossier →
Accidental chain split

March 2013: the accidental chain split

Mar 11, 2013 · block 225,430

A block that Bitcoin 0.8 accepted and older versions could not process split the network for about six hours, until large pools switched back to the older software.

Read the dossier →
Mining failure

July 2015: pools mining on an invalid block

Jul 4, 2015

When the BIP66 soft fork took effect, a small miner produced an invalid block, and large pools that did not check blocks before building on them extended it. Two short invalid chains followed.

Read the dossier →
Software vulnerability

CVE-2018-17144: the inflation bug that was never used

Sep 17, 2018

A bug in Bitcoin Core would have let a miner spend the same coins twice in one block, creating new bitcoin. It was reported, patched and released within about 30 hours; no exploitation is known.

Read the dossier →
Contested split

Bitcoin Cash splits off

Aug 1, 2017

A planned hard fork by the big-block camp; the stale-block data records 18 blocks from 18:12 UTC that day.

The full story on Bitcoin forks →
Contested split

BIP-110 nodes split off

Aug 8, 2026

Nodes enforcing a soft fork that almost no miner followed; the stale-block data records 8 blocks of that chain.

The full story on Bitcoin forks →

Every disclosed Bitcoin Core vulnerability

As published by the Bitcoin Core project, newest first. Most were fixed quietly and disclosed later, under the project’s security disclosure policy; severity is the project’s own rating. Updated weekly; last check 2026-11-13.

DisclosedAdvisorySeveritySummary (the advisory’s own)
Nov 10, 2026CVE-2025-62859 - Block processing stall via witness malleationMediumBlock processing may be stalled by a peer announcing a compact block with a malleated witness
Nov 10, 2026CVE-2025-62860 - Inbound Tor connections wrongly receive -whitelist permissionsMediumVarious DoS and privacy protections were lifted for incoming Tor connections on affected nodes.
Nov 10, 2026CVE-2025-62861 - Block template creation halted by TRUC sibling eviction during reorgHighA chain reorganization could trigger erroneous "sibling eviction" of TRUC (v3) transactions, corrupting the mempool so an affected node can no longer create block templates until it is restarted. A fix was released on October 10th 2025 in Bitcoin Core v30.0.
Oct 28, 2026CVE-2026-117349 - Slow unbounded memory growth on paused pre-BIP31 peersMediumBitcoin Core queues announcements for all peers, including paused ones. Pre-BIP31 peers could stay paused forever and let the queue grow unboundedly.
Oct 28, 2026CVE-2026-117350 - Unbounded memory growth through TCP urgent data on non-Linux systemsMediumOn platforms other than Linux, a malicious peer could cause a node to run out of memory by sending TCP urgent (out-of-band) data.
Oct 28, 2026CVE-2026-117346 - Undo file overflow under extreme conditionsLowAfter filling thousands of blocks in preparation, a miner able to trigger a precisely timed short reorg following a specific sequence of blocks could crash some nodes by corrupting their undo data. A fix for 64-bit systems was released in Bitcoin Core versions 29.5, 30.4, 31.2 and 32.1; 32-bit systems and nodes storing blocks on FAT32 remain affected.
May 5, 2026CVE-2024-52911 - Script Interpreter Remote CrashHighA specially-crafted block can be used to remotely crash a Bitcoin Core node by exploiting a use-after-free in its script interpreter.
Oct 24, 2025CVE-2025-46597 - Highly unlikely remote crash on 32-bit systemsLowAn attacker could produce a block that crashes nodes running on 32-bit systems in a rare edge case. A fix was released on October 10th 2025 in Bitcoin Core v30.0.
Oct 24, 2025CVE-2025-46598 - CPU DoS from unconfirmed transaction processingLowSpecially crafted invalid unconfirmed transactions could cause unnecessary resource usage. A fix was released on October 10th 2025 in Bitcoin Core v30.0.
Oct 24, 2025CVE-2025-54604 - Disk filling from spoofed self connectionsLowAn attacker could cause a victim node to fill up its disk space by repeatedly faking self-connections over a long time. A fix was released on October 10th 2025 in Bitcoin Core v30.0.
Oct 24, 2025CVE-2025-54605 - Disk filling from invalid blocksLowAn attacker could cause a victim node to fill up its disk space by repeatedly sending invalid blocks. A fix was released on October 10th 2025 in Bitcoin Core v30.0.
Apr 28, 2025CVE-2024-52919 - Remote crash due to addr message spam (part 2)LowAn attacker could crash a node by spamming it with `addr` messages for a very long time. A fix was released on April 14th 2025 in Bitcoin Core v29.0.
Nov 5, 2024CVE-2024-52922 - Hindered block propagation due to stalling peersMediumA peer could hinder block propagation by announcing blocks first and then simply withholding the block.
Oct 8, 2024Disclosure of CVE-2024-35202HighAn attacker could remotely crash a Bitcoin Core node by triggering an assertion in the blocktxn message handling logic.
Oct 8, 2024Disclosure of DoS due to inv-to-send sets growing too largeMediumThe inv-to-send sets could grow too large to a point where the time spent sorting the sets would affect the node's ability to communicate with its peers.
Oct 8, 2024CVE-2024-52921 - Hindered block propagation due to mutated blocksMediumA peer could hinder block propagation by sending mutated blocks.
Sep 18, 2024CVE-2019-25220 - Memory DoS due to headers spamHighAn attacker could spam a Bitcoin Core node with low-difficulty headers chains, which could be used to remotely crash it.
Jul 31, 2024CVE-2024-52919 - Remote crash due to addr message spamHighNodes could be spammed with addr messsages, which could be used to crash them. A fix was released on September 14th, 2021 in Bitcoin Core v22.0.
Jul 31, 2024CVE-2024-52917 - Infinite loop bug in the miniupnp dependencyLowNodes could be crashed by a malicious UPnP device on the local network. A fix was released on September 14th, 2021 in Bitcoin Core v22.0.
Jul 3, 2024CVE-2024-52918 - Crash using malicious BIP72 URIMediumThe BIP70 implementation in Bitcoin-Qt could silently crash when opening a BIP72 URI. A fix was released on June 3rd, 2020 in Bitcoin Core 0.20.0.
Jul 3, 2024CVE-2024-52920 - DoS using huge GETDATA messagesLowA malformed `GETDATA` message could trigger 100% CPU usage on the receiving node. A fix was released on June 3rd, 2020 in Bitcoin Core 0.20.0.
Jul 3, 2024CVE-2024-52916 - Memory DoS using low-difficulty headersMediumNodes could be spammed with low-difficulty headers, which could be used to crash it. A fix was released on September 14th, 2017 in Bitcoin Core 0.15.0.
Jul 3, 2024CVE-2024-52915 - Memory DoS using huge INV messagesMediumNodes would allocate up to 50 MB of memory per attacker sending a malicious `INV` message. A fix was released on June 3rd, 2020 in Bitcoin Core 0.20.0.
Jul 3, 2024CVE-2024-52914 - Significant DoS due to orphan handlingHighA node could be stalled for hours when receiving a specially crafted unconfirmed transaction. A fix was released on May 18th, 2019 in Bitcoin Core 0.18.0.
Jul 3, 2024CVE-2024-52912 - Netsplit due to timestamp adjustmentMediumA node could be split from the network when attacked by its first 200 peers. A fix was released on January 15th, 2021 in Bitcoin Core version 0.21.0.
Jul 3, 2024Disclosure of CVE-2020-14198HighNodes could be subject to CPU and memory DoS when attacked by lots of distinct IPs. A fix was released on August 1st, 2020 in Bitcoin Core 0.20.1.
Jul 3, 2024CVE-2024-52913 - Censorship due to transaction re-request handlingMediumNodes could be prevented from seeing specific unconfirmed transactions by a malicious peer. A fix was released on January 14th, 2021 in Bitcoin Core 0.21.0.
Jul 3, 2024Disclosure of CVE-2015-3641MediumAttackers sending large incomplete messages would cause high memory usage. A fix was released on April 27th, 2015 in Bitcoin Core 0.10.1.
Jul 3, 2024CVE-2015-20111 - Remote code execution due to bug in miniupnpcMediumA bug in the miniupnpc library could have led to a remote code execution in Bitcoin Core. A fix was released on October 15th, 2015 in Bitcoin Core 0.11.1.
Nov 8, 2019Disclosure of CVE-2017-18350not statedNodes were potentially vulnerable to a buffer overflow by malicious SOCKS servers. A fix was released on November 6th, 2017 in Bitcoin Core version 0.15.1.
Sep 20, 2018Disclosure of CVE-2018-17144not statedBitcoin Core was vulnerable to a DoS and inflation attack. A fix was released on September 18th, 2018 in Bitcoin Core versions 0.16.3 and 0.17.0rc4.

The longest runs of stale blocks

Heights where competing blocks were recorded several blocks in a row. A long run means two chains grew side by side for a while.

HeightsBlocksFirst blockWhat it was
225,430–225,46132Mar 11, 2013, 22:39 UTCThe March 2013 chain split
24 blocks were orphaned before the chains rejoined at 225,454; the data also holds stale blocks at the heights just after
478,559–478,57618Aug 1, 2017, 18:12 UTCBitcoin Cash splits off
222,562–222,57211time unknownNot explained in our sources
961,632–961,6398Aug 8, 2026, 20:12 UTCThe BIP-110 minority chain
213,277–213,2815time unknownNot explained in our sources
213,272–213,2754Dec 23, 2012, 06:44 UTCNot explained in our sources

How this record is made

Only what happened

Every fact on these pages comes from a source linked beside it, primary sources first: BIPs, release notes, project alerts and the original reports. Where a detail could not be confirmed, it is left out.

What counts as an incident

A bug that broke Bitcoin’s rules, an accidental split of the chain, or a failure that put users on an invalid chain. Contested splits are on the forks page; exchange hacks and price crashes are on the crashes page.

Stale blocks are an incomplete record

The data set collects blocks seen by contributors’ own nodes, so it is not complete, especially before 2015. Blocks that break Bitcoin’s rules, such as those of July 2015, are usually not in it.

Prices at the moment

Dossiers show the last Bitstamp trade at the minute an incident began and the range over the next 24 hours, from the Time Machine data. Before 2012 only first-of-month prices exist.

Data and licences

Use our data. The incident record and the monthly stale-block counts are free to reuse under CC BY 4.0. Credit “Bitcoin Years, Bitcoin under stress” with a link to this page. Downloads: incidents.csv (each incident with its block, start time and primary source) · stale-monthly.csv (stale blocks per month). The advisory summaries belong to the Bitcoin Core project and are not covered.

Bitcoin Years. (2026). Bitcoin under stress: incident record and monthly stale blocks [Data set; stale blocks from bitcoin-data/stale-blocks, CC0]. CC BY 4.0. https://bitcoinyears.com/bitcoin-under-stress/

Sources. Stale blocks: bitcoin-data/stale-blocks, data CC0 1.0. Vulnerabilities: Bitcoin Core security advisories (titles, dates and severities as published; summaries are each advisory’s own excerpt). Copies, refreshed weekly: stale.json · advisories.json. Prices: Bitstamp BTC/USD via the Time Machine. Check today’s block 74,638 yourself: Proof of history.