Network · data from 2026-11-12
AS59374 BEST IDC
Registry name: BANGMODENTERPRISE-AS-AP - Bangmod Enterprise, TH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59374, 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.233.192.204/32 | Invalid: maxLength | Nonecovered by 103.233.192.0/24 | 0 0%low visibility |
| 103.233.193.168/32 | Invalid: maxLength | Nonecovered by 103.233.193.0/24 | 0 0%low visibility |
| 103.233.194.207/32 | Invalid: maxLength | Nonecovered by 103.233.194.0/24 | 0 0%low visibility |
| 43.255.241.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.70.5.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.70.6.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.233.193.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.254.164.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 43.255.240.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.233.192.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.233.194.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.233.195.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
AS-SET
AS59374'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 20 are in fix.csv.
- ROA: maxLength3
- Route object: none3
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 103.233.192.204/32 | ROA 103.233.192.0/24 AS59374 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.233.192.204/32. |
| Route object: none | 103.233.192.204/32 | No route object for it. A route object for 103.233.192.0/24 with origin AS59374 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59374 in the RIR database for the space. |
| ROA: maxLength | 103.233.193.168/32 | ROA 103.233.193.0/24 AS59374 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.233.193.168/32. |
| Route object: none | 103.233.193.168/32 | No route object for it. A route object for 103.233.193.0/24 with origin AS59374 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59374 in the RIR database for the space. |
| ROA: maxLength | 103.233.194.207/32 | ROA 103.233.194.0/24 AS59374 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.233.194.207/32. |
| Route object: none | 103.233.194.207/32 | No route object for it. A route object for 103.233.194.0/24 with origin AS59374 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59374 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS59374 whose prefix no peer sees AS59374 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 27.254.164.0/22 | APNIC, RADB | Valid |
| 27.254.165.0/24 | APNIC, RADB | Valid |
| 27.254.166.0/24 | APNIC, RADB | Valid |
| 27.254.167.0/24 | APNIC, RADB | Valid |
| 43.255.240.0/22 | APNIC, RADB | No ROA |
| 43.255.240.0/23 | APNIC | Valid |
| 43.255.242.0/24 | APNIC | Invalid: origin |
| 43.255.243.0/24 | APNIC | Invalid: origin |
| 103.70.4.0/22 | RADB | No ROA |
| 103.233.192.0/22 | APNIC, RADB | No ROA |
| 147.50.241.0/24 | APNIC | Valid |
| 160.238.12.0/22 | APNIC, RADB | No ROA |
| 2401:1a80::/32 | RADB | No ROA |
| 2406:480::/32 | 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.