Network · data from 2026-11-12
AS132296 Seven Star Digital Network
Registry name: SEVENSTARDIGITAL-AS-AP - Seven Star Digital Network Private Limited, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS132296, 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.
| 43.248.68.0/22 | No ROA | Other origin only | 672 100% |
| 103.57.252.0/22 | No ROA | None | 672 100% |
| 103.255.36.0/22 | No ROA | Other origin only | 672 100% |
| 202.134.158.0/23 | No ROA | None | 672 100% |
| 103.138.211.0/24 | No ROA | None | 2 0%low visibility |
| 43.248.70.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 43.248.71.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.57.252.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.57.253.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.57.254.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.57.255.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.72.72.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 103.72.72.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.72.73.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.72.74.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.72.75.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.147.174.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.157.230.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.157.231.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.162.224.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.162.225.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.171.126.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.171.127.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.233.140.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.233.141.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.255.115.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 163.128.22.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 163.128.23.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.134.144.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.134.150.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.134.151.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.134.152.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.134.153.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.134.158.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.134.159.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 43.248.68.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 43.248.69.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 49.213.39.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.116.169.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.147.175.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.157.206.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.157.207.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.157.230.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.174.26.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.174.27.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.177.58.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.177.58.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.177.59.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.177.128.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.177.129.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.181.147.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.233.140.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.248.202.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.248.203.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.255.36.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.255.37.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.255.38.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.255.39.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 163.128.91.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.134.145.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.134.146.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.134.147.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.134.148.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.134.149.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.134.162.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.134.167.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.134.168.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.134.173.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.134.174.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 45.119.12.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 45.119.13.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 45.119.14.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 45.119.15.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 2402:5c80::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 2406:b580::/32 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS132296: APNIC::AS132296:AS-PEERS. 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 (AS132296 isn't in the set, or no route object for AS132296 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 | AS132296 in it | Not covered |
|---|---|---|---|---|---|
| APNIC::AS132296:AS-PEERS | APNIC | 30 | 1 | Yes | 5 |
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 28 are in fix.csv.
- ROA: none5
- Route object: none5
- Route object: not announced18
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 43.248.68.0/22 | No ROA covers it. Add a ROA for AS132296, maxLength 22. |
| Route object: none | 43.248.68.0/22 | Route objects for it name AS58678. Add a route object with origin AS132296 in the RIR database for the space. |
| ROA: none | 103.57.252.0/22 | No ROA covers it. Add a ROA for AS132296, maxLength 22. |
| Route object: none | 103.57.252.0/22 | No route object for it. Add a route object with origin AS132296 in the RIR database for the space. |
| ROA: none | 103.255.36.0/22 | No ROA covers it. Add a ROA for AS132296, maxLength 22. |
| Route object: none | 103.255.36.0/22 | Route objects for it name AS58678. Add a route object with origin AS132296 in the RIR database for the space. |
| ROA: none | 202.134.158.0/23 | No ROA covers it. Add a ROA for AS132296, maxLength 23. |
| Route object: none | 202.134.158.0/23 | No route object for it. Add a route object with origin AS132296 in the RIR database for the space. |
| ROA: none | 103.138.211.0/24 | No ROA covers it. Add a ROA for AS132296, maxLength 24. |
| Route object: none | 103.138.211.0/24 | No route object for it. Add a route object with origin AS132296 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS132296 whose prefix no peer sees AS132296 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.112.8.0/24 | APNIC | Invalid: origin |
| 103.112.9.0/24 | APNIC | Invalid: origin |
| 103.112.10.0/24 | APNIC | Invalid: origin |
| 103.112.11.0/24 | APNIC | Invalid: origin |
| 103.147.174.0/23 | APNIC | Valid |
| 103.148.138.0/23 | APNIC | Valid |
| 103.148.138.0/24 | APNIC | Valid |
| 103.148.139.0/24 | APNIC | Valid |
| 103.151.16.0/23 | APNIC | Invalid: origin |
| 103.157.206.0/23 | APNIC | Valid |
| 103.162.224.0/23 | APNIC | Valid |
| 103.171.126.0/23 | APNIC | Valid |
| 103.174.26.0/23 | APNIC | Valid |
| 103.176.74.0/24 | APNIC | Invalid: origin |
| 103.248.202.0/23 | APNIC | Valid |
| 202.134.157.0/24 | APNIC | Valid |
| 2407:6fc0::/32 | APNIC | Valid |
| 2407:6fc0:103::/52 | APNIC | Invalid: maxLength |
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.