asn.dev

Observed topology

AS198769 LLC3DATADC LLC 3data DC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS198769: 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
AS12389PJSC RostelecomResidentialIPv4274
AS201706SERVICEPIPE LLCUnclassifiedIPv4171
AS482193DATA LLCUnclassifiedIPv4110

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215438ANDREY LEBEDEVUnclassifiedIPv461
AS204459LLC 3data DCUnclassifiedIPv424
AS206501LLC Russian cloudsUnclassifiedIPv42
AS208107Evseev Pavel NikolaevichUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4299
AS201706SERVICEPIPE LLCUnclassifiedIPv4188
AS482193DATA LLCUnclassifiedIPv4156
AS215438ANDREY LEBEDEVUnclassifiedIPv461
AS204459LLC 3data DCUnclassifiedIPv424
AS206501LLC Russian cloudsUnclassifiedIPv42
AS208107Evseev Pavel NikolaevichUnclassifiedIPv41

Provenance

Where this comes from

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