bgpreport

Network · data from 2026-11-12

AS153844 Riderz Network Broadband

Registry name: RNBL-AS-AP - Riderz Network Broadband (Private) Limited, PK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS153844, 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.
103.117.160.0/24 Invalid: origin Other origin only 1 0%low visibility 1
103.117.161.0/24 Invalid: origin Other origin only 1 0%low visibility 1
103.72.84.0/24 Valid RIR databaseAPNIC 673 100% 68
103.72.85.0/24 Valid RIR databaseAPNIC 673 100% 68
103.72.87.0/24 Valid RIR databaseAPNIC 673 100% 68
103.94.244.0/24 Valid RIR databaseAPNIC 673 100% 67
103.102.38.0/24 Valid RIR databaseAPNIC 673 100% 67
103.102.40.0/24 Valid RIR databaseAPNIC 673 100% 67
103.102.41.0/24 Valid RIR databaseAPNIC 673 100% 67
163.227.213.0/24 Valid RIR databaseAPNIC 673 100% 66
203.3.132.0/24 Valid RIR databaseAPNIC 673 100% 68
203.11.65.0/24 Valid RIR databaseAPNIC 673 100% 67
203.142.218.0/24 Valid RIR databaseAPNIC 673 100% 68
203.161.179.0/24 Valid RIR databaseAPNIC 673 100% 68
103.72.86.0/24 Valid RIR databaseAPNIC 672 100% 66
163.227.212.0/24 Valid RIR databaseAPNIC 672 100% 66
14.192.153.0/24 Valid RIR databaseAPNIC 671 100% 66
14.192.156.0/24 Valid RIR databaseAPNIC 671 100% 66
14.192.158.0/24 Valid RIR databaseAPNIC 671 100% 66
2402:b60::/32 Valid RIR databaseAPNIC 636 100% 69
2406:c380::/32 Valid RIR databaseAPNIC 627 99% 67

AS-SET

AS153844's PeeringDB record names no 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.

  • ROA: origin2
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin103.117.160.0/24ROAs covering it name AS140594, not AS153844. If AS153844 should announce it, add a ROA for AS153844.1 of 673
Route object: none103.117.160.0/24Route objects for it name AS140594. Add a route object with origin AS153844 in the RIR database for the space.1 of 673
ROA: origin103.117.161.0/24ROAs covering it name AS140594, not AS153844. If AS153844 should announce it, add a ROA for AS153844.1 of 673
Route object: none103.117.161.0/24Route objects for it name AS140594. Add a route object with origin AS153844 in the RIR database for the space.1 of 673

Route objects not announced

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

103.72.84.0/22APNICValid
103.102.40.0/23APNICValid
163.227.212.0/23APNICValid

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.