Network · data from 2026-11-12
AS55309 MTT-AS-VN - Minh Tu Telecom Limited Company
Registry name: MTT-AS-VN - Minh Tu Telecom Limited Company, VN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS55309, 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.
| 112.109.90.80/32 | Invalid: maxLength | Nonecovered by 112.109.90.0/24 | 2 0%low visibility |
| 112.109.92.99/32 | Invalid: maxLength | Nonecovered by 112.109.92.0/24 | 2 0%low visibility |
| 2405:cb00::/40 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:1::/48 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:2::/48 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:3::/48 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:11::/48 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:12::/48 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:13::/48 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:14::/48 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:15::/48 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:16::/48 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:17::/48 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:20::/48 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:21::/48 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:22::/48 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:23::/48 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:100::/40 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:7e00::/48 | Valid | Nonecovered by 2405:cb00::/32 | 636 100% |
| 2405:cb00:10::/48 | Valid | Nonecovered by 2405:cb00::/32 | 334 53% |
| 2405:cb00::/48 | Valid | Other IRR onlyNTTCOM | 335 53% |
| 112.109.88.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 112.109.94.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 112.109.95.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 182.237.20.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 182.237.21.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.235.208.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.235.208.0/23 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.235.208.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.235.209.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.235.210.0/23 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.235.210.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 112.109.88.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 112.109.88.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 112.109.88.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 112.109.89.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 112.109.90.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 112.109.90.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 112.109.91.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 112.109.92.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 112.109.92.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 112.109.92.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 112.109.93.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 112.109.94.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 182.237.20.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 182.237.20.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 182.237.22.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 182.237.22.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 182.237.23.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.235.211.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 2405:cb00::/32 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
AS55309 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 23 are in fix.csv.
- ROA: maxLength2
- Route object: none20
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 112.109.90.80/32 | ROA 112.109.88.0/21 AS55309 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 112.109.90.80/32. |
| Route object: none | 112.109.90.80/32 | No route object for it. A route object for 112.109.90.0/24 with origin AS55309 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS55309 in the RIR database for the space. |
| ROA: maxLength | 112.109.92.99/32 | ROA 112.109.88.0/21 AS55309 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 112.109.92.99/32. |
| Route object: none | 112.109.92.99/32 | No route object for it. A route object for 112.109.92.0/24 with origin AS55309 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00::/40 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:1::/48 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:2::/48 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:3::/48 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:11::/48 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:12::/48 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:13::/48 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:14::/48 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:15::/48 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:16::/48 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:17::/48 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:20::/48 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:21::/48 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:22::/48 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:23::/48 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:100::/40 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:7e00::/48 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: none | 2405:cb00:10::/48 | No route object for it. A route object for 2405:cb00::/32 with origin AS55309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55309 in the RIR database for the space. |
| Route object: RIR | 2405:cb00::/48 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS55309 is announced.
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.