bgpreport

Network · data from 2026-11-12

AS140456 PT Era Awan Digital

Registry name: IDNIC-ERANYACLOUD-AS-ID - PT Era Awan Digital, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS140456, 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.
160.22.250.0/24 Valid Nonecovered by 160.22.250.0/23 673 100% 69
160.22.251.0/24 Valid Nonecovered by 160.22.250.0/23 673 100% 69
103.96.146.0/23 Valid Other IRR onlyRADB 673 100% 69
103.96.146.0/24 Valid Other IRR onlyRADB 673 100% 69
103.96.147.0/24 Valid Other IRR onlyRADB 673 100% 69
103.153.60.0/23 Valid Other IRR onlyRADB 673 100% 69
2001:df4:3680::/48 Valid Other IRR onlyRADB 635 100% 70
103.153.60.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
103.153.61.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
160.22.250.0/23 Valid RIR databaseAPNIC, RADB 673 100% 69

AS-SET

AS140456'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.

  • Route object: none2
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
Route object: none160.22.250.0/24No route object for it. A route object for 160.22.250.0/23 with origin AS140456 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140456 in the RIR database for the space.673 of 673
Route object: none160.22.251.0/24No route object for it. A route object for 160.22.250.0/23 with origin AS140456 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140456 in the RIR database for the space.673 of 673
Route object: RIR103.96.146.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.96.146.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.96.147.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.153.60.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2001:df4:3680::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS140456 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.