asn.dev

Observed topology

AS267429 AS267429 - GRAFNET TELECOM

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267429: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6156
AS265038TELFO SERVICO DE TELECOMUNICACOES LTDAResidentialIPv4 IPv662
AS13786Seabras 1 USA, LLCUnclassifiedIPv4 IPv642
AS52320GlobeNet Cabos Submarinos Colombia, S.A.S.UnclassifiedIPv4 IPv638

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS265294ACE COMERCIO E SERVICOS DE INFORMATICA LTDA - MEResidentialIPv4 IPv6179
AS270792luciano comin cardozo-meUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS265294ACE COMERCIO E SERVICOS DE INFORMATICA LTDA - MEResidentialIPv4 IPv6526
AS52320GlobeNet Cabos Submarinos Colombia, S.A.S.UnclassifiedIPv4 IPv6371
AS6939Hurricane Electric LLCTransitIPv4 IPv6222
AS13786Seabras 1 USA, LLCUnclassifiedIPv4 IPv6171
AS265038TELFO SERVICO DE TELECOMUNICACOES LTDAResidentialIPv4 IPv662
AS270792luciano comin cardozo-meUnclassifiedIPv42

Provenance

Where this comes from

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