asn.dev

Observed topology

AS263468 AS263468 - RAPNET COMUNICACAO MULTIMIDIA LTDA

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263468: 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
AS267670NetLink Telecom LtdaResidentialIPv4 IPv683
AS14840BR.Digital TelecomUnclassifiedIPv475
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv662

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS265026ADN LINKUnclassifiedIPv4 IPv6154
AS267670NetLink Telecom LtdaResidentialIPv4 IPv6114
AS265425NEOLINEPB TELECOMUnclassifiedIPv4 IPv697
AS266218DDL LINE TELECOM LTDAUnclassifiedIPv4 IPv697

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS267670NetLink Telecom LtdaResidentialIPv4 IPv6319
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6246
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6231
AS265026ADN LINKUnclassifiedIPv4 IPv6154
AS265425NEOLINEPB TELECOMUnclassifiedIPv4 IPv697
AS266218DDL LINE TELECOM LTDAUnclassifiedIPv4 IPv697

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.