Observed topology

AS272659 Neton Comercio e Servicos de Informatica Ltda ME

Unclassified APNIC

Upstreams 2 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS272659: 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
AS3356	Level 3 Parent, LLC	Transit	IPv6	189
AS268311	Dconnect Telecom	Residential	IPv6	49

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS52752	Vegas Telecom Informatica Ltda.	Unclassified	IPv4	59
AS267563	Ei Telecom LTDA	Unclassified	IPv4	59
AS268311	Dconnect Telecom	Residential	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	324
AS268311	Dconnect Telecom	Residential	IPv4 IPv6	150
AS52752	Vegas Telecom Informatica Ltda.	Unclassified	IPv4	59
AS267563	Ei Telecom LTDA	Unclassified	IPv4	59

Provenance

Where this comes from

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