Observed topology

AS266841 AS266841 - GALANET SOLUTION C.A.

Unclassified LACNIC

Upstreams 5 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266841: 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	Corporacion Telemic C.A.	Unclassified	IPv4	518
AS263703	VIGINET C.A	Residential	IPv4	418
AS264628	CORPORACION FIBEX TELECOM, C.A.	Residential	IPv4 IPv6	215
AS11562	Net Uno, C.A.	Residential	IPv4	62
AS264778	TotalCom Venezuela C.A.	Hosting	IPv4	59

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS271920	Corporacion SLJ, C.A	Unclassified	IPv4	59
AS274874	LITHIUM TELECOM, C.A	Unclassified	IPv4	2

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS21826	Corporacion Telemic C.A.	Unclassified	IPv4	520
AS263703	VIGINET C.A	Residential	IPv4	477
AS264628	CORPORACION FIBEX TELECOM, C.A.	Residential	IPv4 IPv6	215
AS11562	Net Uno, C.A.	Residential	IPv4	62
AS264778	TotalCom Venezuela C.A.	Hosting	IPv4	59
AS271920	Corporacion SLJ, C.A	Unclassified	IPv4	59
AS274874	LITHIUM TELECOM, C.A	Unclassified	IPv4	2

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.