Network · data from 2026-11-12
AS154568 IRINN-NETADMIN-AS-IN - ECAP EQUITIES LIMITED
Registry name: IRINN-NETADMIN-AS-IN - ECAP EQUITIES LIMITED, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS154568, 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.
| 162.4.74.0/24 | Invalid: origin | Other origin only | 7 1%low visibility |
| 163.128.107.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 163.128.106.0/24 | Valid | RIR databaseAPNIC | 670 100% |
AS-SET
AS154568 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 3 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 162.4.74.0/24 | ROAs covering it name AS141173, not AS154568. If AS154568 should announce it, add a ROA for AS154568. |
| Route object: none | 162.4.74.0/24 | Route objects for it name AS141173. Add a route object with origin AS154568 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS154568 whose prefix no peer sees AS154568 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 163.128.106.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.