Observed topology

AS272481 SV PROVEDOR DE INTERNET LTDA - ME

Unclassified APNIC

Upstreams 2 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 3

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS272481: 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
AS52696	JTR DA SILVA TECNOLOGIA ME	Unclassified	IPv6	126
AS53180	INFORTEL COMUNICACOES LTDA	Residential	IPv6	33

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS263302	TORPEDOLINK TELECOM	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS52696	JTR DA SILVA TECNOLOGIA ME	Unclassified	IPv4 IPv6	146
AS53180	INFORTEL COMUNICACOES LTDA	Residential	IPv4 IPv6	72
AS263302	TORPEDOLINK TELECOM	Unclassified	IPv4	59

Provenance

Where this comes from

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