asn.dev

Observed topology

AS51648 GIGA-AS # 2

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51648: 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
AS6939Hurricane Electric LLCTransitIPv4528
AS49102Connected sp. z o. o.UnclassifiedIPv440
AS24724Atman Sp. z o.o.HostingIPv434
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv416
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv411
AS24482SG.GSHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50153NET BIS SP Z O OResidentialIPv41,350
AS51792GIGAINTERNET Sp z o.o.UnclassifiedIPv4487
AS35318Inter Com Slawomir LebekUnclassifiedIPv464
AS201793SIGMA A spolka z ograniczona odpowiedzialnosciaUnclassifiedIPv464

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv42,395
AS50153NET BIS SP Z O OResidentialIPv41,350
AS51792GIGAINTERNET Sp z o.o.UnclassifiedIPv4524
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv495
AS35318Inter Com Slawomir LebekUnclassifiedIPv464
AS201793SIGMA A spolka z ograniczona odpowiedzialnosciaUnclassifiedIPv464
AS24724Atman Sp. z o.o.HostingIPv460
AS49102Connected sp. z o. o.UnclassifiedIPv451
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv426
AS24482SG.GSHostingIPv45

Provenance

Where this comes from

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