View

If you are scraping this block for the prefixes that a AS originates, please use the data dumps in https://bgp.tools/kb/api and cache them

	Prefix	Description
	90.156.248.0/22	LLC VK
	93.183.84.0/22	VK Tech Kazakhstan LLP
	176.123.176.0/22	VK Tech Kazakhstan LLP
	185.47.167.0/24	VK Tech Kazakhstan LLP
	194.31.156.0/22	VK Tech Kazakhstan LLP

---

Network Policy

Click here to learn more about what this graph means and what makes up a network policy Global Aggregation Policy sad_antonelli Policy pedantic_kalam

Chart Display Options

Display links using non straight lines

Prefixes in selected policy

Load all prefixes in policy

---

How are upstreams and downstreams calculated?

Upstreams

	ASN	Description	IPv4	IPv6
	AS35104	Jusan Mobile JSC	✔	✘
	AS41798	JSC Transtelecom	✔	✘

---

Peers

	ASN	Description	IPv4	IPv6
	AS35104	Jusan Mobile JSC	✔	✘
	AS41798	JSC Transtelecom	✔	✘

aut-num:        AS201817
as-name:        KZVKTECH
org:            ORG-VTKL1-RIPE
remarks:
remarks:        =========================================
remarks:        Partners
remarks:        -----------------------------------------
remarks:
import:         from AS47764 accept ANY
export:         to AS47764 announce AS201817
remarks:
remarks:        =========================================
remarks:        Uplinks
remarks:        -----------------------------------------
remarks:
import:         from AS47764 accept ANY
export:         to AS47764 announce AS201817
import:         from AS35104 accept ANY
export:         to AS35104 announce AS201817
import:         from AS41798 accept ANY
export:         to AS41798 announce AS201817
import:         from AS51878 accept ANY
export:         to AS51878 announce AS201817
remarks:
remarks:        =========================================
remarks:        BGP Policy
remarks:        -----------------------------------------
remarks:
remarks:        External communities may be set by some external peers
remarks:        when talking to 201817.
remarks:        They are 201817:[1-3]*
remarks:
remarks:        The following control communities are accepted from any
remarks:        BGP peer (partner/peer/uplink):
remarks:
remarks:        201817:20 - Don't accept prefix
remarks:        201817:2x - Accept prefix and expand its as-path with
remarks:        last AS x (x=1, 2 or 3) times.
remarks:
remarks:        The following control communities are accepted only from
remarks:        partners:
remarks:
remarks:        Community Meaning
remarks:
remarks:        large:201817:1100x When advertising to uplink, specifically:
remarks:        large:201817:1102x When advertising to KAZTTK (AS41798) uplink...
remarks:        large:201817:1103x When advertising to KAZTRANSCOM (AS35104) uplink...
remarks:        large:201817:1104x When advertising to KDS (AS51878) uplink...
remarks:
remarks:        ...x=0 - do not advertise
remarks:        ...x=1, 2 - prepend 201817 1 or 2 times
remarks:        -------------------------------------------------------------
remarks:
remarks:        Other 201817:* communities are deleted.
remarks:        Other *:* communities are passed intact but not to all
remarks:        peers.
remarks:
remarks:        Own routes get local preference 400 (highest).
remarks:        Partner's routes get local preference 300.
remarks:        Technological partner's routes get local preference 250.
remarks:        Peer's and uplink's routes get local preference 200.
remarks:        We don't change lprefs by outer requests, so please don't
remarks:        request us about it.
remarks:
remarks:        -------------------------------------------------------------
remarks:
remarks:        Internal communities are assigned only internally.
remarks:        They may be used by peers to filter some prefixes.
remarks:
remarks:        Community Meaning
remarks:
remarks:        201817:40000 Our own routes
remarks:
remarks:        201817:41100 Receieved from Uplink, specifically:
remarks:        201817:41102 Receieved from TTC
remarks:        201817:41103 Receieved from KAZTRANSCOM
remarks:        201817:41104 Receieved from KDS
remarks:
remarks:        201817:50103 Receieved in Astana
remarks:
remarks:        Last Update: February 2023
remarks:        -------------------------------------------------------------
remarks:
admin-c:        DUMY-RIPE
tech-c:         DUMY-RIPE
status:         ASSIGNED
mnt-by:         RIPE-NCC-END-MNT
mnt-by:         MNT-NETBRIDGE
created:        2022-10-28T08:58:45Z
last-modified:  2026-05-06T13:39:43Z
source:         RIPE
remarks:        ****************************
remarks:        * THIS OBJECT IS MODIFIED
remarks:        * Please note that all data that is generally regarded as personal
remarks:        * data has been removed from this object.
remarks:        * To view the original object, please query the RIPE Database at:
remarks:        * http://www.ripe.net/whois
remarks:        ****************************


organisation:   ORG-VTKL1-RIPE
org-name:       VK Tech Kazakhstan LLP
country:        KZ
org-type:       LIR
address:        Dummy address for ORG-VTKL1-RIPE
# Email removed, Log into bgp.tools to see whois emails/phone numbers
abuse-c:        AR69178-RIPE
mnt-ref:        MNT-NETBRIDGE
mnt-by:         RIPE-NCC-HM-MNT
mnt-by:         MNT-NETBRIDGE
created:        2022-10-18T09:51:37Z
last-modified:  2026-04-29T05:03:45Z
source:         RIPE
remarks:        ****************************
remarks:        * THIS OBJECT IS MODIFIED
remarks:        * Please note that all data that is generally regarded as personal
remarks:        * data has been removed from this object.
remarks:        * To view the original object, please query the RIPE Database at:
remarks:        * http://www.ripe.net/whois
remarks:        ****************************

Last Update: 2026-05-06T13:39:49Z UTC

---

Member of the following AS-SETs

-	Member	ASN Count
RADB	as-hurricane	24734
RIPE	as-retn-actual-v4	12835
RIPE	as-transkz	1322
RIPE	as-kaztelecompeers	1155
RADB	as-emix	24500
RIPE	as-vk	17
RIPE	as-ktcpeers	1162