Network · data from 2026-11-12
AS137074 RISE-AS-AP - Responsible Internet Sustainability Effort
Registry name: RISE-AS-AP - Responsible Internet Sustainability Effort, PH · not in PeeringDB
40IPv4 routes
92.5% RPKI valid · 92.5% with a route object
0IPv6 routes
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
28Route objects not announced
registered with origin AS137074, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS137074, 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.
| 45.64.81.0/24 | Invalid: maxLength | Nonecovered by 45.64.80.0/22 | 2 0%low visibility |
| 192.82.54.0/24 | Invalid: maxLength | Nonecovered by 192.82.52.0/22 | 2 0%low visibility |
| 192.82.55.0/24 | Invalid: maxLength | Nonecovered by 192.82.52.0/22 | 2 0%low visibility |
| 43.224.188.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 43.224.188.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 43.224.189.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 43.224.190.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 43.224.191.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 43.226.4.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 43.226.4.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 43.226.6.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 45.64.80.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 103.18.64.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 103.18.64.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.18.66.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.18.67.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.25.176.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 103.43.212.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 103.43.213.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.43.214.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.104.16.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.104.18.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.113.40.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 103.113.42.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 116.89.246.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 116.89.247.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 192.82.52.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 203.28.64.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 203.28.64.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.28.65.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.28.66.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.28.67.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.144.0.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.144.2.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 204.144.188.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 204.144.189.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.43.212.0/24 | Valid | RIR databaseAPNIC | 5 1%low visibility |
| 103.113.40.0/23 | Valid | RIR databaseAPNIC | 5 1%low visibility |
| 204.144.190.0/24 | Valid | RIR databaseAPNIC | 5 1%low visibility |
| 204.144.191.0/24 | Valid | RIR databaseAPNIC | 5 1%low visibility |
AS-SET
AS137074 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 34 are in fix.csv.
- ROA: maxLength3
- Route object: none3
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 45.64.81.0/24 | ROA 45.64.80.0/22 AS137074 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 45.64.81.0/24. |
| Route object: none | 45.64.81.0/24 | No route object for it. A route object for 45.64.80.0/22 with origin AS137074 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137074 in the RIR database for the space. |
| ROA: maxLength | 192.82.54.0/24 | ROA 192.82.52.0/22 AS137074 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 192.82.54.0/24. |
| Route object: none | 192.82.54.0/24 | No route object for it. A route object for 192.82.52.0/22 with origin AS137074 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137074 in the RIR database for the space. |
| ROA: maxLength | 192.82.55.0/24 | ROA 192.82.52.0/22 AS137074 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 192.82.55.0/24. |
| Route object: none | 192.82.55.0/24 | No route object for it. A route object for 192.82.52.0/22 with origin AS137074 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137074 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS137074 whose prefix no peer sees AS137074 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.224.188.0/23 | APNIC | Valid |
| 43.224.190.0/23 | APNIC | Valid |
| 43.226.4.0/24 | APNIC | Valid |
| 43.226.5.0/24 | APNIC | Valid |
| 43.226.6.0/24 | APNIC | Valid |
| 43.226.7.0/24 | APNIC | Valid |
| 103.18.64.0/23 | APNIC | Valid |
| 103.18.65.0/24 | APNIC | Valid |
| 103.18.66.0/23 | APNIC | Valid |
| 103.43.212.0/23 | APNIC | Valid |
| 103.43.214.0/23 | APNIC | Valid |
| 103.43.215.0/24 | APNIC | Valid |
| 103.104.16.0/22 | APNIC | Valid |
| 103.104.16.0/24 | APNIC | Valid |
| 103.104.17.0/24 | APNIC | Valid |
| 103.104.18.0/23 | APNIC | Valid |
| 103.104.19.0/24 | APNIC | Valid |
| 103.113.40.0/24 | APNIC | Valid |
| 103.113.41.0/24 | APNIC | Valid |
| 103.113.42.0/23 | APNIC | Valid |
| 103.113.43.0/24 | APNIC | Valid |
| 116.89.246.0/24 | APNIC | Valid |
| 203.28.64.0/23 | APNIC | Valid |
| 203.28.66.0/23 | APNIC | Valid |
| 203.144.0.0/22 | APNIC | Valid |
| 204.144.188.0/23 | APNIC | Valid |
| 204.144.188.0/24 | APNIC | Valid |
| 204.144.190.0/23 | 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.