Network · data from 2026-11-12
AS135738 Adn Broadband AS135738
Registry name: ADNBROAD-AS - Adn Broadband, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135738, 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.
| 103.107.9.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.155.72.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.155.72.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.155.73.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.158.120.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.159.34.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.159.34.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.159.35.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.176.56.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.176.56.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.176.57.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.178.60.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.178.60.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.178.61.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.179.170.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.179.170.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.179.171.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.236.212.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.236.212.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.236.213.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2001:df6:2180::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2001:df6:2580::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2001:df6:2a80::/48 | Valid | RIR databaseAPNIC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS135738: AS135738:AS-ADNBROADBAND. 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 (AS135738 isn't in the set, or no route object for AS135738 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 | AS135738 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS135738:AS-ADNBROADBAND | In no IRR database read today. | |||||
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 6 are in fix.csv.
- AS-SET: not found1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: not found | AS135738:AS-ADNBROADBAND | PeeringDB names AS135738:AS-ADNBROADBAND; no IRR database read has it. |
Route objects not announced
Route objects with origin AS135738 whose prefix no peer sees AS135738 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.69.236.0/22 | RADB | No ROA |
| 103.69.236.0/24 | RADB | No ROA |
| 103.69.237.0/24 | RADB | No ROA |
| 103.105.96.0/24 | APNIC | Valid |
| 2001:df1:36c0::/48 | 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.