asn.dev

Observed topology

AS197522 ISP-KIM-NET

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS197522: 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
AS3255LLC EKSINTECHUnclassifiedIPv4 IPv61,024
AS6663Euroweb Romania S.R.L.UnclassifiedIPv4 IPv6466
AS49183"Galichina Telekommunication" LTDResidentialIPv4 IPv6152
AS199995Omega Telecom LLCResidentialIPv486
AS50263A-Systems Sp. z o.o.UnclassifiedIPv46
AS24482SG.GSHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS43047Stream-Network Ltd.UnclassifiedIPv492
AS39680"TOV Karpatnaftokhim"UnclassifiedIPv466

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3255LLC EKSINTECHUnclassifiedIPv4 IPv61,146
AS6663Euroweb Romania S.R.L.UnclassifiedIPv4 IPv6491
AS49183"Galichina Telekommunication" LTDResidentialIPv4 IPv6152
AS43047Stream-Network Ltd.UnclassifiedIPv492
AS199995Omega Telecom LLCResidentialIPv489
AS39680"TOV Karpatnaftokhim"UnclassifiedIPv466
AS50263A-Systems Sp. z o.o.UnclassifiedIPv413
AS24482SG.GSHostingIPv42

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.