Network · data from 2026-11-12
AS135663 BENGALHOST-AS-AP - BengalHost
Registry name: BENGALHOST-AS-AP - BengalHost, BD · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135663, 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.
| 23.129.76.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS135663 isn't in PeeringDB, where networks name their AS-SET.
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 66 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced64
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 23.129.76.0/23 | No ROA covers it. Add a ROA for AS135663, maxLength 23. |
| Route object: RIR | 23.129.76.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS135663 whose prefix no peer sees AS135663 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.180.96.0/22 | RADB | No ROA |
| 14.1.96.0/22 | RADB | No ROA |
| 39.109.32.0/23 | RADB | No ROA |
| 43.224.248.0/23 | RADB | No ROA |
| 43.243.192.0/22 | RADB | No ROA |
| 43.251.16.0/23 | RADB | No ROA |
| 43.252.228.0/22 | RADB | No ROA |
| 45.10.172.0/22 | RADB | No ROA |
| 45.11.76.0/22 | RADB | No ROA |
| 45.64.74.0/23 | RADB | No ROA |
| 45.64.112.0/23 | RADB | No ROA |
| 45.92.158.0/23 | RADB | No ROA |
| 45.116.76.0/22 | RADB | No ROA |
| 45.119.52.0/22 | RADB | No ROA |
| 45.120.158.0/24 | RADB | No ROA |
| 45.128.220.0/22 | RADB | No ROA |
| 84.252.100.0/22 | RADB | No ROA |
| 93.90.72.0/22 | RADB | No ROA |
| 93.90.74.0/23 | RADB | No ROA |
| 93.177.76.0/22 | RADB | No ROA |
| 103.21.136.0/22 | RADB | No ROA |
| 103.30.40.0/22 | RADB | No ROA |
| 103.56.112.0/22 | RADB | No ROA |
| 103.59.100.0/22 | RADB | No ROA |
| 103.66.92.0/22 | RADB | No ROA |
| 103.66.216.0/22 | RADB | No ROA |
| 103.85.20.0/22 | RADB | No ROA |
| 103.96.72.0/22 | RADB | No ROA |
| 103.97.128.0/22 | RADB | No ROA |
| 103.100.156.0/22 | RADB | No ROA |
| 103.104.198.0/23 | RADB | No ROA |
| 103.105.23.0/24 | RADB | No ROA |
| 103.109.106.0/23 | RADB | No ROA |
| 103.110.80.0/24 | RADB | No ROA |
| 103.112.68.0/22 | RADB | No ROA |
| 103.126.208.0/22 | RADB | No ROA |
| 103.140.126.0/23 | RADB | No ROA |
| 103.142.102.0/23 | RADB | No ROA |
| 103.146.230.0/23 | RADB | No ROA |
| 103.195.148.0/22 | RADB | No ROA |
| 103.197.24.0/22 | RADB | No ROA |
| 103.212.32.0/22 | RADB | No ROA |
| 103.213.248.0/22 | RADB | No ROA |
| 103.215.80.0/22 | RADB | No ROA |
| 103.226.124.0/22 | RADB | No ROA |
| 103.229.60.0/22 | RADB | No ROA |
| 103.229.116.0/22 | RADB | No ROA |
| 103.229.124.0/22 | RADB | No ROA |
| 103.233.252.0/22 | RADB | No ROA |
| 103.240.180.0/22 | RADB | No ROA |
| 103.240.200.0/22 | RADB | No ROA |
| 103.242.0.0/22 | RADB | No ROA |
| 103.243.24.0/22 | RADB | No ROA |
| 103.255.56.0/22 | RADB | No ROA |
| 144.48.240.0/22 | RADB | No ROA |
| 149.104.15.0/24 | RADB | No ROA |
| 150.129.80.0/22 | RADB | No ROA |
| 185.216.116.0/22 | RADB | No ROA |
| 185.232.92.0/22 | RADB | No ROA |
| 185.243.240.0/22 | RADB | No ROA |
| 203.160.52.0/22 | RADB | No ROA |
| 203.189.232.0/22 | RADB | No ROA |
| 209.40.96.0/19 | RADB | No ROA |
| 209.103.160.0/19 | RADB | No ROA |
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.