TLDR
Two L1s had notable issues this week. 1) Toncoin (TON): reported major outage during the Cloudflare incident on 18 Nov per a media report. 2) Cardano (ADA): reported a chain split on 23 Nov per a media report.
- Toncoin (TON): major outage amid the 18 Nov Cloudflare disruption per a media report.
- Cardano (ADA): a developers experiment caused a reported chain split on 23 Nov per a media report.
- Many disruptions were web front ends, not core consensus outages, per multiple reports.
Deep Dive
1. Toncoin Outage
Toncoin (TON) was cited as suffering a major outage on 18 Nov during the widespread Cloudflare incident that affected many crypto sites and services. The characterization of TONs issue as a major outage appears in coverage of the Cloudflare event, which highlighted downtime across several crypto-facing platforms and tools, including TON-linked services. See the media report for details.
- The same incident was described as knocking various crypto front ends offline, confirming broad service disruptions rather than a single isolated platform failure per a separate report.
Treat TON-related interfaces as potentially affected by upstream web infrastructure outages, and separate front-end downtime from the chains consensus health when assessing risk.
2. Cardano Chain Split
Cardano (ADA) was reported to have experienced a chain split on 23 Nov after a careless developer experiment, according to a media headline and summary. While not framed as a prolonged outage, a chain split is a material network event that can temporarily disrupt normal operations until resolved. See the media report.
- Chain splits can create temporary divergence between nodes and require coordination or patches to restore a single canonical chain. The coverage implies impact sufficient to warrant attention.
If you operate on ADA, monitor for post-mortems or node updates and confirm finality and the canonical chain before executing sensitive transactions.
3. Front Ends vs Core Networks
A large share of this weeks disruptions came from web infrastructure outages, chiefly Cloudflare, which pulled down many crypto interfaces without necessarily halting their underlying blockchains. Reports noted widespread 500 errors across dashboards, APIs, explorers, and exchange front ends during the event. See the report for scope.
- Several outlets also contrasted these web outages with core chains that kept producing blocks, underscoring the difference between service availability and network liveness.
When evaluating an outage, verify whether it is a UI or API dependency failure versus a protocol-level halt. Response plans differ.
Conclusion
This weeks L1 incidents centered on Toncoins reported outage during the Cloudflare disruption and a separate Cardano chain split. Many other issues were front-end outages tied to web infrastructure rather than core chain failures, so distinguish service downtime from protocol liveness when assessing impact.
