asn.dev

Observed topology

AS42687 IzarLink1 Izarlink SAS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42687: 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
AS35280F5 Networks SARLHostingIPv4 IPv6314
AS201675SACLAK NETWORK SASResidentialIPv4 IPv6122
AS6939Hurricane Electric LLCTransitIPv4 IPv643
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv66
AS204092Association GRIFONUnclassifiedIPv4 IPv66
AS6696VERIXI SAUnclassifiedIPv45
AS12779IT.Gate S.p.A.UnclassifiedIPv45

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35280F5 Networks SARLHostingIPv4 IPv6314
AS201675SACLAK NETWORK SASResidentialIPv4 IPv6122
AS6939Hurricane Electric LLCTransitIPv4 IPv643
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv66
AS204092Association GRIFONUnclassifiedIPv4 IPv66
AS6696VERIXI SAUnclassifiedIPv45
AS12779IT.Gate S.p.A.UnclassifiedIPv45

Provenance

Where this comes from

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