asn.dev

Observed topology

AS52892 COPREL TELECOM LTDA

Residential ARIN Cable/DSL/ISP

Upstreams 8 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 12
Adjacent (IPv6) 8
Upstream graph Who carries AS52892, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS52892 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52892: 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.

ASNetworkTypeFamiliesPaths seen
AS28146MHNET TELECOMResidentialIPv4 IPv62,560
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv6560
AS3356Level 3 Parent, LLCTransitIPv4 IPv6477
AS999CORIX NETWORKSUnclassifiedIPv4213
AS6939Hurricane Electric LLCTransitIPv4 IPv6101
AS202Level 3 Parent, LLCUnclassifiedIPv453
AS33891Core-Backbone GmbHHostingIPv4 IPv652
AS3303Swisscom (Schweiz) AGResidentialIPv442

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268218COPREL TELECOM LTDAUnclassifiedIPv4 IPv6275
AS28212COPREL TELECOM LTDAUnclassifiedIPv4 IPv6245
AS265895Atitus Educacao S.AUnclassifiedIPv460
AS262583Fundacao Universidade de Passo FundoUnclassifiedIPv4 IPv653

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS28146MHNET TELECOMResidentialIPv4 IPv62,862
AS3356Level 3 Parent, LLCTransitIPv4 IPv6782
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv6576
AS268218COPREL TELECOM LTDAUnclassifiedIPv4 IPv6275
AS28212COPREL TELECOM LTDAUnclassifiedIPv4 IPv6245
AS999CORIX NETWORKSUnclassifiedIPv4218
AS6939Hurricane Electric LLCTransitIPv4 IPv6101
AS265895Atitus Educacao S.AUnclassifiedIPv460
AS33891Core-Backbone GmbHHostingIPv4 IPv655
AS202Level 3 Parent, LLCUnclassifiedIPv453

All 12 adjacent →

Provenance

Where this comes from

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