bgpreport

Network · data from 2026-11-12

AS28709 VKONTAKTE-REGIONAL-CDN LLC VK

Registry name: VKONTAKTE-REGIONAL-CDN LLC VK, RU · not in PeeringDB

21IPv4 routes 100.0% RPKI valid · 100.0% with a route object
5IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
7Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS28709, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS28709, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
95.142.202.0/24 Valid RIR databaseRIPE 673 100% 67
178.237.28.0/24 Valid RIR databaseRIPE 673 100% 67
95.142.201.0/24 Valid RIR databaseRIPE 672 100% 67
95.142.203.0/24 Valid RIR databaseRIPE 672 100% 67
128.140.170.0/24 Valid RIR databaseRIPE 672 100% 67
178.237.17.0/24 Valid RIR databaseRIPE 672 100% 67
178.237.18.0/24 Valid RIR databaseRIPE 672 100% 66
178.237.19.0/24 Valid RIR databaseRIPE 672 100% 67
178.237.22.0/24 Valid RIR databaseRIPE 672 100% 67
178.237.24.0/24 Valid RIR databaseRIPE 672 100% 67
185.32.251.0/24 Valid RIR databaseRIPE 672 100% 67
178.237.16.0/24 Valid RIR databaseRIPE 671 100% 67
178.237.21.0/24 Valid RIR databaseRIPE 671 100% 67
185.32.249.0/24 Valid RIR databaseRIPE 671 100% 67
2a00:bdc0:e003::/48 Valid RIR databaseRIPE 635 100% 68
2a00:bdc0:e004::/48 Valid RIR databaseRIPE 635 100% 68
2a00:bdc0:e005::/48 Valid RIR databaseRIPE 635 100% 68
2a00:bdc0:e002::/48 Valid RIR databaseRIPE 634 100% 68
2a00:bdc0:e007::/48 Valid RIR databaseRIPE 634 100% 68
5.181.61.0/24 Valid RIR databaseRIPE 12 2%low visibility 10
87.240.166.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
87.240.167.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
91.231.133.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
91.231.134.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
95.213.44.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
95.213.45.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS28709 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 6 are in fix.csv.

  • Route object: not announced6

Route objects not announced

Route objects with origin AS28709 whose prefix no peer sees AS28709 announce. Many are kept on purpose (backup routes, space announced only in some places).

87.240.166.0/23RIPEValid
89.221.235.0/24RIPEValid
91.231.132.0/24RIPEValid
95.213.44.0/23RIPEValid
185.32.250.0/24RIPEValid
2a00:bdc0:e008::/48RIPEValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.