bgpreport

Network · data from 2026-11-12

AS200051 VPSLab-Networks RIZKI ABDUL AZIS

Registry name: VPSLab-Networks RIZKI ABDUL AZIS, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200051, 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.
2.27.62.0/24 Valid Other origin only 668 99% 67
5.175.182.0/24 Valid RIR databaseRIPE 669 99% 67
5.175.253.0/24 Valid RIR databaseRIPE 669 99% 67
217.69.174.0/24 Valid RIR databaseRIPE 669 99% 67
5.230.201.0/24 Valid RIR databaseRIPE 664 99% 67
89.106.83.0/24 Valid RIR databaseRIPE 664 99% 67

AS-SET

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

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none2.27.62.0/24Route objects for it name AS30823, AS210457. Add a route object with origin AS200051 in the RIR database for the space.668 of 673

Route objects not announced

Every route object with origin AS200051 is announced.

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.