asn.dev

Observed topology

AS197204 TELEMAKS

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS197204: 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 RostelecomResidentialIPv4 IPv6613
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6270
AS24482SG.GSHostingIPv4 IPv617
AS9002RETN LimitedUnclassifiedIPv412
AS49673Truenetwork LLCUnclassifiedIPv412

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS41106My Telecom Ltd.UnclassifiedIPv4496
AS57323CJSC "Kubanoptprodtorg"UnclassifiedIPv4248
AS208099TR-Project LTDUnclassifiedIPv461
AS201389I-T EXPERT LLC.UnclassifiedIPv414
AS57314PKI LLCUnclassifiedIPv42
AS59946LLC "Certification Center Orbita"UnclassifiedIPv42
AS51017STOLICA LLCUnclassifiedIPv41

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv61,296
AS41106My Telecom Ltd.UnclassifiedIPv4496
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6374
AS57323CJSC "Kubanoptprodtorg"UnclassifiedIPv4248
AS208099TR-Project LTDUnclassifiedIPv461
AS24482SG.GSHostingIPv4 IPv631
AS49673Truenetwork LLCUnclassifiedIPv426
AS9002RETN LimitedUnclassifiedIPv421
AS201389I-T EXPERT LLC.UnclassifiedIPv414
AS57314PKI LLCUnclassifiedIPv42

All 12 adjacent →

Provenance

Where this comes from

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