asn.dev

Observed topology

AS206262 Telkos TelKos L.L.C

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS206262: 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
AS34772NEOTEL AD SkopjeUnclassifiedIPv4 IPv6984
AS202441mts D.O.OUnclassifiedIPv4808
AS174Cogent Communications, LLCTransitIPv4 IPv6614
AS42313ONE ALBANIA SH.A.UnclassifiedIPv4 IPv6581

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57722N.SH.T "ATI-KOS" sh.p.kUnclassifiedIPv4 IPv6241
AS211458IH-NETWORK SHPKUnclassifiedIPv4 IPv692
AS211468KOSNET Telecommunications LLCUnclassifiedIPv462
AS202969TEB SH.AUnclassifiedIPv460
AS208286Max tv SH. P. KUnclassifiedIPv460
AS211470UBT SH.P.KUnclassifiedIPv460
AS213206Ministry of Internal Affairs (Kosovo)UnclassifiedIPv459
AS210748Edu Invest SH.P.K.UnclassifiedIPv445

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS34772NEOTEL AD SkopjeUnclassifiedIPv4 IPv61,355
AS202441mts D.O.OUnclassifiedIPv4889
AS174Cogent Communications, LLCTransitIPv4 IPv6794
AS42313ONE ALBANIA SH.A.UnclassifiedIPv4 IPv6628
AS57722N.SH.T "ATI-KOS" sh.p.kUnclassifiedIPv4 IPv6241
AS211458IH-NETWORK SHPKUnclassifiedIPv4 IPv692
AS211468KOSNET Telecommunications LLCUnclassifiedIPv462
AS202969TEB SH.AUnclassifiedIPv460
AS208286Max tv SH. P. KUnclassifiedIPv460
AS211470UBT SH.P.KUnclassifiedIPv460

Provenance

Where this comes from

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