Network · data from 2026-11-12
AS153706 STACKNETWORK-AS-AP - Stack Network Sdn. Bhd.
Registry name: STACKNETWORK-AS-AP - Stack Network Sdn. Bhd., MY · not in PeeringDB
29IPv4 routes
86.2% RPKI valid · 86.2% with a route object
2IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
4No ROA
4 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
32Route objects not announced
registered with origin AS153706, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS153706, 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.
| 43.229.152.0/23 | No ROA | None | 667 99% |
| 103.133.136.0/23 | No ROA | None | 664 99% |
| 103.133.136.0/24 | No ROA | Other IRR onlyRADB | 557 83% |
| 103.133.137.0/24 | No ROA | Other IRR onlyRADB | 557 83% |
| 156.254.20.0/24 | Valid | Other origin onlycovered by 156.254.20.0/23 | 670 100% |
| 156.254.21.0/24 | Valid | Other origin onlycovered by 156.254.20.0/23 | 561 83% |
| 156.254.20.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 66.212.56.0/24 | Valid | RIR databaseARIN | 673 100% |
| 66.212.57.0/24 | Valid | RIR databaseARIN | 673 100% |
| 66.212.58.0/23 | Valid | RIR databaseARIN | 671 100% |
| 103.228.64.0/23 | Valid | RIR databaseAPNIC | 671 100% |
| 104.253.124.0/23 | Valid | RIR databaseARIN, RADB | 671 100% |
| 163.223.146.0/23 | Valid | RIR databaseAPNIC | 671 100% |
| 163.223.146.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 172.252.172.0/23 | Valid | RIR databaseARIN, RADB | 671 100% |
| 172.252.224.0/23 | Valid | RIR databaseARIN, RADB | 671 100% |
| 154.89.194.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 2402:7fa0:2000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2402:7fa0:1000::/36 | Valid | RIR databaseAPNIC | 634 100% |
| 172.252.173.0/24 | Valid | RIR databaseARIN | 564 84% |
| 172.252.224.0/24 | Valid | RIR databaseARIN | 564 84% |
| 172.252.225.0/24 | Valid | RIR databaseARIN | 564 84% |
| 103.48.169.0/24 | Valid | RIR databaseAPNIC | 563 84% |
| 103.228.64.0/24 | Valid | RIR databaseAPNIC | 563 84% |
| 104.253.124.0/24 | Valid | RIR databaseARIN | 563 84% |
| 104.253.125.0/24 | Valid | RIR databaseARIN | 563 84% |
| 163.223.147.0/24 | Valid | RIR databaseAPNIC | 563 84% |
| 172.252.172.0/24 | Valid | RIR databaseARIN | 563 84% |
| 43.229.153.0/24 | Valid | RIR databaseAPNIC, RADB | 562 84% |
| 66.212.58.0/24 | Valid | RIR databaseARIN | 562 84% |
| 66.212.59.0/24 | Valid | RIR databaseARIN | 562 84% |
AS-SET
AS153706 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 43 are in fix.csv.
- ROA: none4
- Route object: none4
- Route object: RIR3
- Route object: not announced32
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 43.229.152.0/23 | No ROA covers it. Add a ROA for AS153706, maxLength 23. |
| Route object: none | 43.229.152.0/23 | No route object for it. Add a route object with origin AS153706 in the RIR database for the space. |
| ROA: none | 103.133.136.0/23 | No ROA covers it. Add a ROA for AS153706, maxLength 23. |
| Route object: none | 103.133.136.0/23 | No route object for it. Add a route object with origin AS153706 in the RIR database for the space. |
| ROA: none | 103.133.136.0/24 | No ROA covers it. Add a ROA for AS153706, maxLength 24. |
| Route object: RIR | 103.133.136.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.133.137.0/24 | No ROA covers it. Add a ROA for AS153706, maxLength 24. |
| Route object: RIR | 103.133.137.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 156.254.20.0/24 | Route objects for it name AS400619. A route object for 156.254.20.0/23 with origin AS153706 covers it (filters allowing more-specifics accept it). Add a route object with origin AS153706 in the RIR database for the space. |
| Route object: none | 156.254.21.0/24 | Route objects for it name AS400619. A route object for 156.254.20.0/23 with origin AS153706 covers it (filters allowing more-specifics accept it). Add a route object with origin AS153706 in the RIR database for the space. |
| Route object: RIR | 156.254.20.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS153706 whose prefix no peer sees AS153706 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.41.8.0/23 | ARIN | Valid |
| 66.212.56.0/23 | ARIN | Valid |
| 128.242.182.0/23 | NTTCOM | Valid |
| 154.193.208.0/24 | AFRINIC | Invalid: origin |
| 154.193.209.0/24 | AFRINIC | Invalid: origin |
| 154.193.210.0/24 | AFRINIC | Invalid: origin |
| 154.193.211.0/24 | AFRINIC | Invalid: origin |
| 154.193.247.0/24 | AFRINIC | Invalid: origin |
| 157.238.248.0/22 | NTTCOM | Valid |
| 165.254.160.0/23 | NTTCOM | Valid |
| 165.254.210.0/23 | NTTCOM | Valid |
| 165.254.226.0/23 | NTTCOM | Valid |
| 165.254.228.0/23 | NTTCOM | Valid |
| 165.254.234.0/23 | NTTCOM | Valid |
| 165.254.240.0/23 | NTTCOM | Valid |
| 192.217.0.0/21 | NTTCOM | Valid |
| 192.217.232.0/21 | NTTCOM | Valid |
| 192.217.240.0/21 | NTTCOM | Valid |
| 204.1.142.0/23 | NTTCOM | Valid |
| 204.1.240.0/22 | NTTCOM | Valid |
| 204.2.202.0/23 | NTTCOM | Valid |
| 204.2.236.0/23 | NTTCOM | Valid |
| 204.141.206.0/23 | NTTCOM | Valid |
| 204.141.244.0/23 | NTTCOM | Valid |
| 206.163.14.0/23 | NTTCOM | Valid |
| 209.227.16.0/21 | NTTCOM | Valid |
| 209.227.50.0/23 | NTTCOM | Valid |
| 209.227.56.0/21 | NTTCOM | Valid |
| 209.227.64.0/21 | NTTCOM | Valid |
| 209.227.76.0/23 | NTTCOM | Valid |
| 209.227.84.0/23 | NTTCOM | Valid |
| 2402:7fa0::/32 | APNIC | Valid |
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.