Observed topology

AS266304 Plig Telecom LTDA

Unclassified APNIC Cable/DSL/ISP

Upstreams 3 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266304: 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
AS262532	NET ONDA SERVICOS DE INTERNET LTDA	Residential	IPv4 IPv6	136
AS61832	DB3 SERVICOS DE TELECOMUNICACOES S.A	Unclassified	IPv4 IPv6	42
AS6939	Hurricane Electric LLC	Transit	IPv4	30

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS268903	M A DE M VIDAL	Unclassified	IPv4 IPv6	93

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS262532	NET ONDA SERVICOS DE INTERNET LTDA	Residential	IPv4 IPv6	137
AS61832	DB3 SERVICOS DE TELECOMUNICACOES S.A	Unclassified	IPv4 IPv6	122
AS268903	M A DE M VIDAL	Unclassified	IPv4 IPv6	93
AS6939	Hurricane Electric LLC	Transit	IPv4	41
AS28368	SOBRALNET SERVICOS E TELECOMUNICACOES LTDA - ME	Residential	IPv4	1

Provenance

Where this comes from

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