Network · data from 2026-11-12
AS58487 Rumahweb Indonesia
Registry name: CRI-AS-AP - CV. Rumahweb Indonesia, ID · PeeringDB
62IPv4 routes
88.7% RPKI valid · 95.2% with a route object
2IPv6 routes
50.0% RPKI valid · 100.0% with a route object
1RPKI invalid
0 origin · 1 maxLength
7No ROA
3 with no route object for this origin
4Low visibility
seen by under 10% of full-table peers
28Route objects not announced
registered with origin AS58487, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS58487, 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.
| 202.10.37.119/32 | Invalid: maxLength | Nonecovered by 202.10.37.0/24 | 0 0%low visibility |
| 202.10.40.0/22 | No ROA | Other origin onlycovered by 202.10.40.0/21 | 669 99% |
| 103.84.206.0/24 | No ROA | Nonecovered by 103.84.206.0/23 | 35 5%low visibility |
| 103.84.206.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 202.10.36.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 202.10.44.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 2001:df0:27b::/48 | No ROA | Other IRR onlyNTTCOM | 635 100% |
| 103.84.207.0/24 | No ROA | Other IRR onlyRADB | 35 5%low visibility |
| 103.253.212.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.253.213.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.253.215.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 103.253.212.0/22 | Valid | Other IRR onlyNTTCOM | 669 99% |
| 2001:df1:7800::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 80.43.0.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 80.43.32.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 80.43.36.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 80.43.40.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 80.43.44.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 80.43.48.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 80.43.52.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 80.43.56.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 80.43.60.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 103.3.233.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.247.8.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.247.9.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.247.10.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.247.11.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.10.34.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 202.10.34.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.10.36.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 202.10.36.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.10.38.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.10.39.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.10.40.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.10.41.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.10.42.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.10.43.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.10.44.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.10.47.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.10.48.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.10.49.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.155.13.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.155.16.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.155.17.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.175.8.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 203.175.11.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.194.112.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 203.194.112.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 203.194.112.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.194.113.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.194.114.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.194.115.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 218.33.124.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 80.43.1.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.247.8.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 203.175.8.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 203.175.9.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 202.10.35.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 202.10.37.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 202.10.45.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 202.10.46.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 203.175.10.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 202.155.136.0/24 | Valid | RIR databaseAPNIC | 667 99% |
| 218.33.100.0/22 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
AS58487'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 49 are in fix.csv.
- ROA: maxLength1
- ROA: none7
- Route object: none3
- Route object: RIR10
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 202.10.37.119/32 | ROA 202.10.36.0/23 AS58487 has maxLength 23; ROA 202.10.37.0/24 AS58487 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 202.10.37.119/32. |
| Route object: none | 202.10.37.119/32 | No route object for it. A route object for 202.10.37.0/24 with origin AS58487 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS58487 in the RIR database for the space. |
| ROA: none | 202.10.40.0/22 | No ROA covers it. Add a ROA for AS58487, maxLength 22. |
| Route object: none | 202.10.40.0/22 | Route objects for it name AS9462, AS24538, AS45180. A route object for 202.10.40.0/21 with origin AS58487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58487 in the RIR database for the space. |
| ROA: none | 103.84.206.0/24 | No ROA covers it. Add a ROA for AS58487, maxLength 24. |
| Route object: none | 103.84.206.0/24 | No route object for it. A route object for 103.84.206.0/23 with origin AS58487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58487 in the RIR database for the space. |
| ROA: none | 103.84.206.0/23 | No ROA covers it. Add a ROA for AS58487, maxLength 23. |
| Route object: RIR | 103.84.206.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 202.10.36.0/22 | No ROA covers it. Add a ROA for AS58487, maxLength 22. |
| Route object: RIR | 202.10.36.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 202.10.44.0/22 | No ROA covers it. Add a ROA for AS58487, maxLength 22. |
| Route object: RIR | 202.10.44.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2001:df0:27b::/48 | No ROA covers it. Add a ROA for AS58487, maxLength 48. |
| Route object: RIR | 2001:df0:27b::/48 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 103.84.207.0/24 | No ROA covers it. Add a ROA for AS58487, maxLength 24. |
| Route object: RIR | 103.84.207.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.253.212.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.253.213.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.253.215.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.253.212.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 2001:df1:7800::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS58487 whose prefix no peer sees AS58487 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.43.0.0/23 | APNIC | Valid |
| 103.247.8.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.247.10.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.253.212.0/23 | NTTCOM, RADB | Valid |
| 103.253.214.0/23 | NTTCOM, RADB | Valid |
| 103.253.214.0/24 | NTTCOM, RADB | Valid |
| 202.10.38.0/23 | APNIC | Valid |
| 202.10.40.0/21 | RADB | No ROA |
| 202.10.40.0/23 | APNIC | Valid |
| 202.10.42.0/23 | APNIC | Valid |
| 202.10.44.0/23 | APNIC | Valid |
| 202.10.46.0/23 | APNIC | Valid |
| 202.10.48.0/23 | APNIC | Valid |
| 203.175.8.0/23 | APNIC | Valid |
| 203.175.10.0/23 | APNIC | Valid |
| 203.194.114.0/23 | APNIC | Valid |
| 218.33.100.0/23 | APNIC | Valid |
| 218.33.100.0/24 | APNIC | Valid |
| 218.33.101.0/24 | APNIC | Valid |
| 218.33.102.0/23 | APNIC | Valid |
| 218.33.102.0/24 | APNIC | Valid |
| 218.33.103.0/24 | APNIC | Valid |
| 218.33.124.0/23 | APNIC | Valid |
| 218.33.124.0/24 | APNIC | Valid |
| 218.33.125.0/24 | APNIC | Valid |
| 218.33.126.0/23 | APNIC | Valid |
| 218.33.126.0/24 | APNIC | Valid |
| 218.33.127.0/24 | 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.