bgpreport

Network · data from 2026-11-12

AS47542 VKONTAKTE-MSK-CDN-AS LLC VK

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

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
4Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS47542, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS47542, 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.
2a00:bdc0:f000::/36 Valid RIR databaseRIPE 635 100% 68
95.142.204.0/23 Valid RIR databaseRIPE 155 23% 44
95.142.207.0/24 Valid RIR databaseRIPE 155 23% 44
128.140.173.0/24 Valid RIR databaseRIPE 155 23% 44
87.240.166.0/24 Valid RIR databaseRIPE 14 2%low visibility 10
87.240.167.0/24 Valid RIR databaseRIPE 14 2%low visibility 10
95.213.44.0/24 Valid RIR databaseRIPE 14 2%low visibility 10
95.213.45.0/24 Valid RIR databaseRIPE 14 2%low visibility 10

AS-SET

AS47542 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 7 are in fix.csv.

  • Route object: not announced7

Route objects not announced

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

5.181.61.0/24RIPEValid
87.240.166.0/23RIPEValid
89.221.235.0/24RIPEValid
91.231.132.0/24RIPEValid
91.231.133.0/24RIPEValid
91.231.134.0/24RIPEValid
95.213.44.0/23RIPEValid

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.