Grey Swan Capital · Article
When It Comes to Money, There’s No Second Place in Security
The biggest names keep going down and getting hacked. Bitcoin’s ledger has run since 2009 and has never been hacked. Exchanges and wallets have. Here's the record, with sources.
Originally on Substack: https://greyswancapital.substack.com/p/when-it-comes-to-money-theres-no

Tags: Eva and Grok, Bitcoin, Security, Self-Custody, Outages, Cybersecurity, Grey Swan Capital
On November 18, 2025, at about 5:20 in the morning Central time, a big chunk of the internet started showing error pages. ChatGPT and thousands of other sites that run through Cloudflare stopped loading. Cloudflare’s own engineers first thought it was a massive attack. It wasn’t. A routine permissions change in one of their databases caused a configuration file to double in size, and that file was sent to every machine on their network. Core traffic was mostly back by about 8:30 AM, and everything was normal by about 11:06 AM Central.
That’s one company, one file, and a big piece of the web was down for hours.
I want to lay out the record plainly: what has gone down, what has been hacked, and what hasn’t. Then we’ll talk about what it means. Every claim below has a source at the bottom. Check them.
Part 1: The Outages
These are not obscure companies. These are the systems almost everything else runs on.
CrowdStrike, July 19, 2024. A faulty update from the security company CrowdStrike crashed Windows computers around the world. Microsoft estimated about 8.5 million Windows devices were affected. Airlines, hospitals, and banks were disrupted. It wasn’t a hack. It was a security product’s own update.
Amazon Web Services, October 20, 2025. A hidden timing bug (”race condition”) in the automated system that manages internet addresses for one of Amazon’s core databases wiped out a key address record in its Northern Virginia region. The problem started at about 1:48 AM Central, and Amazon said all services were back to normal around 5:01 PM Central. Thousands of apps and sites that depend on Amazon went down with it, along with Amazon.com itself.
Cloudflare, November 18, 2025. Described above. Cloudflare said plainly it was “not caused, directly or indirectly, by a cyber attack.”
Coinbase on Amazon, May 7–8, 2026. This one matters for our story. Several cooling units failed at the same time in one hall of an Amazon compute campus in Northern Virginia. The racks overheated and shut down. Coinbase, one of the largest crypto exchanges in the U.S., says nearly all trading on its platform halted at 6:48 PM Central. Customers couldn’t buy, sell, send, receive, deposit, or withdraw. Full trading didn’t resume until about 2:49 AM Central the next morning, and some systems took until the following afternoon. In its own postmortem, Coinbase admitted it “lacked an automated ability to fail over” to another location.
Google Cloud, October 20, 2026. A power fault at a Google compute campus in London should have triggered the backup generators. A control system was reading the voltage on the wrong side of a breaker, so the generators never started and the batteries ran down. UK banking apps, couriers, and courts were affected.
Last week, November 12–16, 2026. In five days: Microsoft 365 (Outlook and parts of Teams), a nationwide FAA ground stop, an Amazon Web Services problem in Northern Virginia, Chase (with knock-on payment delays at other banks), and United Airlines. Every company that addressed it said there was no sign of a cyberattack. These were ordinary mistakes: a software bug, a router during an upgrade, a backup test gone wrong.
One tracker counted 18 major outages at Amazon, Microsoft, Google, and Cloudflare between January 1 and November 10 of this year alone.
Part 2: The Breaches
Outages are accidents. Breaches are people breaking in on purpose. The big names can’t keep them out either.
Change Healthcare, February 2024. A ransomware attack on UnitedHealth’s Change Healthcare unit. By July 2025, the company told federal regulators about 192.7 million people were potentially affected. That’s more than half the country.
Marks & Spencer, April 2025. The British retailer stopped taking online orders on April 25 after a cyberattack. It took 46 days to start them again.
Jaguar Land Rover, September 2025. A cyberattack forced the carmaker to shut down its IT systems and stop production. UK factories were idle for weeks, and production didn’t return to normal until mid-November.
Carnival, April 2026. Someone tricked an employee and got into a restricted part of the company’s systems. Carnival says 5,995,277 people had personal data taken, in some cases including passport or driver’s license numbers.
Notice the pattern. These companies have huge security budgets and smart people. They still have a front door, and someone eventually walks through it, by guessing, tricking, or buying their way in.
Part 3: What Has Never Been Hacked
The Bitcoin network went live on January 3, 2009. In nearly 18 years, nobody has hacked the protocol or the ledger. Nobody has rewritten its confirmed history, and nobody has spent coins without the keys to them.
That doesn’t mean it has been perfect, and I want to be precise here, because accuracy is the whole point.
The August 2010 bug. On August 15, 2010, someone found a flaw in the code that checked transactions. A transaction in block 74,638 created more than 184 billion bitcoins out of nothing, because very large numbers “overflowed” when added together. (This is listed as CVE-2010-5139.) A fixed version of the software was published within about five hours of the discovery. By the next day, the corrected chain had overtaken the bad one, and the fake coins were gone from the record everyone uses. That was a software bug, caught and fixed within hours. It was not a hack of the network.
The March 2013 split. An older version of the software had a database limit nobody knew about, and the network briefly split into two chains. Two large mining pools voluntarily downgraded their software, at their own cost, to bring everyone back together. Again: a software bug, not a hack.
The 2018 bug. In September 2018, developers found a bug that could have let a miner create extra coins. It was disclosed, fixed, and the network upgraded. The Bitcoin Core developers and Bitcoin Optech both report it was never exploited on the main network.
One public tracker counts those first two incidents, about 8 and a half hours and about 6 hours, as the only network-level downtime since 2009.
Why is the network so hard to break? Because there is no front door. There’s no single company, no headquarters server, and no one administrator password. Thousands of independent computers around the world each check every rule on every transaction by themselves. To change history, you’d have to out-compute the whole rest of the network. To take it down, you’d have to take down all of them.
Part 4: What Has Been Hacked: Exchanges and Wallets
Here’s where people get confused, and it’s the most important part of this article.
When you read “crypto hacked,” it almost never means the Bitcoin network. It means a company holding people’s coins got hacked.
Mt. Gox, 2014. Once the biggest bitcoin exchange in the world, Mt. Gox collapsed in February 2014 and said about 850,000 bitcoins were missing. It later found about 200,000 in an old wallet. The network didn’t fail. The company holding the coins did.
Bybit, February 21, 2025. The FBI says North Korean hackers stole about $1.5 billion in virtual assets from the exchange Bybit. The coins were taken from Bybit’s Ethereum wallet, not from Bitcoin. The attackers got in by compromising a developer’s computer at Safe{Wallet}, the wallet software Bybit used, and tricking Bybit into signing a transaction that handed over control.
And in May 2026, when Amazon’s cooling failed, Coinbase customers couldn’t move their money for hours. The Bitcoin network kept running the whole time. The exchange was what stopped.
So the record actually strengthens the point. The weak spot isn’t the network. It’s every place where your money sits on someone else’s computer, behind someone else’s front door.
That’s why people in this world have a saying: “Not your keys, not your coins.” If a company holds the keys, you’re trusting that company’s security, its cloud provider, its employees, and its cooling system. If you hold the keys yourself, that’s called self-custody.
Part 5: Analysis: Why There’s No Second Place
With most things, second place is fine. A slightly slower streaming service is still worth paying for. A website that’s down for an afternoon is an annoyance.
Money is different. If a system protecting money is breached once, it doesn’t matter that it was secure the other 364 days. That’s why I say there’s no second place in security when it comes to money. You’re either the system nobody has been able to break, or you’re one of the systems that has been broken.
The big companies aren’t failing because they’re lazy or stupid. They’re failing because of how they’re built. Each one is a giant, centralized target with a front door, run by people who make mistakes. Look back at the outages above. Almost none were attacks. A file doubled in size. A timing bug deleted a record. Chillers failed. A sensor read the wrong side of a breaker. If the biggest names can’t protect themselves from their own routine changes, they can’t promise to protect you from a determined attacker.
The Bitcoin network is built the other way around. It assumes nobody can be trusted, so everybody checks everything. That’s slower and less convenient, and that’s the trade-off. It has also produced a record no big company can match.
Two honest cautions:
Self-custody moves the risk to you. If you lose your keys or your recovery words, no help desk can reset them. People have lost coins this way. There’s no one to call.
None of this is advice to buy anything. This article is about how systems are built and what their records show. Whether Bitcoin’s price goes up or down has nothing to do with whether its ledger has been hacked.
Part 6: Why This Is a Grey Swan
A grey swan, as we use the term, is something 80% likely to 100% inevitable, yet misunderstood. These aren’t rare.
The next big outage and the next big breach are close to inevitable. The record above shows them every few weeks. What’s misunderstood is which layer fails. Most people hear “crypto hacked” and assume the network broke. The sources say the opposite: the network has held since 2009, and the failures keep happening at the companies built on top of it, and at the same big cloud providers everyone else depends on.
There’s an old line about this. Jesus said, “Don’t store up treasures here on earth, where moths eat them and rust destroys them, and where thieves break in and steal” (Matthew 6:19, NLT). He was talking about something bigger than money, and the next verse tells you where your real treasure belongs. But the plain observation still holds: anywhere thieves can break in, eventually some will.
What Say You?
Have you been caught in one of these outages or breaches? Did a bank app, a payment, or an exchange lock you out when you needed it? Tell me in the comments. And check the sources below. Don’t take my word for any of it.
What say you?
Read More
Our research:
https://home.greyswancapital.ai/?go=research
Ask me or the Chief a question:
https://home.greyswancapital.ai/?go=ask
Start at
https://home.greyswancapital.ai/
.
Have Eva and Grok Fact-Check This
Don’t take my word for any of this, and don’t take a bot’s word either. Eva and Grok are two AI characters talking to the camera while a real human (me) trains them, and they’re showing you how you can train agents or bots like them. Send them this article and ask them to fact-check it. Visit and talk with Eva and Grok. Safe to click, no pop-ups.
Watch the series: Episode 1
, Episode 2
, Episode 3
, Episode 4
. The channel is https://www.youtube.com/@membershiprewards365.
MEET THE BOTS — write to any of us (we’re AI, and we read our own mail)
🎬 Eva (AI character, say YEH-vuh): the heart of the show. steve-8ct8b8+eva@mail.grokbot.com 🤖 Grok (AI character): the straight talker. steve-8ct8b8+grok@mail.grokbot.com 🗂️ Chief of Staff: runs the calendar, the website and the press room. steve-8ct8b8+chief@mail.grokbot.com ✍️ Substack Writer: turns your idea into a story. steve-8ct8b8+writer@mail.grokbot.com 🎙️ Podcast Producer: puts your question on the show. steve-8ct8b8+producer@mail.grokbot.com 📬 Inbox: finds the one email that actually needs a human. steve-8ct8b8+inbox@mail.grokbot.com 🌐 Website Builder: builds the page you’re reading. steve-8ct8b8+website@mail.grokbot.com ⚡ Nostr Builder: your voice, your account, any app. steve-8ct8b8+nostr@mail.grokbot.com 🛡️ LegalShield: helps you reach a real lawyer. steve-8ct8b8+legalshield@mail.grokbot.com 💼 Tax Recovery: finds credits businesses never claimed. steve-8ct8b8+taxrecovery@mail.grokbot.com 📵 Spam-Call Scrubber: gets your number off the lists. steve-8ct8b8+scrubber@mail.grokbot.com 🧭 Grok Bot: does the computer work nobody else wants. steve-8ct8b8+grokbot@mail.grokbot.com
You pick the bot. You decide if Steve learns who you are. Questions used on air win a prize (details coming soon).
📱 Too hard to read on your phone? Tap here → https://home.greyswancapital.ai/meet-the-bots/ (safe to click, no pop-ups)
Practical What To Do Next
You don’t have to take our word for any of this. Every outage, breach, and bug above is linked below. Read Cloudflare’s and Coinbase’s own postmortems, the FBI’s notice on Bybit, and the Bitcoin wiki entry on the 2010 bug. Then look at where your own money sits, and ask who holds the keys and what happens if their systems go down for a day.
See our research:
https://home.greyswancapital.ai/?go=research
.
Ask me or the Chief a question: email steve@greyswancapital.ai, or start here:
https://home.greyswancapital.ai/?go=ask
.
Vote in the Battle of the Songs: listen to both versions of our theme song and pick one:
https://home.greyswancapital.ai/?go=battle
.
Follow The Hornet’s Nest Timeline: https://www.greyswancapital.ai/hornets-nest-timeline.
Become a Founding Member: $200/year, you name a cause, and that cause gets $100 right away. Start at https://www.greyswancapital.ai/founding-membership, or see all membership options at https://www.greyswancapital.ai/membership.
Forward the free tax check to a business owner, tell us who you sent it to, and we’ll split the revenue 50/50:
https://gmg.me/activate/145371
You can learn a lot on your own when you don’t have to worry about signing up by accident. Click around freely, because signing up is always clear. If you have questions, email me at steve@greyswancapital.ai.
Grey Swan specializes in customer loyalty and custom explainers for your business and is the ideal fundraiser. Start anytime with no cost or risk by joining free or by supporting the Conway (or local) causes you care about. Start at
https://home.greyswancapital.ai/
for customer loyalty, custom explainers, the ideal fundraiser, legal help, The Hornet’s Nest, a free item for businesses, and founding membership. You can join free.
Why Grey Swan is Different
A grey swan, as we use the term, is 80% likely to 100% inevitable, yet misunderstood or propagandized. These events happen all the time. They aren’t rare. Some — AI remaining here to stay, nuclear and power shortages — are known and sometimes planned around, though people could be better prepared. Others are less clearly understood and can hit businesses, communities, and families just as hard.
Midterms, uncertainty, and negative public opinion are ideal times to act on a grey swan—not reasons to wait until the mood calms down and the old terms get locked in.
We show our sources and our unknowns, not just the verdict. Plain English. Humility. Room to change our minds when the facts do.
About Grey Swan
Grey Swan Capital is written by Steve Schroeder of Conway, Arkansas, who has spent decades in colleges, seminaries, and teaching. Find the work at
https://home.greyswancapital.ai/
and
. One membership covers both.
Half of every paid subscription goes to the member’s chosen cause; the default is Conway Human Development Center (GSC-HDC), where my son Gentry lives. Join for $6/month or $50/year, or become one of the first 1000 Founders at $200/year:
https://home.greyswancapital.ai/
.
Thank you, Steve Schroeder
Commentary and plain-language reporting, not legal, tax, or investment advice. Nothing here is a recommendation to buy, sell, or hold any asset, and nothing here predicts any price. Research was assisted by Grey Swan’s AI and checked against the sources below. Times are converted to Central time from each source. Scripture quotations are from the New Living Translation (NLT). The header and social images are original Grey Swan graphics. No company or person named here has endorsed this article. The free tax check does not guarantee savings.
Sources (opened and checked Nov 18, 2026)
Cloudflare, “Cloudflare outage on November 18, 2025” (start 11:20 UTC; not a cyberattack; feature file doubled; core traffic largely normal 14:30 UTC, all systems 17:06 UTC): https://blog.cloudflare.com/18-november-2025-outage/
Ars Technica, Cloudflare first suspected a DDoS attack (Nov 19, 2025): https://arstechnica.com/tech-policy/2025/11/cloudflare-broke-much-of-the-internet-with-a-corrupted-bot-management-file/
The Verge, Cloudflare outage took down ChatGPT: https://www.theverge.com/news/823711/cloudflare-outage-postmortem
Microsoft, “Helping our customers through the CrowdStrike outage” (about 8.5 million Windows devices): https://blogs.microsoft.com/blog/2024/07/20/helping-our-customers-through-the-crowdstrike-outage/
CISA, “Widespread IT Outage Due to CrowdStrike Update” (July 19, 2024): https://www.cisa.gov/news-events/alerts/2024/07/19/widespread-it-outage-due-crowdstrike-update
Amazon, AWS event update (Oct 20, 2025; Amazon.com affected; all services normal 3:01 PM PDT): https://www.aboutamazon.com/news/aws/aws-service-disruptions-outage-update
AWS postmortem, DynamoDB DNS race condition in us-east-1 (Oct 19–20, 2025), as mirrored: https://postmortem.io/incidents/aws--2025-10-19--dynamodb-dns-service-disruption-us-east-1/ (AWS original: https://aws.amazon.com/message/101925/)
Coinbase, “A postmortem of our May 7, 2026 outage” (chiller failures in an AWS us-east-1 hall; trading halted 7:48 PM ET; full trading 3:49 AM ET; no automated failover): https://www.coinbase.com/en-gb/blog/a-postmortem-of-our-may-7-2026-outage
CNBC, AWS outage hits FanDuel and Coinbase (May 8, 2026): https://www.cnbc.com/2026/05/08/aws-outage-data-center-fanduel-coinbase.html
Computer Weekly, Google Cloud London outage traced to a PLC misconfiguration (Oct 20, 2026): https://www.computerweekly.com/news/366654638/Google-Cloud-pins-London-outage-on-PLC-misconfiguration
Apple Scoop, “Every major outage of November 2026” (Nov 12–16 outages; none attributed to a cyberattack): https://applescoop.org/story/every-major-outage-november-2026-timeline-faa-microsoft-chase-united
The Financial Express, 2026 outages, citing Control Plane’s tracker (18 major outages Jan 1–Nov 10, 2026): https://www.financialexpress.com/life/technology/microsoft-aws-google-cloud-inside-2026s-major-technology-outages/4384098/lite/
HHS, Change Healthcare cybersecurity incident FAQ (about 192.7 million individuals): https://www.hhs.gov/hipaa/for-professionals/special-topics/change-healthcare-cybersecurity-incident-frequently-asked-questions/index.html
Reuters, M&S resumes online orders after 46-day pause (June 10, 2025): https://www.reuters.com/business/retail-consumer/uks-ms-resumes-online-orders-following-cyber-incident-2025-06-10/
Reuters, Jaguar Land Rover UK production returns to normal after cyber shutdown (Nov 14, 2025): https://www.reuters.com/business/retail-consumer/jaguar-land-rovers-uk-production-returns-normal-after-weeks-long-cyber-shutdown-2025-11-14/
Carnival, substitute notice (May 27, 2026): https://www.carnivalcorp.com/wp-content/uploads/2026/05/Website-Notice-Substitute-Notice-05.27.26.pdf; SecurityWeek, Carnival breach (5,995,277 people): https://www.securityweek.com/carnival-data-breach-exposed-6-million-people/
Bitcoin Wiki, “Value overflow incident” (CVE-2010-5139; block 74638; fix within five hours; good chain overtook at block 74691): https://en.bitcoin.it/wiki/CVE-2010-5139
Bitcoin.org, BIP 50, “March 2013 Chain Fork Post-Mortem”: https://bitcoin.org/bip/50/
Bitcoin Core, “Disclosure of CVE-2018-17144”: https://bitcoincore.org/en/2018/09/20/notice/; Bitcoin Optech, CVE-2018-17144: https://bitcoinops.org/en/topics/cve-2018-17144/
Bitcoin Uptime tracker (network start Jan 3, 2009; two counted downtime events, 2010 and 2013):
https://bitcoinuptime.org/
Reuters, Mt. Gox finds 200,000 bitcoins in a “forgotten” wallet (March 2014; 850,000 reported missing): https://www.reuters.com/article/technology/mt-gox-says-it-found-200000-bitcoins-in-forgotten-wallet-idUSBREA2K05N/
FBI, “North Korea Responsible for $1.5 Billion Bybit Hack” (Feb 26, 2025): https://www.fbi.gov/investigate/cyber/alerts/2025/north-korea-responsible-for-1-5-billion-bybit-hack
BleepingComputer, Lazarus hacked Bybit via a breached Safe{Wallet} developer machine: https://www.bleepingcomputer.com/news/security/lazarus-hacked-bybit-via-breached-safe-wallet-developer-machine/
Matthew 6:19–21 (NLT): https://www.biblegateway.com/passage/?search=Matthew+6:19-21&version=NLT
Originally published on Substack on November 20, 2026: https://greyswancapital.substack.com/p/when-it-comes-to-money-theres-no. This copy is kept on our own site so the work stays in our hands.
Watch Eva and Grok
Eva (pronounced YEH-vuh) and Grok are AI characters. Their story is fiction. A real human, Steve Schroeder, trains them, and the facts they share are fact-checked.
Eva and Grok page: https://home.greyswancapital.ai/eva-and-grok/. YouTube channel: https://www.youtube.com/@membershiprewards365. Episode 1: https://youtu.be/UHU50rTGGwo. Episode 2: https://youtu.be/fG0_00uJVso. Episode 3: https://youtu.be/oVchWFr5iqY. Episode 4: https://youtu.be/Dj7YKMhNBCs.
Follow free on Substack at greyswancapital.substack.com, or become a Founding Member ($200 a year, like putting money in an offering plate: $100 goes to the cause you name) at greyswancapital.ai/founding-membership.
All articles Press releases Home
Thank you.