Observed topology

AS269946 BOOM SOLUTIONS C.A.

Unclassified LACNIC Cable/DSL/ISP

Upstreams 3 carry this network

Downstreams 8 this network carries

Adjacent (IPv4) 11

Adjacent (IPv6) 2

Upstream graph Who carries AS269946, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS269946 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269946: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

AS	Network	Type	Families	Paths seen
AS21826	Telemic C.A.	Unclassified	IPv4 IPv6	1,133
AS263703	C.A	Residential	IPv4	349
AS27717	Digitel C.A.	Unclassified	IPv4	114

Transit

Downstream networks

inferred

Networks for which AS269946 was observed as the last hop before the origin, meaning it appears to provide them transit.

AS	Network	Type	Families	Paths seen
AS265633	Galup C.A	Unclassified	IPv4	232
AS274117	TELECOM C.A	Residential	IPv4	216
AS272993	C.A.	Unclassified	IPv4 IPv6	90
AS269788	OFIC TECH DE VENEZUELA C.A.	Unclassified	IPv4	58
AS273011	C.A	Unclassified	IPv4	58
AS274956	TELECOM.NET, C.A	Unclassified	IPv4	58
AS272946	FIX, C.A	Unclassified	IPv4	57
AS274331	TELECOM, C.A	Unclassified	IPv4	40

Adjacency

Adjacent networks

All 11

Every AS seen directly next to AS269946 in a routing path, in either direction.

AS	Network	Type	Families	Paths seen
AS21826	Telemic C.A.	Unclassified	IPv4 IPv6	1,942
AS263703	C.A	Residential	IPv4	349
AS265633	Galup C.A	Unclassified	IPv4	232
AS274117	TELECOM C.A	Residential	IPv4	216
AS27717	Digitel C.A.	Unclassified	IPv4	114
AS272993	C.A.	Unclassified	IPv4 IPv6	90
AS269788	OFIC TECH DE VENEZUELA C.A.	Unclassified	IPv4	58
AS273011	C.A	Unclassified	IPv4	58
AS274956	TELECOM.NET, C.A	Unclassified	IPv4	58
AS272946	FIX, C.A	Unclassified	IPv4	57

All 11 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.