6 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
The article examines a BGP route leak involving Venezuela's state ISP, CANTV (AS8048), which redistributed routes improperly on January 2. This incident highlights potential issues with CANTV's routing policies rather than malicious intent, as similar leaks have occurred frequently in recent months.
If you do, here's more
On January 2, 2026, Venezuela's state-run ISP, CANTV (AS8048), experienced a significant BGP route leak, which was highlighted in a cybersecurity newsletter using Cloudflare Radar data. Since December, there have been eleven route leak events involving AS8048, pointing to a pattern of insufficient routing policies rather than intentional wrongdoing. The leaks appeared to occur when CANTV redistributed routes from its provider, Sparkle (AS6762), to a Colombian network, V.tal GlobeNet (AS52320). This suggests a potential misconfiguration in their routing practices.
BGP route leaks can disrupt internet traffic flow, akin to taking a detour on a highway. They violate established routing protocols by allowing an Autonomous System to pass traffic routes from a provider or peer to another provider or peer, which is not standard practice. In this case, many of the leaked routes were prepended with AS8048 multiple times, making them less appealing for routing. This raises questions about whether CANTV was trying to exploit the leak for malicious purposes, but evidence indicates that this was more likely a technical mishap.
The timing of the leak was notable, occurring over twelve hours before U.S. military actions in Venezuela, suggesting no direct connection to those events. Thereβs a history of similar leaks by AS8048, indicating that this is not a new issue but rather a recurring technical problem. The numerous leaks and the patterns observed hint at broader challenges within CANTV's routing practices, rather than a targeted attack or espionage effort.
Questions about this article
No questions yet.