asn.dev

Observed topology

AS62068 SPECTRAIP SpectraIP B.V.

Hosting RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS62068: 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
AS57717FiberXpress BVUnclassifiedIPv4835
AS174Cogent Communications, LLCTransitIPv4 IPv6421
AS6939Hurricane Electric LLCTransitIPv6224
AS3257GTT Communications Inc.TransitIPv4 IPv6221
AS1103SURF B.V.UnclassifiedIPv68
AS24482SG.GSHostingIPv68
AS56662Marcin GondekUnclassifiedIPv68
AS58057Securebit AGUnclassifiedIPv68

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214337Nijmegen B.V.HostingIPv4 IPv6254
AS50868VoIPStarr B.V.UnclassifiedIPv4 IPv6153
AS218878SpectraIP B.V.UnclassifiedIPv458
AS212025Cukman KresimirUnclassifiedIPv633
AS209553NETVAZ LIMITEDUnclassifiedIPv615

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS57717FiberXpress BVUnclassifiedIPv4994
AS174Cogent Communications, LLCTransitIPv4 IPv6608
AS3257GTT Communications Inc.TransitIPv4 IPv6322
AS6939Hurricane Electric LLCTransitIPv6282
AS214337Nijmegen B.V.HostingIPv4 IPv6254
AS50868VoIPStarr B.V.UnclassifiedIPv4 IPv6153
AS218878SpectraIP B.V.UnclassifiedIPv458
AS212025Cukman KresimirUnclassifiedIPv633
AS209553NETVAZ LIMITEDUnclassifiedIPv615
AS1103SURF B.V.UnclassifiedIPv610

All 13 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.