asn.dev

Observed topology

AS268935 AS268935 - VibeNet Telecom

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268935: 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 IPv6214
AS265038TELFO SERVICO DE TELECOMUNICACOES LTDAResidentialIPv4 IPv639
AS264293Smart Solucoes em TelecomunicacoesResidentialIPv4 IPv629
AS24482SG.GSHostingIPv4 IPv66
AS35280F5 Networks SARLHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270282SIMONE BARBOSA DO NASCIMENTO SOUZA COMUNICACAOUnclassifiedIPv460
AS272218Luiz Henrique Rocha MacielUnclassifiedIPv632

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6241
AS265038TELFO SERVICO DE TELECOMUNICACOES LTDAResidentialIPv4 IPv676
AS270282SIMONE BARBOSA DO NASCIMENTO SOUZA COMUNICACAOUnclassifiedIPv460
AS264293Smart Solucoes em TelecomunicacoesResidentialIPv4 IPv654
AS272218Luiz Henrique Rocha MacielUnclassifiedIPv632
AS24482SG.GSHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv65
AS35280F5 Networks SARLHostingIPv4 IPv64

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.