asn.dev

Observed topology

AS60880 AS60880 - Horizon Telecom B.V.

Unclassified RIPE NSP

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS60880: 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
AS60068Datacamp LimitedHostingIPv4196
AS6939Hurricane Electric LLCTransitIPv4 IPv6154
AS174Cogent Communications, LLCTransitIPv474
AS43366OSSO B.V.HostingIPv4 IPv661
AS24482SG.GSHostingIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv610
AS1103SURF B.V.UnclassifiedIPv4 IPv69
AS20766Association "Gitoyen"UnclassifiedIPv47
AS34927iFog GmbHHostingIPv47
AS58057Securebit AGUnclassifiedIPv47

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205142Flex Ltd.UnclassifiedIPv4104
AS208537M3 Groep BVUnclassifiedIPv491
AS202892Bestseller A/SUnclassifiedIPv461

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS60068Datacamp LimitedHostingIPv4356
AS6939Hurricane Electric LLCTransitIPv4 IPv6164
AS174Cogent Communications, LLCTransitIPv4142
AS205142Flex Ltd.UnclassifiedIPv4104
AS208537M3 Groep BVUnclassifiedIPv491
AS43366OSSO B.V.HostingIPv4 IPv674
AS202892Bestseller A/SUnclassifiedIPv461
AS24482SG.GSHostingIPv4 IPv611
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv611
AS1103SURF B.V.UnclassifiedIPv4 IPv610

All 17 adjacent →

Provenance

Where this comes from

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