bgpreport

Network · data from 2026-11-12

AS64053 GRASP-AS-AP - Grasp International Limited

Registry name: GRASP-AS-AP - Grasp International Limited, BD · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS64053, 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.198.168.0/22 Valid RIR databaseAPNIC 672 100% 67
103.198.168.0/24 Valid RIR databaseAPNIC 672 100% 67
103.198.169.0/24 Valid RIR databaseAPNIC 672 100% 67
103.198.170.0/24 Valid RIR databaseAPNIC 672 100% 67
103.198.171.0/24 Valid RIR databaseAPNIC 672 100% 67

AS-SET

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

  • Route object: not announced33

Route objects not announced

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

103.198.168.0/23APNICValid
103.198.170.0/23APNICValid
2401:f1c0::/32APNICValid
2401:f1c0::/33APNICValid
2401:f1c0::/34APNICValid
2401:f1c0::/35APNICValid
2401:f1c0::/36APNICValid
2401:f1c0:1000::/36APNICValid
2401:f1c0:2000::/35APNICValid
2401:f1c0:2000::/36APNICValid
2401:f1c0:3000::/36APNICValid
2401:f1c0:4000::/34APNICValid
2401:f1c0:4000::/35APNICValid
2401:f1c0:4000::/36APNICValid
2401:f1c0:5000::/36APNICValid
2401:f1c0:6000::/35APNICValid
2401:f1c0:6000::/36APNICValid
2401:f1c0:7000::/36APNICValid
2401:f1c0:8000::/33APNICValid
2401:f1c0:8000::/34APNICValid
2401:f1c0:8000::/35APNICValid
2401:f1c0:8000::/36APNICValid
2401:f1c0:9000::/36APNICValid
2401:f1c0:a000::/35APNICValid
2401:f1c0:a000::/36APNICValid
2401:f1c0:b000::/36APNICValid
2401:f1c0:c000::/34APNICValid
2401:f1c0:c000::/35APNICValid
2401:f1c0:c000::/36APNICValid
2401:f1c0:d000::/36APNICValid
2401:f1c0:e000::/35APNICValid
2401:f1c0:e000::/36APNICValid
2401:f1c0:f000::/36APNICValid

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.