asn.dev

Observed topology

AS51175 MULTIPLAYPL-AS Multiplay Sp. z o.o.

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51175: 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
AS29535Orange Polska Spolka AkcyjnaUnclassifiedIPv4 IPv6282
AS1299Arelion Sweden ABTransitIPv4210
AS6939Hurricane Electric LLCTransitIPv4 IPv6190
AS3356Level 3 Parent, LLCTransitIPv4112
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4 IPv686
AS24482SG.GSHostingIPv4 IPv616
AS8218Zayo Infrastructure France SAUnclassifiedIPv414
AS34927iFog GmbHHostingIPv414
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS35209RADIO OPOLE S.A.UnclassifiedIPv451

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS29535Orange Polska Spolka AkcyjnaUnclassifiedIPv4 IPv6299
AS1299Arelion Sweden ABTransitIPv4226
AS6939Hurricane Electric LLCTransitIPv4 IPv6199
AS3356Level 3 Parent, LLCTransitIPv4112
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4 IPv692
AS35209RADIO OPOLE S.A.UnclassifiedIPv451
AS24482SG.GSHostingIPv4 IPv617
AS8218Zayo Infrastructure France SAUnclassifiedIPv415
AS34927iFog GmbHHostingIPv415
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv62

Provenance

Where this comes from

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