asn.dev

Observed topology

AS49528 ALFANET-PL-AS MARCIN MALOLEPSZY @ALFANET

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS49528: 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
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv4144
AS50606Horyzont Technologie Internetowe sp.z.o.o.UnclassifiedIPv488
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv412
AS6939Hurricane Electric LLCTransitIPv48
AS24482SG.GSHostingIPv4 IPv66
AS20473The Constant Company, LLCHostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS47896ALFASZYBKINET Sp. z o. o.UnclassifiedIPv466
AS60755Lukasz Istek KomputerLANUnclassifiedIPv466

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv4253
AS50606Horyzont Technologie Internetowe sp.z.o.o.UnclassifiedIPv4104
AS47896ALFASZYBKINET Sp. z o. o.UnclassifiedIPv466
AS60755Lukasz Istek KomputerLANUnclassifiedIPv466
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv417
AS6939Hurricane Electric LLCTransitIPv48
AS24482SG.GSHostingIPv4 IPv68
AS20473The Constant Company, LLCHostingIPv62

Provenance

Where this comes from

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