asn.dev

Observed topology

AS15945 PFALZKOM-NET Koschatplatz 1

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS15945: 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
AS33891Core-Backbone GmbHHostingIPv4 IPv668
AS174Cogent Communications, LLCTransitIPv4 IPv625

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209400KurpfalzTEL GmbHUnclassifiedIPv480
AS35501Deere & Company CorpUnclassifiedIPv4 IPv672
AS56368Nicola von ThaddenUnclassifiedIPv4 IPv660
AS15492PFALZWERKE AGUnclassifiedIPv411
AS47296HIFX EUROPE LIMITEDUnclassifiedIPv411
AS209917VAG GmbHUnclassifiedIPv411
AS216277DHV e-net GmbHUnclassifiedIPv411
AS215547Megaspace Internet Services GmbHUnclassifiedIPv4 IPv64

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS33891Core-Backbone GmbHHostingIPv4 IPv6267
AS174Cogent Communications, LLCTransitIPv4 IPv686
AS209400KurpfalzTEL GmbHUnclassifiedIPv480
AS35501Deere & Company CorpUnclassifiedIPv4 IPv672
AS56368Nicola von ThaddenUnclassifiedIPv4 IPv660
AS15492PFALZWERKE AGUnclassifiedIPv411
AS47296HIFX EUROPE LIMITEDUnclassifiedIPv411
AS209917VAG GmbHUnclassifiedIPv411
AS216277DHV e-net GmbHUnclassifiedIPv411
AS215547Megaspace Internet Services GmbHUnclassifiedIPv4 IPv64

Provenance

Where this comes from

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