Skip to content

Autonomous System

AS199669 — ATLEX-AS - Okay-Telecom Ltd.(RU)

Last fetched

AS199669 is an Autonomous System operated by ATLEX-AS - Okay-Telecom Ltd. and registered in RU. As of Sun, 06 Sep 2026 14:04:24 GMT, it announces 16 routed IP prefixes and peers with 13 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS199669Routing diversity6.1/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/199669

Routing footprint

AS199669 announces 16 distinct routed prefixes. The 16-prefix sample below links to per-prefix pages with full conflict and reverse-DNS detail.

Peering ecosystem

13 distinct peers via BGP. The first 13 are listed below.

Peer ASNOperatorCountry
AS199599CIREX - Telecom-Birzha, LLCRU
AS208972gibirnet-tr - GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETITR
AS24482SGGS-AS-AP - SG.GSSG
AS29076CITYTELECOM-AS - Citytelecom LLCRU
AS31500GNM-AS - Global Network Management IncAG
AS37721Virtual Technologies & Solutions - Virtual Technologies & SolutionsBF
AS49673TRUENETWORK - Truenetwork LLCRU
AS50673Serverius-as - Serverius Holding B.V.NL
AS51248HOST-TELECOM - Host-Telecom.com s.r.o.CZ
AS56655GIGAHOST - Gigahost ASNO
AS57304RETNRU-AS - JSC "RetnNet"RU
AS6939HURRICANE - Hurricane Electric LLCUS
AS9002RETN-AS - RETN LimitedGB

Blast radius

Count of dependent hostnames if AS199669 disappeared from the routing table.

Blast radius: Computing — check back later. The precompute pipeline refreshes this panel within a few days.

MOAS / hijack watch

Prefixes routed by AS199669 that another Autonomous System also announces. A non-empty list is one of the strongest BGP-hijack signals available without active probes.

No active MOAS conflicts. Every prefix announced by AS199669 is unique to AS199669 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS199669.

Cypher and MCP

Reproduce the headline metric directly against graph.whisper.security:

MATCH (a:ASN {name: "AS199669"})-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN a.name AS asn, n.name AS operator, c.name AS country

Or query Whisper from your own LLM workflow via the Whisper MCP server.