asn.dev

Observed topology

AS34924 PANKERL-MEDIA

Upstreams 21 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 15
Adjacent (IPv6) 9

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34924: 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 IPv696
AS8772NetAssist LLCUnclassifiedIPv67
AS58299Openfactory GmbH in LiquidationResidentialIPv67
AS29632Netassist International EOODUnclassifiedIPv64
AS58057Securebit AGUnclassifiedIPv63
AS33891Core-Backbone GmbHHostingIPv43
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv63
AS205794JINZE YANGUnclassifiedIPv62
AS202365Omer GOLGELIUnclassifiedIPv41
AS57821Nonattached Network e.V.UnclassifiedIPv41
AS31500Global Network Management IncUnclassifiedIPv41
AS56662Marcin GondekUnclassifiedIPv61
AS57463NetIX Communications JSCUnclassifiedIPv41
AS5405Inter.link GmbHUnclassifiedIPv41
AS34800Securebit AGUnclassifiedIPv41
AS212508Lowhosting services of Davide GennariUnclassifiedIPv41
AS25091IP-Max SAUnclassifiedIPv41
AS4913410VPN Research Network LTDUnclassifiedIPv41
AS20562Broadband Hosting B.V.HostingIPv41
AS206499LOCIX LIMITEDUnclassifiedIPv41

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.

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

24 shown

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv696
AS58299Openfactory GmbH in LiquidationResidentialIPv67
AS8772NetAssist LLCUnclassifiedIPv67
AS29632Netassist International EOODUnclassifiedIPv64
AS33891Core-Backbone GmbHHostingIPv43
AS58057Securebit AGUnclassifiedIPv63
AS24482SG.GSHostingIPv4 IPv63
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv63
AS205794JINZE YANGUnclassifiedIPv62
AS34800Securebit AGUnclassifiedIPv41
AS57821Nonattached Network e.V.UnclassifiedIPv41
AS56662Marcin GondekUnclassifiedIPv61
AS212508Lowhosting services of Davide GennariUnclassifiedIPv41
AS5405Inter.link GmbHUnclassifiedIPv41
AS31500Global Network Management IncUnclassifiedIPv41
AS20562Broadband Hosting B.V.HostingIPv41
AS25091IP-Max SAUnclassifiedIPv41
AS4913410VPN Research Network LTDUnclassifiedIPv41
AS206499LOCIX LIMITEDUnclassifiedIPv41
AS202365Omer GOLGELIUnclassifiedIPv41
AS57463NetIX Communications JSCUnclassifiedIPv41

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.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS34924, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 6 exchanges across 3 countries and 2 regions.

ExchangeLocationTheir addressMember ports
4b42 Internet Exchange PointZurich, Switzerland185.1.125.641,242
KleyReX Internet ExchangeFrankfurt, Germany193.189.82.44475
DE-CIX DusseldorfDüsseldorf, Germany185.1.170.158226
Local Internet Exchange FrankfurtFrankfurt, Germany185.1.167.186223
Local Internet Exchange DüsseldorfDüsseldorf, Germany185.1.155.16214
UNMETERED ExchangeVancouver, Canada192.34.27.11128

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-08 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,137 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.