Network · data from 2026-11-12
AS213186 Yanoor Islam Khan
Registry name: AYSTOR Yanoor Islam Khan, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213186, 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.61.146.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 2a0f:9400:6161::/48 | Valid | Other IRR onlyRADB | 634 100% |
| 45.158.10.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 62.233.51.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.155.65.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 151.242.92.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 185.224.2.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 199.245.176.0/24 | Valid | RIR databaseARIN | 670 100% |
| 98.142.247.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
| 157.254.223.0/24 | Valid | RIR databaseARIN, RADB | 667 99% |
| 2a10:3c80::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS213186'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 4 are in fix.csv.
- ROA: none1
- Route object: RIR2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.61.146.0/24 | No ROA covers it. Add a ROA for AS213186, maxLength 24. |
| Route object: RIR | 45.61.146.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a0f:9400:6161::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS213186 whose prefix no peer sees AS213186 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 160.250.225.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.