asn.dev

Observed topology

AS50398 FASTCOMMUNICATIONS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50398: 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
AS6663Euroweb Romania S.R.L.UnclassifiedIPv4 IPv6381
AS6939Hurricane Electric LLCTransitIPv4 IPv660
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv68
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv68
AS206548ZCOM.cz s.r.oHostingIPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210111Netcraft Solutions s.r.o.UnclassifiedIPv4 IPv640

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6663Euroweb Romania S.R.L.UnclassifiedIPv4 IPv6421
AS6939Hurricane Electric LLCTransitIPv4 IPv660
AS210111Netcraft Solutions s.r.o.UnclassifiedIPv4 IPv640
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv68
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv68
AS206548ZCOM.cz s.r.oHostingIPv63

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.