asn.dev

Observed topology

AS51993 REGION-TV-AS

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51993: 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
AS206621IT-KARKAS LLCUnclassifiedIPv4572
AS50581Ukrainian Telecommunication Group LLCUnclassifiedIPv4183
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4180
AS60159EUROLINE UKRAINE LLCUnclassifiedIPv414
AS24482SG.GSHostingIPv412

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS35588Telecompany LiS LTDUnclassifiedIPv4127
AS47389IT Center Odesa LLCUnclassifiedIPv484

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS206621IT-KARKAS LLCUnclassifiedIPv4773
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4190
AS50581Ukrainian Telecommunication Group LLCUnclassifiedIPv4183
AS35588Telecompany LiS LTDUnclassifiedIPv4127
AS47389IT Center Odesa LLCUnclassifiedIPv484
AS60159EUROLINE UKRAINE LLCUnclassifiedIPv414
AS24482SG.GSHostingIPv412

Provenance

Where this comes from

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