asn.dev

Observed topology

AS12399 SCAN-PLUS-AS q.beyond AG

Unclassified RIPE

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS12399: 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 IPv6216
AS9002RETN LimitedUnclassifiedIPv4 IPv643
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv616
AS3320Deutsche Telekom AGMobileIPv4 IPv611
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv66
AS48185team.blue NVUnclassifiedIPv4 IPv66
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv66
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv66
AS212024Marc SchmittUnclassifiedIPv4 IPv66

All 21 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS47309q.beyond AGUnclassifiedIPv4 IPv6360

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6436
AS47309q.beyond AGUnclassifiedIPv4 IPv6360
AS9002RETN LimitedUnclassifiedIPv4 IPv686
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv632
AS3320Deutsche Telekom AGMobileIPv4 IPv621
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv612
AS48185team.blue NVUnclassifiedIPv4 IPv612
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv612
AS212024Marc SchmittUnclassifiedIPv4 IPv612

All 22 adjacent →

Provenance

Where this comes from

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