asn.dev

Observed topology

AS263450 AS263450 - NORTE BRASIL NETWORK TELECOMUNICACOES LTDA

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263450: 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
AS2709664W NET ES TELECOMUNICACOES LTDAHostingIPv4 IPv6830
AS271494Soft TelecomUnclassifiedIPv4 IPv66
AS264387OZONIO TELECOMUNICACOES LTDAUnclassifiedIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271656WOMP TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6270
AS262486PRODAM Processamento de Dados Amazonas S.AUnclassifiedIPv463

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2709664W NET ES TELECOMUNICACOES LTDAHostingIPv4 IPv61,098
AS271656WOMP TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6270
AS262486PRODAM Processamento de Dados Amazonas S.AUnclassifiedIPv463
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv460
AS271494Soft TelecomUnclassifiedIPv4 IPv68
AS264387OZONIO TELECOMUNICACOES LTDAUnclassifiedIPv47
AS52863UPX TECNOLOGIA LTDAUnclassifiedIPv41

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.