bgpreport

Network · data from 2026-11-12

AS133360 Awinet Global Mandiri

Registry name: IDNIC-AWINET-AS-ID - PT Awinet Global Mandiri, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133360, 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.101.96.0/24 Invalid: origin Other origin only 23 3%low visibility 17
38.43.64.0/23 No ROA Other IRR onlyRADB 672 100% 67
38.43.64.0/24 No ROA Other IRR onlyRADB 671 100% 67
38.43.65.0/24 No ROA Other IRR onlyRADB 671 100% 67
103.185.43.0/24 Valid None 672 100% 67
2400:5f20:1000::/36 Valid Nonecovered by 2400:5f20::/32 635 100% 67
103.31.109.0/24 Valid Other IRR onlyRADB 671 100% 67
2400:5f20::/32 Valid Other IRR onlyRADB 635 100% 68
103.36.8.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 67
103.36.9.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 67
103.36.10.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 67
103.36.11.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 67

AS-SET

PeeringDB's irr_as_set for AS133360: AS133360:AS-AWINET. 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 (AS133360 isn't in the set, or no route object for AS133360 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 objectsAS133360 in itNot covered
AS133360:AS-AWINET APNIC 6125 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 15 are in fix.csv.

  • ROA: origin1
  • ROA: none3
  • Route object: none3
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin103.101.96.0/24ROAs covering it name AS150940, not AS133360; an AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS133360 should announce it, add a ROA for AS133360.23 of 673
Route object: none103.101.96.0/24Route objects for it name AS150940. Add a route object with origin AS133360 in the RIR database for the space.23 of 673
ROA: none38.43.64.0/23No ROA covers it. Add a ROA for AS133360, maxLength 23.672 of 673
Route object: RIR38.43.64.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.43.64.0/24No ROA covers it. Add a ROA for AS133360, maxLength 24.671 of 673
Route object: RIR38.43.64.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.43.65.0/24No ROA covers it. Add a ROA for AS133360, maxLength 24.671 of 673
Route object: RIR38.43.65.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: none103.185.43.0/24No route object for it. Add a route object with origin AS133360 in the RIR database for the space.672 of 673
Route object: none2400:5f20:1000::/36No route object for it. A route object for 2400:5f20::/32 with origin AS133360 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133360 in the RIR database for the space.635 of 636
Route object: RIR103.31.109.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2400:5f20::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

103.36.8.0/22APNIC, NTTCOM, RADBValid
103.36.8.0/23NTTCOMValid
103.36.10.0/23NTTCOMValid

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.