bgpreport

Network · data from 2026-11-12

AS58389 Sumber Data Indonesia NAP

Registry name: SDI-NAP-AS-ID - PT Sumber Data Indonesia, ID · PeeringDB

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

Announced routes

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

2404:fd00:39::/48 Invalid: origin None 17 3%low visibility 14
2404:fd00:40::/48 Invalid: origin None 16 3%low visibility 13
2404:fd00:45::/48 Invalid: origin None 16 3%low visibility 13
2404:fd00:1f::/48 Invalid: origin None 3 0%low visibility 3
2404:fd00::/32 Invalid: origin None 1 0%low visibility 1
2401:a0a0:4::/48 No ROA None 633 100% 67
103.226.119.0/24 No ROA Other IRR onlyRADB 673 100% 68
103.227.248.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 68
2404:fd00:34::/48 Valid None 633 100% 69
2404:fd00:36::/48 Valid None 633 100% 69
2404:fd00:10::/48 Valid None 632 99% 69
114.198.241.0/24 Valid Other IRR onlyRADB 673 100% 67
114.198.247.0/24 Valid Other IRR onlyRADB 673 100% 69
116.68.164.0/24 Valid Other IRR onlyRADB 673 100% 69
116.68.169.0/24 Valid Other IRR onlyRADB 671 100% 68
202.72.207.0/24 Valid Other IRR onlyRADB 671 100% 68
43.240.230.0/24 Valid Other IRR onlyRADB 669 99% 67
43.240.228.0/24 Valid Other IRR onlyRADB 217 32% 57
103.11.28.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
103.11.30.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
103.143.222.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
114.198.243.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
116.68.167.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
202.47.182.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
116.68.165.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
103.11.31.0/24 Valid RIR databaseAPNIC, RADB 217 32% 57

AS-SET

PeeringDB's irr_as_set for AS58389: RADB::AS58389:AS-SDINAP. 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 (AS58389 isn't in the set, or no route object for AS58389 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 objectsAS58389 in itNot covered
RADB::AS58389:AS-SDINAP RADB2 member sets in no database: AS131717:AS-CIFO, AS47311:AS-ATHARVA 448214,198 Yes 9

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

  • ROA: origin5
  • ROA: none3
  • Route object: none9
  • Route object: RIR8
  • AS-SET: missing member2
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: origin2404:fd00:39::/48ROAs covering it name AS58552, not AS58389. If AS58389 should announce it, add a ROA for AS58389.17 of 636
Route object: none2404:fd00:39::/48No route object for it. Add a route object with origin AS58389 in the RIR database for the space.17 of 636
ROA: origin2404:fd00:40::/48ROAs covering it name AS58552, not AS58389. If AS58389 should announce it, add a ROA for AS58389.16 of 636
Route object: none2404:fd00:40::/48No route object for it. Add a route object with origin AS58389 in the RIR database for the space.16 of 636
ROA: origin2404:fd00:45::/48ROAs covering it name AS58552, not AS58389. If AS58389 should announce it, add a ROA for AS58389.16 of 636
Route object: none2404:fd00:45::/48No route object for it. Add a route object with origin AS58389 in the RIR database for the space.16 of 636
ROA: origin2404:fd00:1f::/48ROAs covering it name AS58552, not AS58389. If AS58389 should announce it, add a ROA for AS58389.3 of 636
Route object: none2404:fd00:1f::/48No route object for it. Add a route object with origin AS58389 in the RIR database for the space.3 of 636
ROA: origin2404:fd00::/32ROAs covering it name AS58552, not AS58389. If AS58389 should announce it, add a ROA for AS58389.1 of 636
Route object: none2404:fd00::/32No route object for it. Add a route object with origin AS58389 in the RIR database for the space.1 of 636
ROA: none2401:a0a0:4::/48No ROA covers it. Add a ROA for AS58389, maxLength 48.633 of 636
Route object: none2401:a0a0:4::/48No route object for it. Add a route object with origin AS58389 in the RIR database for the space.633 of 636
ROA: none103.226.119.0/24No ROA covers it. Add a ROA for AS58389, maxLength 24.673 of 673
Route object: RIR103.226.119.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.227.248.0/24No ROA covers it. Add a ROA for AS58389, maxLength 24.673 of 673
Route object: none2404:fd00:34::/48No route object for it. Add a route object with origin AS58389 in the RIR database for the space.633 of 636
Route object: none2404:fd00:36::/48No route object for it. Add a route object with origin AS58389 in the RIR database for the space.633 of 636
Route object: none2404:fd00:10::/48No route object for it. Add a route object with origin AS58389 in the RIR database for the space.632 of 636
Route object: RIR114.198.241.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR114.198.247.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.68.164.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.68.169.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR202.72.207.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR43.240.230.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR43.240.228.0/24Route object only in RADB. Add it in the RIR database for the space.217 of 673
AS-SET: missing memberRADB::AS58389:AS-SDINAPAS58389:AS-SDINAP (RADB) lists AS131717:AS-CIFO; no IRR database read has it.
AS-SET: missing memberRADB::AS58389:AS-SDINAPAS58389:AS-SDINAP (RADB) lists AS47311:AS-ATHARVA; no IRR database read has it.

Route objects not announced

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

103.10.120.0/24APNICInvalid: origin
103.10.121.0/24APNICInvalid: origin
103.10.122.0/24APNICInvalid: origin
103.10.123.0/24APNICInvalid: origin
103.11.28.0/22APNICNo ROA
103.11.29.0/24APNIC, RADBValid
103.58.146.0/24APNICInvalid: origin
103.143.222.0/23APNICValid
103.143.223.0/24APNIC, RADBValid
103.162.233.0/24RADBNo ROA
103.226.118.0/24RADBNo ROA
103.227.249.0/24APNIC, RADBNo ROA
103.227.250.0/24RADBNo ROA
103.227.251.0/24RADBNo ROA
116.68.173.0/24APNICInvalid: origin
202.47.183.0/24APNICValid

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.