AS201817 VK Tech Kazakhstan LLP #23,311
IPv4 addresses
4,352
IPv6 /48 networks
0
RPKI
5 valid0 no ROA
Peers and downstreams
0
Holder
- AS name
- KZVKTECH
- Description
- VK Tech Kazakhstan LLP
- Organisation
- VK Tech Kazakhstan LLP
- Registered in
- Almaty, Kazakhstan
- Abuse contact
- abuse@corp.mail.ru
- Assigned
- 2022-10-27
- Registered
- 2022-10-28
- Record last changed
- 2026-09-17 15:17 UTC
None announced.
None seen.
None seen.
Upstream graph
Upstreams and their upstreams, from BGP pathsNetwork rating
#23,311 of 123,601 · 44.2/100| Customer cone weight 27%, 0 networks behind this AS |
0 |
| Announced address space weight 22% |
57 |
| Peers and providers weight 16% |
30 |
| Registry record weight 11% |
70 |
| Routing stability weight 11% |
80 |
| RPKI and IPv6 weight 13% |
80 |
Network health
Grade B · 75/100| pass | Prefixes covered by valid ROAs 5 of 5 announced prefixes are RPKI valid. |
25/25 |
| pass | No RPKI invalid announcements None of the announcements is RPKI invalid. |
10/10 |
| fail | Announces IPv6 No IPv6 prefixes are announced. |
0/15 |
| pass | More than one upstream 3 upstreams seen in BGP. |
10/10 |
| pass | Working abuse contact abuse@corp.mail.ru is published. |
15/15 |
| fail | Publishes a geofeed No geofeed found. Without one, location databases have to guess. |
0/10 |
| pass | No prefixes smaller than /24 or /48 All prefixes are /24 (IPv4) or /48 (IPv6) or larger. |
10/10 |
| pass | Registry record maintained Last changed 2026-09-17. |
5/5 |
Routing changes
Last 30 daysNo changes recorded in the last 30 days. Changes are recorded each time the routing data of this AS is refreshed. Get alerts in real time.
WHOIS
aut-num: AS201817 as-name: KZVKTECH org: ORG-VTKL1-RIPE remarks: remarks: ========================================= remarks: Partners remarks: ----------------------------------------- remarks: remarks: remarks: ========================================= remarks: Uplinks remarks: ----------------------------------------- remarks: 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:1103x When advertising to KAZTRANSCOM (AS35104) uplink... remarks: large:201817:1104x When advertising to KDS (AS51878) uplink... remarks: large:201817:1105x When advertising to KAZTEELEPORT (AS207446) 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:41103 Receieved from KAZTRANSCOM remarks: 201817:41104 Receieved from KDS remarks: 201817:41105 Receieved from KAZTEELEPORT remarks: remarks: 201817:50103 Receieved in Astana remarks: remarks: Last Update: February 2023 remarks: ------------------------------------------------------------- remarks: admin-c: VN3650-RIPE tech-c: VN3650-RIPE status: ASSIGNED mnt-by: RIPE-NCC-END-MNT mnt-by: MNT-NETBRIDGE created: 2022-10-28T08:58:45Z last-modified: 2026-09-17T15:17:58Z source: RIPE % 10 routing policy lines (import/export) not shown