Which L1s faced incidents this week?

TLDR

This week, Cardano (ADA) and Toncoin (TON) faced notable incidents.

1. Cardano (ADA): A malformed transaction triggered a temporary chain split; a patch was issued and no user funds were reported lost per an ecosystem update. details
2. Toncoin (TON): Experienced significant downtime tied to the Cloudflare outage affecting crypto infrastructure. report

Deep Dive

1. Cardano Chainsplit

Cardano suffered a temporary chain split after a malformed delegation transaction exploited an old bug, leading some nodes to follow a poisoned branch while others stayed on the canonical chain.

1. The incident caused parallel ledgers until an emergency patch and upgrade instructions were issued to node operators. incident summary
2. Governance group Intersect and core teams coordinated the fix and emphasized that no user funds were lost during the disruption. follow-up
3. The event highlights the risk of long-lived edge-case bugs and the importance of prompt, coordinated upgrades across validators and infrastructure.

2. Toncoin Downtime From Cloudflare Outage

Toncoins availability was hit during a broad Cloudflare outage that disrupted many crypto front ends and services, showing how centralized internet providers can indirectly impact L1 access.

1. Coverage noted significant downtime for Toncoin as part of the wider outage affecting thousands of sites and several crypto services. outage wrap
2. Despite front-end issues across the ecosystem, many blockchains, including Bitcoin and Ethereum, continued on-chain operations normally during the incident. context
3. The takeaway is architectural: protocol liveness can persist while user-facing access degrades if infrastructure dependencies fail.

Conclusion

Cardano faced a direct protocol incident that required a network patch, while Toncoins issue stemmed from an upstream infrastructure outage. For users, the operational lesson is twofold: prioritize chains and providers that communicate swiftly on upgrades and diversify your access paths so infrastructure hiccups do not become protocol-level confusion.