asn.dev

Observed topology

AS10906 Nucleo de Inf. e Coord. do Ponto BR - NIC.

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS10906: 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
AS52320GlobeNet Cabos Submarinos Colombia, S.A.S.UnclassifiedIPv4 IPv6148
AS5538Institute of Mathematics and Computer Science of University of LatviaEducationIPv4 IPv627
AS22548Nucleo de Inf. e Coord. do Ponto BR - NIC.BRUnclassifiedIPv4 IPv611
AS4608Asia Pacific Network Information CentreUnclassifiedIPv4 IPv66
AS40528ICANNUnclassifiedIPv43
AS24482SG.GSHostingIPv4 IPv62
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv62

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52320GlobeNet Cabos Submarinos Colombia, S.A.S.UnclassifiedIPv4 IPv6148
AS5538Institute of Mathematics and Computer Science of University of LatviaEducationIPv4 IPv627
AS22548Nucleo de Inf. e Coord. do Ponto BR - NIC.BRUnclassifiedIPv4 IPv611
AS4608Asia Pacific Network Information CentreUnclassifiedIPv4 IPv66
AS40528ICANNUnclassifiedIPv43
AS24482SG.GSHostingIPv4 IPv62
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv62

Provenance

Where this comes from

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