asn.dev

Observed topology

AS264270 NETCOL - SERVICO DE PROVEDORES DE ACESSO LTDA

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264270: 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
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6410
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4289
AS262645BrasilNET Telecomunicacoes do Parana LTDAResidentialIPv4129
AS6939Hurricane Electric LLCTransitIPv4 IPv6121
AS24482SG.GSHostingIPv4 IPv619

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269714vipfiber telecom LTDAUnclassifiedIPv4 IPv6254
AS273328joselia e cesar servicos de telecomunicacao ltda mUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6520
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4442
AS269714vipfiber telecom LTDAUnclassifiedIPv4 IPv6254
AS6939Hurricane Electric LLCTransitIPv4 IPv6156
AS262645BrasilNET Telecomunicacoes do Parana LTDAResidentialIPv4 IPv6138
AS273328joselia e cesar servicos de telecomunicacao ltda mUnclassifiedIPv459
AS24482SG.GSHostingIPv4 IPv625

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.