Observed topology

AS272501 Cotia Fiber Telecomunicacoes e Servicos LTDA

Unclassified APNIC Cable/DSL/ISP

Upstreams 2 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS272501: 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
AS52468	UFINET PANAMA S.A.	Unclassified	IPv6	231
AS24482	SG.GS	Hosting	IPv6	7

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS271500	LINKGOLD TELECOMUNICACOES	Residential	IPv4	189
AS269561	M.M. Brito da Silva - Multimidia	Unclassified	IPv4 IPv6	92

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS52468	UFINET PANAMA S.A.	Unclassified	IPv4 IPv6	542
AS263966	WORLD WIFI TELECOMUNICACOES LTDA - ME	Residential	IPv4 IPv6	264
AS271500	LINKGOLD TELECOMUNICACOES	Residential	IPv4	189
AS265937	Alianca TecnoinfoLtda	Residential	IPv4 IPv6	92
AS269561	M.M. Brito da Silva - Multimidia	Unclassified	IPv4 IPv6	92
AS273459	COMFORT NET SERVICOS DE TELECOMUNICACOES LTDA	Residential	IPv4	17
AS24482	SG.GS	Hosting	IPv4 IPv6	10

Provenance

Where this comes from

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