asn.dev

Observed topology

AS31025 GHOSTnet GmbH

Hosting APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31025: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS24940Hetzner Online GmbHHostingIPv4 IPv697
AS29551Aixit GmbHHostingIPv4 IPv627
AS12360KEVAG Telekom GmbHResidentialIPv423
AS8495INTERNET AG Global NetworkHostingIPv68

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12586GHOSTnet GmbHHostingIPv4 IPv6384
AS24940Hetzner Online GmbHHostingIPv4 IPv6349
AS29551Aixit GmbHHostingIPv4 IPv636
AS12360KEVAG Telekom GmbHResidentialIPv435
AS8495INTERNET AG Global NetworkHostingIPv625
AS57821Nonattached Network e.V.UnclassifiedIPv4 IPv621
AS24482SG.GSHostingIPv4 IPv617
AS202365Omer GOLGELIUnclassifiedIPv410
AS212508Lowhosting services of Davide GennariUnclassifiedIPv48
AS6939Hurricane Electric LLCTransitIPv4 IPv65

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.