asn.dev

Observed topology

AS50153 NET-BIS-AS

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50153: 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
AS51648GIGAINTERNET Sp z o.o.ResidentialIPv41,291
AS24724Atman Sp. z o.o.HostingIPv4169
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv442
AS24115EquinixHostingIPv438
AS24482SG.GSHostingIPv420

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS51792GIGAINTERNET Sp z o.o.UnclassifiedIPv4136
AS35318Inter Com Slawomir LebekUnclassifiedIPv41
AS201793SIGMA A spolka z ograniczona odpowiedzialnosciaUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS51648GIGAINTERNET Sp z o.o.ResidentialIPv41,291
AS24724Atman Sp. z o.o.HostingIPv4206
AS51792GIGAINTERNET Sp z o.o.UnclassifiedIPv4139
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv489
AS24115EquinixHostingIPv475
AS24482SG.GSHostingIPv440
AS35318Inter Com Slawomir LebekUnclassifiedIPv41
AS201793SIGMA A spolka z ograniczona odpowiedzialnosciaUnclassifiedIPv41

Provenance

Where this comes from

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