asn.dev

Observed topology

AS262480 AS262480 - CONNECT10 INTERNET EIRELI

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262480: 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
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6198
AS270814ZAAZ PROVEDOR DE INTERNET E TELECOMUNICACOES LTDAResidentialIPv4 IPv6186
AS6939Hurricane Electric LLCTransitIPv4 IPv6173
AS1031PEER 1031 LLCUnclassifiedIPv426
AS24482SG.GSHostingIPv4 IPv613
AS35280F5 Networks SARLHostingIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv47

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267490C e B do Amaral Comunicacao - MEResidentialIPv4 IPv6343
AS266164Henrique Esdras dos Santos - MEUnclassifiedIPv4207

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS270814ZAAZ PROVEDOR DE INTERNET E TELECOMUNICACOES LTDAResidentialIPv4 IPv6487
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6383
AS267490C e B do Amaral Comunicacao - MEResidentialIPv4 IPv6343
AS6939Hurricane Electric LLCTransitIPv4 IPv6221
AS266164Henrique Esdras dos Santos - MEUnclassifiedIPv4 IPv6217
AS1031PEER 1031 LLCUnclassifiedIPv450
AS24482SG.GSHostingIPv4 IPv617
AS35280F5 Networks SARLHostingIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS11432Telium Telecomunicacoes LtdaHostingIPv62

Provenance

Where this comes from

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