asn.dev

Observed topology

AS262995 NETDIGITAL TELECOMUNICACOES LTDA

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262995: 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
AS262355VSX NetworksUnclassifiedIPv4 IPv6862
AS53115ISPX Solucoes em Telecomunicacoes SPE LtdaUnclassifiedIPv4268
AS6939Hurricane Electric LLCTransitIPv4164
AS24482SG.GSHostingIPv4 IPv632
AS35280F5 Networks SARLHostingIPv4 IPv612
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv612

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270942GLINK TELECOMUNICACAO LTDAUnclassifiedIPv4 IPv6157

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS262355VSX NetworksUnclassifiedIPv4 IPv6986
AS53115ISPX Solucoes em Telecomunicacoes SPE LtdaUnclassifiedIPv4 IPv6274
AS6939Hurricane Electric LLCTransitIPv4185
AS270942GLINK TELECOMUNICACAO LTDAUnclassifiedIPv4 IPv6157
AS24482SG.GSHostingIPv4 IPv638
AS35280F5 Networks SARLHostingIPv4 IPv612
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv612

Provenance

Where this comes from

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