Network · data from 2026-11-12
AS135817 Esto Broadband
Registry name: ESTO-AS-AP - ESTO MEDIA PRIVATE LIMITED, IN · PeeringDB
38IPv4 routes
100.0% RPKI valid · 100.0% with a route object
16IPv6 routes
50.0% RPKI valid · 50.0% with a route object
6RPKI invalid
0 origin · 6 maxLength
2No ROA
8 with no route object for this origin
25Low visibility
seen by under 10% of full-table peers
14Route objects not announced
registered with origin AS135817, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS135817, 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.
| 2403:8940:8940::/48 | Invalid: maxLength | Nonecovered by 2403:8940::/32 | 95 15% |
| 2403:8940:3::/48 | Invalid: maxLength | Nonecovered by 2403:8940::/32 | 1 0%low visibility |
| 2403:8940:61::/48 | Invalid: maxLength | Nonecovered by 2403:8940::/32 | 1 0%low visibility |
| 2403:8940:600::/48 | Invalid: maxLength | Nonecovered by 2403:8940::/32 | 1 0%low visibility |
| 2403:8940:1f00::/40 | Invalid: maxLength | Nonecovered by 2403:8940::/32 | 1 0%low visibility |
| 2403:8940:a100::/48 | Invalid: maxLength | Nonecovered by 2403:8940::/32 | 1 0%low visibility |
| 2404:9d00::/32 | No ROA | Other origin only | 634 100% |
| 2404:9d00:1a00::/40 | No ROA | None | 6 1%low visibility |
| 43.255.164.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 103.11.80.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 103.11.81.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.52.32.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.78.46.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.97.46.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.97.84.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.110.164.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.123.234.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.147.150.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.148.152.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.148.153.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.162.44.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.170.56.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.170.56.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.170.57.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.215.115.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 157.66.32.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 45.117.1.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 2403:8940::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 2403:8940:2::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2403:8940:40::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2403:8940:1a00::/40 | Valid | RIR databaseAPNIC | 635 100% |
| 2403:8940:abcd::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2403:8940:fffd::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2403:8940:ffff::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2403:8940:e000::/40 | Valid | RIR databaseAPNIC | 634 100% |
| 103.110.164.0/24 | Valid | RIR databaseAPNIC | 42 6%low visibility |
| 103.110.165.0/24 | Valid | RIR databaseAPNIC | 42 6%low visibility |
| 103.123.234.0/24 | Valid | RIR databaseAPNIC | 42 6%low visibility |
| 103.123.235.0/24 | Valid | RIR databaseAPNIC | 42 6%low visibility |
| 103.162.44.0/24 | Valid | RIR databaseAPNIC | 42 6%low visibility |
| 103.162.45.0/24 | Valid | RIR databaseAPNIC | 42 6%low visibility |
| 43.255.164.0/24 | Valid | RIR databaseAPNIC | 6 1%low visibility |
| 43.255.165.0/24 | Valid | RIR databaseAPNIC | 6 1%low visibility |
| 43.255.166.0/24 | Valid | RIR databaseAPNIC | 6 1%low visibility |
| 43.255.167.0/24 | Valid | RIR databaseAPNIC | 6 1%low visibility |
| 103.11.80.0/24 | Valid | RIR databaseAPNIC | 6 1%low visibility |
| 103.11.82.0/24 | Valid | RIR databaseAPNIC | 6 1%low visibility |
| 103.11.83.0/24 | Valid | RIR databaseAPNIC | 6 1%low visibility |
| 103.97.46.0/24 | Valid | RIR databaseAPNIC | 6 1%low visibility |
| 103.97.47.0/24 | Valid | RIR databaseAPNIC | 6 1%low visibility |
| 103.147.150.0/24 | Valid | RIR databaseAPNIC | 6 1%low visibility |
| 103.147.151.0/24 | Valid | RIR databaseAPNIC | 6 1%low visibility |
| 103.148.152.0/24 | Valid | RIR databaseAPNIC | 6 1%low visibility |
| 103.52.32.0/23 | Valid | RIR databaseAPNIC | 3 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS135817: APNIC::AS-ESTO. 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 (AS135817 isn't in the set, or no route object for AS135817 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 | AS135817 in it | Not covered |
|---|---|---|---|---|---|
| APNIC::AS-ESTO | APNIClists itself further down7 member sets in no database: AS-134294, AS-6186, AS-BHARATCO, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL … | 580 | 56 | 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 37 are in fix.csv.
- ROA: maxLength6
- ROA: none2
- Route object: none8
- AS-SET: missing member7
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2403:8940:8940::/48 | ROA 2403:8940::/32 AS135817 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2403:8940:8940::/48. |
| Route object: none | 2403:8940:8940::/48 | No route object for it. A route object for 2403:8940::/32 with origin AS135817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135817 in the RIR database for the space. |
| ROA: maxLength | 2403:8940:3::/48 | ROA 2403:8940::/32 AS135817 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2403:8940:3::/48. |
| Route object: none | 2403:8940:3::/48 | No route object for it. A route object for 2403:8940::/32 with origin AS135817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135817 in the RIR database for the space. |
| ROA: maxLength | 2403:8940:61::/48 | ROA 2403:8940::/32 AS135817 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2403:8940:61::/48. |
| Route object: none | 2403:8940:61::/48 | No route object for it. A route object for 2403:8940::/32 with origin AS135817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135817 in the RIR database for the space. |
| ROA: maxLength | 2403:8940:600::/48 | ROA 2403:8940::/32 AS135817 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2403:8940:600::/48. |
| Route object: none | 2403:8940:600::/48 | No route object for it. A route object for 2403:8940::/32 with origin AS135817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135817 in the RIR database for the space. |
| ROA: maxLength | 2403:8940:1f00::/40 | ROA 2403:8940::/32 AS135817 has maxLength 32; the route is a /40. Raise the maxLength, or add a ROA for 2403:8940:1f00::/40. |
| Route object: none | 2403:8940:1f00::/40 | No route object for it. A route object for 2403:8940::/32 with origin AS135817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135817 in the RIR database for the space. |
| ROA: maxLength | 2403:8940:a100::/48 | ROA 2403:8940::/32 AS135817 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2403:8940:a100::/48. |
| Route object: none | 2403:8940:a100::/48 | No route object for it. A route object for 2403:8940::/32 with origin AS135817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135817 in the RIR database for the space. |
| ROA: none | 2404:9d00::/32 | No ROA covers it. Add a ROA for AS135817, maxLength 32. |
| Route object: none | 2404:9d00::/32 | Route objects for it name AS132051. Add a route object with origin AS135817 in the RIR database for the space. |
| ROA: none | 2404:9d00:1a00::/40 | No ROA covers it. Add a ROA for AS135817, maxLength 40. |
| Route object: none | 2404:9d00:1a00::/40 | No route object for it. Add a route object with origin AS135817 in the RIR database for the space. |
| AS-SET: missing member | APNIC::AS-ESTO | AS-ESTO (APNIC) lists AS-134294; no IRR database read has it. |
| AS-SET: missing member | APNIC::AS-ESTO | AS-ESTO (APNIC) lists AS-6186; no IRR database read has it. |
| AS-SET: missing member | APNIC::AS-ESTO | AS-ESTO (APNIC) lists AS-BHARATCO; no IRR database read has it. |
| AS-SET: missing member | APNIC::AS-ESTO | AS-ESTO (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it. |
| AS-SET: missing member | APNIC::AS-ESTO | AS-ESTO (APNIC) lists AS137609:AS-DCSISPL; no IRR database read has it. |
| AS-SET: missing member | APNIC::AS-ESTO | AS-ESTO (APNIC) lists AS214174:AS-RIPE; no IRR database read has it. |
| AS-SET: missing member | APNIC::AS-ESTO | AS-ESTO (APNIC) lists AS215228:AS-WSNL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS135817 whose prefix no peer sees AS135817 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.255.164.0/23 | APNIC | Valid |
| 43.255.166.0/23 | APNIC | Valid |
| 103.11.80.0/23 | APNIC | Valid |
| 103.11.82.0/23 | APNIC | Valid |
| 103.52.33.0/24 | APNIC | Valid |
| 103.159.239.0/24 | APNIC | Valid |
| 103.177.84.0/24 | APNIC | Valid |
| 103.234.66.0/23 | APNIC | Invalid: origin |
| 163.227.38.0/24 | APNIC | Valid |
| 163.227.39.0/24 | APNIC | Valid |
| 2001:df2:9680::/48 | APNIC | No ROA |
| 2001:df2:da80::/48 | APNIC | Valid |
| 2001:df4:a300::/48 | APNIC | Valid |
| 2001:df6:f180::/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.