asn.dev

Observed topology

AS264935 AS264935 - CENTRALNET TELECOMUNICACOES LTDA - ME

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264935: 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
AS263073DTEL TELECOMResidentialIPv4 IPv6127
AS6939Hurricane Electric LLCTransitIPv4 IPv692
AS263276BBG TELECOM LTDAResidentialIPv4 IPv633
AS52850Oxente.net Solucoes Tecnologicas EireliResidentialIPv416
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv66
AS35280F5 Networks SARLHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271671REALTEC NETWORKS LTDAUnclassifiedIPv4 IPv6224

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS271671REALTEC NETWORKS LTDAUnclassifiedIPv4 IPv6224
AS263073DTEL TELECOMResidentialIPv4 IPv6216
AS263276BBG TELECOM LTDAResidentialIPv4 IPv6148
AS6939Hurricane Electric LLCTransitIPv4 IPv6110
AS52850Oxente.net Solucoes Tecnologicas EireliResidentialIPv416
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv68
AS35280F5 Networks SARLHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66

Provenance

Where this comes from

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