asn.dev

Observed topology

AS12625 AS12625 GERMANY

Unclassified RIPE Enterprise

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS12625: 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
AS198949Radware LtdUnclassifiedIPv4 IPv61,007
AS6939Hurricane Electric LLCTransitIPv4 IPv631
AS3356Level 3 Parent, LLCTransitIPv4 IPv628
AS3257GTT Communications Inc.TransitIPv411
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv64
AS12859BIT BVHostingIPv4 IPv62
AS24482SG.GSHostingIPv4 IPv62
AS29632Netassist International EOODUnclassifiedIPv62
AS33891Core-Backbone GmbHHostingIPv42
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv62

All 20 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS15814Clearstream Services S.A.UnclassifiedIPv4 IPv6801

Adjacency

Adjacent networks

All 21

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

ASNetworkTypeFamiliesPaths seen
AS198949Radware LtdUnclassifiedIPv4 IPv61,808
AS15814Clearstream Services S.A.UnclassifiedIPv4 IPv6801
AS6939Hurricane Electric LLCTransitIPv4 IPv631
AS3356Level 3 Parent, LLCTransitIPv4 IPv628
AS3257GTT Communications Inc.TransitIPv411
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv64
AS12859BIT BVHostingIPv4 IPv62
AS24482SG.GSHostingIPv4 IPv62
AS29632Netassist International EOODUnclassifiedIPv62
AS33891Core-Backbone GmbHHostingIPv42

All 21 adjacent →

Provenance

Where this comes from

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