Network · data from 2026-11-12
AS132445 Khetan Cable Network
Registry name: KHETAN-IN - Khetan Cable Network Pvt. Limited, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS132445, 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.
| 2400:ea80::/32 | No ROA | RIR databaseAPNIC | 636 100% |
| 103.21.53.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.21.54.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.21.55.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.180.38.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.180.39.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.180.80.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.180.81.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.187.100.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.187.101.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.187.160.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.187.161.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 115.166.140.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 115.166.141.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 115.166.142.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 115.166.143.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS132445: AS132445:AS-CUSTOMERS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS132445 isn't in the set, or no route object for AS132445 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS132445 in it | Not covered |
|---|---|---|---|---|---|
| AS132445:AS-CUSTOMERS | APNIC | 3 | 1 | Yes | 0 |
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 5 are in fix.csv.
- ROA: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2400:ea80::/32 | No ROA covers it. Add a ROA for AS132445, maxLength 32. |
Route objects not announced
Route objects with origin AS132445 whose prefix no peer sees AS132445 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.180.38.0/23 | APNIC | Valid |
| 103.180.80.0/23 | APNIC | Valid |
| 103.187.160.0/23 | APNIC | Valid |
| 116.206.151.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.