asn.dev

Observed topology

AS50115 WESTELE-UA-AS

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50115: 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
AS35297Dataline LLCUnclassifiedIPv4571
AS50263A-Systems Sp. z o.o.UnclassifiedIPv429
AS24482SG.GSHostingIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv410
AS49673Truenetwork LLCUnclassifiedIPv410
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv410

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS211250TELECOM TRADE LLCUnclassifiedIPv4128
AS201803Stratievska Olga AnatoliivnaUnclassifiedIPv454

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35297Dataline LLCUnclassifiedIPv4732
AS211250TELECOM TRADE LLCUnclassifiedIPv4128
AS201803Stratievska Olga AnatoliivnaUnclassifiedIPv454
AS50263A-Systems Sp. z o.o.UnclassifiedIPv438
AS24482SG.GSHostingIPv413
AS37721Virtual Technologies & SolutionsResidentialIPv413
AS49673Truenetwork LLCUnclassifiedIPv413
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv413

Provenance

Where this comes from

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