Observed topology

AS52548 AS52548 - tc conecta servicos de telecomunicacoes e provedor

Unclassified RIPE

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52548: 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
AS3549	Level 3 Parent, LLC	Transit	IPv4 IPv6	232
AS263432	CORPORATIVA TELECOMUNICACOES EIRELI ME	Unclassified	IPv4 IPv6	140
AS61712	YUPNET TELECOMUNICACOES LTDA	Residential	IPv4	86
AS268976	Weclix Telecom S/A	Unclassified	IPv4	58
AS52660	e.serv informatica e tecnologia ltda.	Residential	IPv4	47
AS263305	NET.COM TELECOMUNICACOES EIRELI	Unclassified	IPv4 IPv6	35
AS270364	NOVALINK INTERNET LTDA	Residential	IPv4 IPv6	25

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS268191	MARTINS TELECOM	Unclassified	IPv4	49

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3549	Level 3 Parent, LLC	Transit	IPv4 IPv6	253
AS263432	CORPORATIVA TELECOMUNICACOES EIRELI ME	Unclassified	IPv4 IPv6	140
AS61712	YUPNET TELECOMUNICACOES LTDA	Residential	IPv4	114
AS268976	Weclix Telecom S/A	Unclassified	IPv4	58
AS268191	MARTINS TELECOM	Unclassified	IPv4	49
AS52660	e.serv informatica e tecnologia ltda.	Residential	IPv4	47
AS263305	NET.COM TELECOMUNICACOES EIRELI	Unclassified	IPv4 IPv6	35
AS270364	NOVALINK INTERNET LTDA	Residential	IPv4 IPv6	25

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.