Observed topology
AS51396 PFCLOUD
Hosting Spamhaus ASN-DROP RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS51396: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS49581 | Ferdinand Zink trading as Tube-Hosting | Hosting | IPv4 IPv6 | 1,582 |
| AS62403 | PletX GmbH | Unclassified | IPv4 IPv6 | 609 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 385 |
| AS64457 | Matteo Fruhwald trading as PipeHost e.U. | Unclassified | IPv6 | 333 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 192 |
| AS34779 | T-2, d.o.o. | Residential | IPv4 IPv6 | 96 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 50 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 26 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 16 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 16 |
Transit
Downstream networks
Networks for which AS51396 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS202412 | Omegatech LTD | Unclassified | IPv4 | 477 |
| AS214413 | WYOCORE TECHNOLOGIES LLC | Unclassified | IPv4 | 420 |
| AS197769 | VPS Dedicated LLC | Unclassified | IPv4 | 360 |
| AS209373 | SWISSNET LLC | Hosting | IPv4 | 241 |
| AS208068 | Ludwig Moritz Hodiamont | Unclassified | IPv6 | 192 |
| AS218751 | Fontaine, LLC | Unclassified | IPv4 | 120 |
| AS219067 | Chiara Conti | Unclassified | IPv4 | 117 |
| AS219097 | Fanth sp. z o.o. | Unclassified | IPv4 IPv6 | 97 |
| AS205211 | Tilen Barbiric | Unclassified | IPv4 IPv6 | 96 |
| AS212094 | Andre Schmidt | Unclassified | IPv6 | 74 |
Adjacency
Adjacent networks
Every AS seen directly next to AS51396 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS49581 | Ferdinand Zink trading as Tube-Hosting | Hosting | IPv4 IPv6 | 3,044 |
| AS62403 | PletX GmbH | Unclassified | IPv4 IPv6 | 843 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 649 |
| AS30823 | aurologic GmbH | Hosting | IPv4 | 507 |
| AS202412 | Omegatech LTD | Unclassified | IPv4 | 477 |
| AS214413 | WYOCORE TECHNOLOGIES LLC | Unclassified | IPv4 | 420 |
| AS197769 | VPS Dedicated LLC | Unclassified | IPv4 IPv6 | 396 |
| AS64457 | Matteo Fruhwald trading as PipeHost e.U. | Unclassified | IPv6 | 371 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 244 |
| AS209373 | SWISSNET LLC | Hosting | IPv4 | 241 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M 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.