Network · data from 2026-11-12
AS132730 Maximum Business Information Technology
Registry name: MBIT-KH - Maximum Business Information Technology, KH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS132730, 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.24.32.0/22 | Valid | RIR databaseALTDB, APNIC, NTTCOM, RADB | 673 100% |
| 103.24.32.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.24.33.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.24.34.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.24.35.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.224.28.0/22 | Valid | RIR databaseALTDB, APNIC, NTTCOM, RADB | 673 100% |
| 103.224.30.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.224.31.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.224.29.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.224.28.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.231.60.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 103.231.60.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 103.231.61.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 103.231.62.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 103.231.63.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
AS-SET
AS132730's PeeringDB record names no 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 50 are in fix.csv.
- Route object: not announced50
Route objects not announced
Route objects with origin AS132730 whose prefix no peer sees AS132730 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.24.32.0/23 | NTTCOM, RADB | Valid |
| 103.24.34.0/23 | NTTCOM, RADB | Valid |
| 103.88.155.0/24 | APNIC | Valid |
| 103.88.162.0/24 | APNIC | Valid |
| 103.224.28.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.224.30.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.240.112.0/22 | APNIC | Valid |
| 103.240.112.0/24 | APNIC | Valid |
| 103.240.113.0/24 | APNIC | Valid |
| 103.240.114.0/24 | APNIC | Valid |
| 103.240.115.0/24 | APNIC | Valid |
| 120.136.24.0/21 | APNIC | Valid |
| 120.136.24.0/24 | APNIC | Valid |
| 120.136.25.0/24 | APNIC | Valid |
| 120.136.26.0/24 | APNIC | Valid |
| 120.136.27.0/24 | APNIC | Valid |
| 120.136.28.0/24 | APNIC | Valid |
| 120.136.29.0/24 | APNIC | Valid |
| 120.136.30.0/24 | APNIC | Valid |
| 120.136.31.0/24 | APNIC | Valid |
| 124.108.48.0/21 | APNIC | Valid |
| 124.108.48.0/24 | APNIC | Valid |
| 124.108.49.0/24 | APNIC | Valid |
| 124.108.50.0/24 | APNIC | Valid |
| 124.108.51.0/24 | APNIC | Valid |
| 124.108.52.0/23 | APNIC | Valid |
| 124.108.52.0/24 | APNIC | Valid |
| 124.108.53.0/24 | APNIC | Valid |
| 124.108.54.0/24 | APNIC | Valid |
| 124.108.55.0/24 | APNIC | Valid |
| 160.202.32.0/22 | RADB | No ROA |
| 160.202.32.0/23 | RADB | No ROA |
| 160.202.34.0/23 | RADB | No ROA |
| 163.53.28.0/22 | ALTDB, APNIC, NTTCOM, RADB | Valid |
| 163.53.28.0/23 | NTTCOM, RADB | Valid |
| 163.53.28.0/24 | APNIC, NTTCOM, RADB | Valid |
| 163.53.29.0/24 | APNIC, NTTCOM, RADB | Valid |
| 163.53.30.0/23 | NTTCOM, RADB | Valid |
| 163.53.30.0/24 | APNIC, NTTCOM, RADB | Valid |
| 163.53.31.0/24 | APNIC, NTTCOM, RADB | Valid |
| 183.81.184.0/21 | APNIC | Valid |
| 183.81.184.0/24 | APNIC | Valid |
| 183.81.185.0/24 | APNIC | Valid |
| 183.81.186.0/24 | APNIC | Valid |
| 183.81.187.0/24 | APNIC | Valid |
| 183.81.188.0/24 | APNIC | Valid |
| 183.81.189.0/24 | APNIC | Valid |
| 183.81.190.0/24 | APNIC | Valid |
| 183.81.191.0/24 | APNIC | Valid |
| 2406:b100::/32 | 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.