asn.dev

Observed topology

AS60150 AREA-7 IP-Routing by area-7 IT-Services GmbH

Unclassified RIPE NSP

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS60150: 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 IPv6283
AS48314Michael Sebastian Schinzel trading as IP-Projects GmbH & Co. KGUnclassifiedIPv4 IPv6235
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6122
AS5405Inter.link GmbHUnclassifiedIPv4 IPv693
AS50304Blix Solutions ASUnclassifiedIPv4 IPv628
AS24482SG.GSHostingIPv4 IPv618
AS401753BIXCE IncUnclassifiedIPv4 IPv618
AS35133Eranium B.V.HostingIPv415
AS206499LOCIX LIMITEDUnclassifiedIPv47
AS20764CJSC RASCOMUnclassifiedIPv45

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS24381BGP.ExchangeHostingIPv4 IPv664

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6310
AS48314Michael Sebastian Schinzel trading as IP-Projects GmbH & Co. KGUnclassifiedIPv4 IPv6239
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6125
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6122
AS24381BGP.ExchangeHostingIPv4 IPv664
AS50304Blix Solutions ASUnclassifiedIPv4 IPv628
AS24482SG.GSHostingIPv4 IPv619
AS401753BIXCE IncUnclassifiedIPv4 IPv618
AS35133Eranium B.V.HostingIPv415
AS206499LOCIX LIMITEDUnclassifiedIPv47

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