asn.dev

Observed topology

AS200107 KL-EXT

Unclassified RIPE

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

Transit

Upstream networks

All 23

Networks observed carrying traffic for AS200107: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6378
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6311
AS29226JSC MastertelUnclassifiedIPv4 IPv6299
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6276
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6264
AS199599Telecom-Birzha, LLCUnclassifiedIPv4 IPv6253
AS9002RETN LimitedUnclassifiedIPv4 IPv6251
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6193
AS209030AO Kaspersky LabUnclassifiedIPv4177
AS8470JSC MacomnetUnclassifiedIPv4 IPv6140

All 23 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS154239Neosoft Technologies And Software Pvt LtdUnclassifiedIPv459

Adjacency

Adjacent networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6411
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6311
AS29226JSC MastertelUnclassifiedIPv4 IPv6299
AS9002RETN LimitedUnclassifiedIPv4 IPv6277
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6276
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6264
AS199599Telecom-Birzha, LLCUnclassifiedIPv4 IPv6253
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6193
AS209030AO Kaspersky LabUnclassifiedIPv4177
AS8470JSC MacomnetUnclassifiedIPv4 IPv6140

All 24 adjacent →

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.