Network · data from 2026-11-12
AS141174 INTELLIGENT-AS-AP - INTELLIGENT CONNECTION LIMITED
Registry name: INTELLIGENT-AS-AP - INTELLIGENT CONNECTION LIMITED, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS141174, 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.31.51.0/24 | Invalid: origin | Other origin only | 9 1%low visibility |
| 2400:cb80:813b::/48 | No ROA | None | 635 100% |
| 2400:cb80:813f::/48 | No ROA | None | 635 100% |
| 103.152.246.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 2606:d440:2a::/48 | No ROA | Other IRR onlyRADB | 635 100% |
| 103.155.154.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.155.155.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 2001:df4:d280::/48 | Valid | RIR databaseAPNIC | 635 100% |
AS-SET
AS141174 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 22 are in fix.csv.
- ROA: origin1
- ROA: none4
- Route object: none3
- Route object: RIR2
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 154.31.51.0/24 | ROAs covering it name AS215787, not AS141174. If AS141174 should announce it, add a ROA for AS141174. |
| Route object: none | 154.31.51.0/24 | Route objects for it name AS215787. Add a route object with origin AS141174 in the RIR database for the space. |
| ROA: none | 2400:cb80:813b::/48 | No ROA covers it. Add a ROA for AS141174, maxLength 48. |
| Route object: none | 2400:cb80:813b::/48 | No route object for it. Add a route object with origin AS141174 in the RIR database for the space. |
| ROA: none | 2400:cb80:813f::/48 | No ROA covers it. Add a ROA for AS141174, maxLength 48. |
| Route object: none | 2400:cb80:813f::/48 | No route object for it. Add a route object with origin AS141174 in the RIR database for the space. |
| ROA: none | 103.152.246.0/24 | No ROA covers it. Add a ROA for AS141174, maxLength 24. |
| Route object: RIR | 103.152.246.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 2606:d440:2a::/48 | No ROA covers it. Add a ROA for AS141174, maxLength 48. |
| Route object: RIR | 2606:d440:2a::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS141174 whose prefix no peer sees AS141174 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.152.246.0/23 | NTTCOM | No ROA |
| 103.155.154.0/23 | APNIC, NTTCOM | Valid |
| 210.77.176.0/24 | RADB | No ROA |
| 210.77.177.0/24 | RADB | No ROA |
| 210.77.178.0/24 | RADB | No ROA |
| 210.77.180.0/24 | RADB | No ROA |
| 210.77.181.0/24 | RADB | No ROA |
| 210.77.182.0/24 | RADB | No ROA |
| 210.77.183.0/24 | RADB | No ROA |
| 210.77.184.0/24 | RADB | No ROA |
| 210.77.185.0/24 | RADB | No ROA |
| 210.77.186.0/24 | RADB | No ROA |
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.