asn.dev

Observed topology

AS201640 PSHOST-NET psHost Network

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS201640: 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
AS214762Sebastian Stefanek trading as MatHost.euHostingIPv4 IPv6170

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS218646Ksawery DudaUnclassifiedIPv637
AS198038Szymon DabrowskiUnclassifiedIPv636
AS198826Dominik WojtewiczUnclassifiedIPv636
AS213413Michal PawskiUnclassifiedIPv633
AS219327Disaster LimitedUnclassifiedIPv633

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS214762Sebastian Stefanek trading as MatHost.euHostingIPv4 IPv6279
AS401896MISIU LLCUnclassifiedIPv666
AS218646Ksawery DudaUnclassifiedIPv637
AS198038Szymon DabrowskiUnclassifiedIPv636
AS198826Dominik WojtewiczUnclassifiedIPv636
AS213413Michal PawskiUnclassifiedIPv633
AS219327Disaster LimitedUnclassifiedIPv633

Provenance

Where this comes from

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