asn.dev

Observed topology

AS266044 AS266044 - Nicnet S.A.

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266044: 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
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6182
AS2914NTT America, Inc.TransitIPv4 IPv6106
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv626
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv610
AS1031PEER 1031 LLCUnclassifiedIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268738M3 Net Fibra LTDA - MEResidentialIPv4 IPv6683

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS268738M3 Net Fibra LTDA - MEResidentialIPv4 IPv6683
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6649
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6138
AS2914NTT America, Inc.TransitIPv4 IPv6106
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6100
AS1031PEER 1031 LLCUnclassifiedIPv423

Provenance

Where this comes from

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