bgpreport

Network · data from 2026-11-12

AS55701 Usaha Adisanggoro

Registry name: ASNET-AS-ID - PT. Usaha Adisanggoro, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55701, 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.

38.46.214.0/24 Invalid: origin None 6 1%low visibility 3
154.41.81.0/24 Invalid: origin None 6 1%low visibility 4
43.252.236.0/22 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
43.252.236.0/23 Valid Nonecovered by 43.252.236.0/22 672 100% 69
103.20.108.0/23 Valid None 672 100% 69
103.20.109.0/24 Valid None 672 100% 69
103.20.108.0/24 Valid None 671 100% 69
103.163.160.0/24 Valid Other IRR onlyRADB 673 100% 69
43.252.236.0/24 Valid Other IRR onlyRADB 672 100% 69
49.0.0.0/23 Valid Other IRR onlyRADB 672 100% 69
49.0.2.0/23 Valid Other IRR onlyRADB 672 100% 69
103.31.232.0/23 Valid Other IRR onlyRADB 672 100% 69
103.31.232.0/24 Valid Other IRR onlyRADB 672 100% 69
103.213.131.0/24 Valid Other IRR onlyRADB 672 100% 69
49.0.0.0/24 Valid Other IRR onlyRADB 669 99% 69
43.252.237.0/24 Valid RIR databaseAPNIC 672 100% 69
43.252.238.0/24 Valid RIR databaseAPNIC 672 100% 69
49.0.0.0/22 Valid RIR databaseAPNIC, RADB 672 100% 69
49.0.1.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
49.0.2.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
49.0.3.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
86.110.37.0/24 Valid RIR databaseRADB, RIPE 672 100% 69
103.18.76.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
103.18.76.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
103.18.77.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
103.18.78.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
103.18.79.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
103.31.232.0/22 Valid RIR databaseAPNIC, RADB 672 100% 69
103.31.233.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
103.31.234.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
103.31.235.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
202.73.24.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
202.73.27.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
151.243.1.0/24 Valid RIR databaseRADB, RIPE 669 99% 68
2405:b900::/32 Valid RIR databaseAPNIC, RADB 635 100% 70

AS-SET

PeeringDB's irr_as_set for AS55701: AS55701:AS-SET-ASNET-ID. 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 (AS55701 isn't in the set, or no route object for AS55701 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 objectsAS55701 in itNot covered
AS55701:AS-SET-ASNET-ID RADB 181165 No 35
APNIC (also)1 member set in no database: AS55701:AS-ASNET-ID 81126 Yes 5

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

  • ROA: origin2
  • ROA: none1
  • Route object: none6
  • Route object: RIR8
  • AS-SET: own ASN1
  • Route object: not announced58
ChangePrefix or setDetailFull-table peers
ROA: origin38.46.214.0/24ROAs covering it name AS174, not AS55701. If AS55701 should announce it, add a ROA for AS55701.6 of 673
Route object: none38.46.214.0/24No route object for it. Add a route object with origin AS55701 in the RIR database for the space.6 of 673
ROA: origin154.41.81.0/24ROAs covering it name AS174, not AS55701. If AS55701 should announce it, add a ROA for AS55701.6 of 673
Route object: none154.41.81.0/24No route object for it. Add a route object with origin AS55701 in the RIR database for the space.6 of 673
ROA: none43.252.236.0/22No ROA covers it. Add a ROA for AS55701, maxLength 22.672 of 673
Route object: none43.252.236.0/23No route object for it. A route object for 43.252.236.0/22 with origin AS55701 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55701 in the RIR database for the space.672 of 673
Route object: none103.20.108.0/23No route object for it. Add a route object with origin AS55701 in the RIR database for the space.672 of 673
Route object: none103.20.109.0/24No route object for it. Add a route object with origin AS55701 in the RIR database for the space.672 of 673
Route object: none103.20.108.0/24No route object for it. Add a route object with origin AS55701 in the RIR database for the space.671 of 673
Route object: RIR103.163.160.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR43.252.236.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR49.0.0.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR49.0.2.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.31.232.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.31.232.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.213.131.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR49.0.0.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
AS-SET: own ASNAS55701:AS-SET-ASNET-IDAS55701 isn't in AS55701:AS-SET-ASNET-ID (RADB) once expanded. Add AS55701 to it.

Route objects not announced

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

43.252.239.0/24APNICInvalid: origin
103.18.76.0/23RADBValid
103.18.78.0/23RADBValid
103.31.234.0/23RADBValid
202.43.88.0/23RADBNo ROA
202.73.24.0/22APNIC, NTTCOMNo ROA
202.73.24.0/23NTTCOMNo ROA
202.73.25.0/24APNICInvalid: origin
202.73.26.0/23NTTCOMNo ROA
202.73.26.0/24APNICInvalid: origin
2405:b900:1::/48RADBValid
2405:b900:2::/48RADBValid
2405:b900:3::/48RADBValid
2405:b900:4::/48RADBValid
2405:b900:5::/48RADBValid
2405:b900:6::/48RADBValid
2405:b900:7::/48RADBValid
2405:b900:8::/48RADBValid
2405:b900:9::/48RADBValid
2405:b900:10::/48RADBValid
2405:b900:13::/48RADBValid
2405:b900:14::/48RADBValid
2405:b900:15::/48RADBValid
2405:b900:16::/48RADBValid
2405:b900:17::/48RADBValid
2405:b900:18::/48RADBValid
2405:b900:19::/48RADBValid
2405:b900:20::/48RADBValid
2405:b900:21::/48RADBValid
2405:b900:22::/48RADBValid
2405:b900:23::/48RADBValid
2405:b900:24::/48RADBValid
2405:b900:25::/48RADBValid
2405:b900:26::/48RADBValid
2405:b900:27::/48RADBValid
2405:b900:28::/48RADBValid
2405:b900:30::/48RADBValid
2405:b900:31::/48RADBValid
2405:b900:32::/48RADBValid
2405:b900:33::/48RADBValid
2405:b900:34::/48RADBValid
2405:b900:35::/48RADBValid
2405:b900:36::/48RADBValid
2405:b900:37::/48RADBValid
2405:b900:38::/48RADBValid
2405:b900:39::/48RADBValid
2405:b900:40::/48RADBValid
2405:b900:52::/48RADBValid
2405:b900:71::/48RADBValid
2405:b900:72::/48RADBValid
2405:b900:73::/48RADBValid
2405:b900:74::/48RADBValid
2405:b900:75::/48RADBValid
2405:b900:1000::/48RADBValid
2405:b900:2000::/48RADBValid
2405:b900:3000::/48RADBValid
2405:b900:4000::/48RADBValid
2405:b900:5570::/48RADBValid

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.