bgpreport

Network · data from 2026-11-12

AS46054 Wahana Lintas Nusa Persada

Registry name: WLAN-AS-ID - PT Wahana Lintas Nusa Persada, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS46054, 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.
58.145.168.0/21 Valid Other IRR onlyALTDB, RADB 673 100% 69
58.145.173.0/24 Valid Other IRR onlyALTDB, RADB 673 100% 69
58.145.172.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 69
2402:66e0::/32 Valid Other IRR onlyALTDB, RADB 636 100% 68
2402:66e0::/48 Valid Other IRR onlyALTDB 636 100% 68
58.145.168.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
58.145.169.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
58.145.170.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
58.145.171.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
58.145.174.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
58.145.175.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69

AS-SET

AS46054'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 36 are in fix.csv.

  • Route object: RIR5
  • Route object: not announced31
ChangePrefix or setDetailFull-table peers
Route object: RIR58.145.168.0/21Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR58.145.173.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR58.145.172.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2402:66e0::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2402:66e0::/48Route object only in ALTDB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

2402:66e0:1::/48ALTDBValid
2402:66e0:2::/48ALTDBValid
2402:66e0:3::/48ALTDBValid
2402:66e0:4::/48ALTDBValid
2402:66e0:5::/48ALTDBValid
2402:66e0:6::/48ALTDBValid
2402:66e0:7::/48ALTDBValid
2402:66e0:8::/48ALTDBValid
2402:66e0:9::/48ALTDBValid
2402:66e0:a::/48ALTDBValid
2402:66e0:b::/48ALTDBValid
2402:66e0:c::/48ALTDBValid
2402:66e0:d::/48ALTDBValid
2402:66e0:e::/48ALTDBValid
2402:66e0:f::/48ALTDBValid
2402:66e0:10::/48ALTDBValid
2402:66e0:11::/48ALTDBValid
2402:66e0:12::/48ALTDBValid
2402:66e0:13::/48ALTDBValid
2402:66e0:14::/48ALTDBValid
2402:66e0:15::/48ALTDBValid
2402:66e0:16::/48ALTDBValid
2402:66e0:17::/48ALTDBValid
2402:66e0:18::/48ALTDBValid
2402:66e0:19::/48ALTDBValid
2402:66e0:1a::/48ALTDBValid
2402:66e0:1b::/48ALTDBValid
2402:66e0:1c::/48ALTDBValid
2402:66e0:1d::/48ALTDBValid
2402:66e0:1e::/48ALTDBValid
2402:66e0:1f::/48ALTDBValid

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.