Network · data from 2026-11-12
AS135724 Allnet Broadband Network Pvt Ltd
Registry name: PVTABNL-AS - Allnet Broadband Network Pvt Ltd, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135724, 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.117.28.0/22 | No ROA | None | 673 100% |
| 103.57.80.0/22 | No ROA | None | 651 97% |
| 103.57.80.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.57.81.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.57.82.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.57.83.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.69.20.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 103.69.20.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.69.21.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.69.22.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.69.23.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.66.188.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 116.66.188.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.66.189.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.66.190.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.66.191.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 45.117.28.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 45.117.29.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 45.117.30.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 45.117.31.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2001:df3:3200::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df4:5c00::/48 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS135724: AS135724:AS-PVTABNL. 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 (AS135724 isn't in the set, or no route object for AS135724 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 | AS135724 in it | Not covered |
|---|---|---|---|---|---|
| AS135724:AS-PVTABNL | APNIC | 17 | 1 | Yes | 2 |
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 8 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.117.28.0/22 | No ROA covers it. Add a ROA for AS135724, maxLength 22. |
| Route object: none | 45.117.28.0/22 | No route object for it. Add a route object with origin AS135724 in the RIR database for the space. |
| ROA: none | 103.57.80.0/22 | No ROA covers it. Add a ROA for AS135724, maxLength 22. |
| Route object: none | 103.57.80.0/22 | No route object for it. Add a route object with origin AS135724 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS135724 whose prefix no peer sees AS135724 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.69.20.0/23 | APNIC | Valid |
| 103.69.22.0/23 | APNIC | Valid |
| 116.66.188.0/23 | APNIC | Valid |
| 116.66.190.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.