Observed topology

AS272461 AS272461 - MKS CONNECT COMUNICACAO E MULTIMIDIA LTDA

Residential APNIC

Upstreams 3 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS272461: 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
AS16735	ALGAR TELECOM S/A	Unclassified	IPv6	78
AS53115	ISPX Solucoes em Telecomunicacoes SPE Ltda	Unclassified	IPv6	18
AS24482	SG.GS	Hosting	IPv6	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS265335	PLANETA NET TELECOM	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS16735	ALGAR TELECOM S/A	Unclassified	IPv4 IPv6	80
AS53115	ISPX Solucoes em Telecomunicacoes SPE Ltda	Unclassified	IPv4 IPv6	73
AS265335	PLANETA NET TELECOM	Unclassified	IPv4	59
AS24482	SG.GS	Hosting	IPv4 IPv6	4
AS37721	Virtual Technologies & Solutions	Residential	IPv4	1

Provenance

Where this comes from

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