bgpreport

Network · data from 2026-11-12

AS200487 OOOVPS-AS OOO VPS

Registry name: OOOVPS-AS OOO VPS, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200487, 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.

5.188.26.93/32 Valid Nonecovered by 5.188.26.0/24 6 1%low visibility 4
5.188.24.0/24 Valid RIR databaseRIPE 673 100% 66
5.188.25.0/24 Valid RIR databaseRIPE 673 100% 66
5.188.26.0/24 Valid RIR databaseRIPE 673 100% 66
5.188.27.0/24 Valid RIR databaseRIPE 673 100% 66
5.188.28.0/24 Valid RIR databaseRIPE 673 100% 66
5.188.29.0/24 Valid RIR databaseRIPE 673 100% 66
5.188.30.0/24 Valid RIR databaseRIPE 673 100% 66
5.188.31.0/24 Valid RIR databaseRIPE 673 100% 66
185.105.224.0/24 Valid RIR databaseRIPE 673 100% 66
185.105.225.0/24 Valid RIR databaseRIPE 673 100% 66
185.105.226.0/24 Valid RIR databaseRIPE 673 100% 66
185.105.227.0/24 Valid RIR databaseRIPE 673 100% 66
5.183.188.0/24 Valid RIR databaseRIPE 672 100% 66
5.183.189.0/24 Valid RIR databaseRIPE 672 100% 66
5.183.190.0/24 Valid RIR databaseRIPE 672 100% 66
5.183.191.0/24 Valid RIR databaseRIPE 672 100% 66
2a01:5a60::/32 Valid RIR databaseRIPE 636 100% 69

AS-SET

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

  • Route object: none1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none5.188.26.93/32No route object for it. A route object for 5.188.26.0/24 with origin AS200487 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS200487 in the RIR database for the space.6 of 673

Route objects not announced

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

5.183.188.0/22RIPEValid
5.188.24.0/21RIPEValid
5.188.24.0/22RIPEValid
5.188.28.0/22RIPEValid
185.105.224.0/22RIPEValid
2a01:5a60:1::/48RIPEValid
2a0e:1600::/32RIPEValid
2a0e:1600:1::/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.