asn.dev

Observed topology

AS268560 AS268560 - FIBRA VIP

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268560: 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 IPv6187
AS28220Alares Cabo Servicos de Telecomunicacoes S.A.ResidentialIPv4 IPv6171
AS24482SG.GSHostingIPv4 IPv614
AS267613ELETRONET S.A.UnclassifiedIPv411
AS35280F5 Networks SARLHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269126Net Onne - Comercio e Servico de InformaticaUnclassifiedIPv4 IPv6339

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28220Alares Cabo Servicos de Telecomunicacoes S.A.ResidentialIPv4 IPv6401
AS269126Net Onne - Comercio e Servico de InformaticaUnclassifiedIPv4 IPv6339
AS6939Hurricane Electric LLCTransitIPv4 IPv6232
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv670
AS24482SG.GSHostingIPv4 IPv619
AS35280F5 Networks SARLHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46

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.