bgpreport

Network · data from 2026-11-12

AS151000 PT Awan Data Indonesia

Registry name: IDNIC-MAXCLOUD-AS-ID - PT Awan Data Indonesia, ID · PeeringDB

24IPv4 routes 100.0% RPKI valid · 91.7% 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 AS151000, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS151000, 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.190.1.0/24 Valid None 673 100% 69
103.190.0.0/23 Valid None 672 100% 67
103.153.188.0/24 Valid Other IRR onlyRADB 673 100% 69
103.153.189.0/24 Valid Other IRR onlyRADB 673 100% 69
103.155.225.0/24 Valid Other IRR onlyRADB 673 100% 68
103.179.67.0/24 Valid Other IRR onlyRADB 673 100% 69
103.179.134.0/24 Valid Other IRR onlyRADB 673 100% 69
103.179.135.0/24 Valid Other IRR onlyRADB 673 100% 68
103.184.12.0/24 Valid Other IRR onlyRADB 673 100% 69
103.184.13.0/24 Valid Other IRR onlyRADB 673 100% 69
157.20.254.0/24 Valid Other IRR onlyRADB 673 100% 69
103.139.244.0/24 Valid Other IRR onlyRADB 672 100% 69
103.139.245.0/24 Valid Other IRR onlyRADB 672 100% 69
103.155.224.0/23 Valid Other IRR onlyRADB 672 100% 67
103.155.224.0/24 Valid Other IRR onlyRADB 672 100% 69
103.179.66.0/24 Valid Other IRR onlyRADB 672 100% 69
103.190.0.0/24 Valid Other IRR onlyRADB 672 100% 68
157.20.255.0/24 Valid Other IRR onlyRADB 672 100% 69
103.139.244.0/23 Valid Other IRR onlyRADB 671 100% 67
103.153.188.0/23 Valid Other IRR onlyRADB 671 100% 67
103.179.66.0/23 Valid Other IRR onlyRADB 671 100% 67
103.179.134.0/23 Valid Other IRR onlyRADB 671 100% 67
103.184.12.0/23 Valid Other IRR onlyRADB 671 100% 67
157.20.254.0/23 Valid Other IRR onlyRADB 671 100% 67
2402:12e0::/32 Valid Other IRR onlyRADB 635 100% 68

AS-SET

PeeringDB's irr_as_set for AS151000: AS151000:AS-MAXCLOUD. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS151000 isn't in the set, or no route object for AS151000 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS151000 in itNot covered
AS151000:AS-MAXCLOUD RADB 6140 Yes 2
APNIC (also) 6140 Yes 2

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

  • Route object: none2
  • Route object: RIR23
ChangePrefix or setDetailFull-table peers
Route object: none103.190.1.0/24No route object for it. Add a route object with origin AS151000 in the RIR database for the space.673 of 673
Route object: none103.190.0.0/23No route object for it. Add a route object with origin AS151000 in the RIR database for the space.672 of 673
Route object: RIR103.153.188.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.153.189.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.155.225.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.179.67.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.179.134.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.179.135.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.184.12.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.184.13.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR157.20.254.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.139.244.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.139.245.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.155.224.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.155.224.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.179.66.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.190.0.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR157.20.255.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.139.244.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.153.188.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.179.66.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.179.134.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.184.12.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR157.20.254.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2402:12e0::/32Route 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 AS151000 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.