Network · data from 2026-11-12
AS9832 ISNNET
Registry name: ISN-AS-AP - ISN, Internet Service Provider, BD · PeeringDB
50IPv4 routes
94.0% RPKI valid · 94.0% with a route object
5IPv6 routes
100.0% RPKI valid · 100.0% with a route object
3RPKI invalid
0 origin · 3 maxLength
0No ROA
3 with no route object for this origin
7Low visibility
seen by under 10% of full-table peers
18Route objects not announced
registered with origin AS9832, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS9832, 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.
| 203.188.248.0/23 | Invalid: maxLength | Nonecovered by 203.188.248.0/21 | 0 0%low visibility |
| 203.188.252.0/23 | Invalid: maxLength | Nonecovered by 203.188.248.0/21 | 0 0%low visibility |
| 203.188.254.0/23 | Invalid: maxLength | Nonecovered by 203.188.248.0/21 | 0 0%low visibility |
| 103.9.132.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 103.9.132.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.9.133.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.9.135.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 180.92.224.0/20 | Valid | RIR databaseAPNIC | 673 100% |
| 180.92.224.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 180.92.226.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 180.92.226.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 180.92.227.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 180.92.228.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 180.92.229.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 180.92.230.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 180.92.232.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 180.92.232.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 180.92.233.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 180.92.238.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 180.92.239.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.148.88.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.188.240.0/20 | Valid | RIR databaseAPNIC | 673 100% |
| 203.188.241.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.188.242.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.188.243.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.188.245.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.188.246.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.188.248.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 203.188.250.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.188.251.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.188.252.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.188.254.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.9.134.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 180.92.224.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 180.92.225.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 180.92.228.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 180.92.231.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 180.92.235.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.188.240.0/21 | Valid | RIR databaseAPNIC | 672 100% |
| 203.188.240.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 203.188.240.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.188.244.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.188.248.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.188.249.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.188.253.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.188.255.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2403:bf80::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 2403:bf80::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2403:bf80:1::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2403:bf80:2::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2403:bf80:3::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 180.92.224.0/21 | Valid | RIR databaseAPNIC | 0 0%low visibility |
| 180.92.234.0/24 | Valid | RIR databaseAPNIC | 0 0%low visibility |
| 203.188.244.0/22 | Valid | RIR databaseAPNIC | 0 0%low visibility |
| 203.188.247.0/24 | Valid | RIR databaseAPNIC | 0 0%low visibility |
AS-SET
AS9832'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 24 are in fix.csv.
- ROA: maxLength3
- Route object: none3
- Route object: not announced18
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 203.188.248.0/23 | ROA 203.188.240.0/20 AS9832 has maxLength 20; ROA 203.188.248.0/21 AS9832 has maxLength 21; the route is a /23. Raise the maxLength, or add a ROA for 203.188.248.0/23. |
| Route object: none | 203.188.248.0/23 | No route object for it. A route object for 203.188.248.0/21 with origin AS9832 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9832 in the RIR database for the space. |
| ROA: maxLength | 203.188.252.0/23 | ROA 203.188.240.0/20 AS9832 has maxLength 20; ROA 203.188.248.0/21 AS9832 has maxLength 21; the route is a /23. Raise the maxLength, or add a ROA for 203.188.252.0/23. |
| Route object: none | 203.188.252.0/23 | No route object for it. A route object for 203.188.248.0/21 with origin AS9832 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9832 in the RIR database for the space. |
| ROA: maxLength | 203.188.254.0/23 | ROA 203.188.240.0/20 AS9832 has maxLength 20; ROA 203.188.248.0/21 AS9832 has maxLength 21; the route is a /23. Raise the maxLength, or add a ROA for 203.188.254.0/23. |
| Route object: none | 203.188.254.0/23 | No route object for it. A route object for 203.188.248.0/21 with origin AS9832 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9832 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9832 whose prefix no peer sees AS9832 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.9.132.0/23 | APNIC | Valid |
| 103.9.134.0/23 | APNIC | Valid |
| 180.92.224.0/23 | APNIC | Valid |
| 180.92.228.0/23 | APNIC | Valid |
| 180.92.230.0/23 | APNIC | Valid |
| 180.92.232.0/22 | APNIC | Valid |
| 180.92.232.0/23 | APNIC | Valid |
| 180.92.234.0/23 | APNIC | Valid |
| 180.92.236.0/22 | APNIC | Valid |
| 180.92.236.0/24 | APNIC | Valid |
| 180.92.237.0/24 | APNIC | Valid |
| 203.148.88.0/22 | APNIC | Valid |
| 203.148.88.0/23 | APNIC | Valid |
| 203.148.89.0/24 | APNIC | Valid |
| 203.148.90.0/23 | APNIC | Valid |
| 203.148.90.0/24 | APNIC | Valid |
| 203.148.91.0/24 | APNIC | Valid |
| 2403:bf80:a::/48 | 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.