Observed topology

AS215457 DCS_LLC DCS LLC

Unclassified RIPE

Upstreams 5 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 3

Upstream graph Who carries AS215457, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS215457 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS215457: 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.

AS	Network	Type	Families	Paths seen
AS196695	NetOne Rus JSC	Unclassified	IPv4	131
AS20764	CJSC RASCOM	Unclassified	IPv4 IPv6	108
AS49063	Data Storage Center JSC	Unclassified	IPv4	98
AS35598	INETCOM CARRIER LLC	Unclassified	IPv4 IPv6	74
AS62255	BiMajLink d.o.o.	Unclassified	IPv6	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS40676	Psychz Networks	Hosting	IPv4	61
AS213602	LLC BK Olimp	Unclassified	IPv4	52
AS197591	Cross Technologies JSC	Unclassified	IPv4	39

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS196695	NetOne Rus JSC	Unclassified	IPv4	164
AS20764	CJSC RASCOM	Unclassified	IPv4 IPv6	158
AS35598	INETCOM CARRIER LLC	Unclassified	IPv4 IPv6	142
AS49063	Data Storage Center JSC	Unclassified	IPv4	99
AS40676	Psychz Networks	Hosting	IPv4	61
AS213602	LLC BK Olimp	Unclassified	IPv4	52
AS197591	Cross Technologies JSC	Unclassified	IPv4	39
AS62255	BiMajLink d.o.o.	Unclassified	IPv6	2

Provenance

Where this comes from

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