bgpreport

Network · data from 2026-11-12

AS138030 IWAN-AS-AP - IWAN TECHNOLOGY PTE. LTD.

Registry name: IWAN-AS-AP - IWAN TECHNOLOGY PTE. LTD., SG · not in PeeringDB

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

Announced routes

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

154.22.137.0/24 No ROA None 673 100% 67
154.22.148.0/24 No ROA None 673 100% 67
103.191.120.0/24 No ROA None 53 8%low visibility 31
103.191.121.0/24 No ROA None 53 8%low visibility 31
150.242.13.0/24 No ROA Other origin only 9 1%low visibility 9
144.79.252.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
144.79.253.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67

AS-SET

AS138030 isn't in PeeringDB, where networks name their 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 12 are in fix.csv.

  • ROA: none5
  • Route object: none5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none154.22.137.0/24No ROA covers it. Add a ROA for AS138030, maxLength 24.673 of 673
Route object: none154.22.137.0/24No route object for it. Add a route object with origin AS138030 in the RIR database for the space.673 of 673
ROA: none154.22.148.0/24No ROA covers it. Add a ROA for AS138030, maxLength 24.673 of 673
Route object: none154.22.148.0/24No route object for it. Add a route object with origin AS138030 in the RIR database for the space.673 of 673
ROA: none103.191.120.0/24No ROA covers it. Add a ROA for AS138030, maxLength 24.53 of 673
Route object: none103.191.120.0/24No route object for it. Add a route object with origin AS138030 in the RIR database for the space.53 of 673
ROA: none103.191.121.0/24No ROA covers it. Add a ROA for AS138030, maxLength 24.53 of 673
Route object: none103.191.121.0/24No route object for it. Add a route object with origin AS138030 in the RIR database for the space.53 of 673
ROA: none150.242.13.0/24No ROA covers it. Add a ROA for AS138030, maxLength 24.9 of 673
Route object: none150.242.13.0/24Route objects for it name AS133296. Add a route object with origin AS138030 in the RIR database for the space.9 of 673

Route objects not announced

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

2402:44a0::/36APNIC, RADBValid
2402:44a0:1000::/36APNIC, RADBValid

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.