bgpreport

Network · data from 2026-11-12

AS149107 TRUMVPS-VN - TRUMVPS COMPANY LIMITED

Registry name: TRUMVPS-VN - TRUMVPS COMPANY LIMITED, VN · not in PeeringDB

17IPv4 routes 52.9% RPKI valid · 52.9% with a route object
4IPv6 routes 100.0% RPKI valid · 100.0% with a route object
8RPKI invalid 5 origin · 3 maxLength
0No ROA 8 with no route object for this origin
8Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS149107, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS149107, 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.164.227.240/32 Invalid: origin None 3 0%low visibility 7
103.164.227.243/32 Invalid: origin None 3 0%low visibility 7
103.249.200.50/32 Invalid: origin None 3 0%low visibility 7
103.249.200.51/32 Invalid: origin None 3 0%low visibility 7
180.93.160.23/32 Invalid: origin None 3 0%low visibility 7
157.66.24.81/32 Invalid: maxLength Nonecovered by 157.66.24.0/23 5 1%low visibility 12
163.47.30.252/32 Invalid: maxLength Nonecovered by 163.47.30.0/23 5 1%low visibility 12
163.47.30.254/32 Invalid: maxLength Nonecovered by 163.47.30.0/23 5 1%low visibility 12
103.188.166.0/23 Valid RIR databaseAPNIC, RADB 673 100% 67
85.117.229.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
157.66.24.0/23 Valid RIR databaseAPNIC 669 99% 67
157.66.26.0/23 Valid RIR databaseAPNIC 669 99% 67
160.30.18.0/23 Valid RIR databaseAPNIC 669 99% 67
160.191.164.0/23 Valid RIR databaseAPNIC 669 99% 67
160.250.182.0/23 Valid RIR databaseAPNIC 669 99% 67
160.250.184.0/23 Valid RIR databaseAPNIC 669 99% 67
163.47.30.0/23 Valid RIR databaseAPNIC 669 99% 67
2001:df4:1bc0::/48 Valid RIR databaseAPNIC 636 100% 69
2001:df4:bac0::/48 Valid RIR databaseAPNIC 636 100% 69
2001:df4:bb40::/48 Valid RIR databaseAPNIC 636 100% 69
2401:8e20::/48 Valid RIR databaseAPNIC 636 100% 69

AS-SET

AS149107 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 20 are in fix.csv.

  • ROA: origin5
  • ROA: maxLength3
  • Route object: none8
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin103.164.227.240/32ROAs covering it name AS150850, not AS149107. If AS149107 should announce it, add a ROA for AS149107.3 of 673
Route object: none103.164.227.240/32No route object for it. Add a route object with origin AS149107 in the RIR database for the space.3 of 673
ROA: origin103.164.227.243/32ROAs covering it name AS150850, not AS149107. If AS149107 should announce it, add a ROA for AS149107.3 of 673
Route object: none103.164.227.243/32No route object for it. Add a route object with origin AS149107 in the RIR database for the space.3 of 673
ROA: origin103.249.200.50/32ROAs covering it name AS150873, not AS149107. If AS149107 should announce it, add a ROA for AS149107.3 of 673
Route object: none103.249.200.50/32No route object for it. Add a route object with origin AS149107 in the RIR database for the space.3 of 673
ROA: origin103.249.200.51/32ROAs covering it name AS150873, not AS149107. If AS149107 should announce it, add a ROA for AS149107.3 of 673
Route object: none103.249.200.51/32No route object for it. Add a route object with origin AS149107 in the RIR database for the space.3 of 673
ROA: origin180.93.160.23/32ROAs covering it name AS7602, not AS149107. If AS149107 should announce it, add a ROA for AS149107.3 of 673
Route object: none180.93.160.23/32No route object for it. Add a route object with origin AS149107 in the RIR database for the space.3 of 673
ROA: maxLength157.66.24.81/32ROA 157.66.24.0/23 AS149107 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 157.66.24.81/32.5 of 673
Route object: none157.66.24.81/32No route object for it. A route object for 157.66.24.0/23 with origin AS149107 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS149107 in the RIR database for the space.5 of 673
ROA: maxLength163.47.30.252/32ROA 163.47.30.0/23 AS149107 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 163.47.30.252/32.5 of 673
Route object: none163.47.30.252/32No route object for it. A route object for 163.47.30.0/23 with origin AS149107 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS149107 in the RIR database for the space.5 of 673
ROA: maxLength163.47.30.254/32ROA 163.47.30.0/23 AS149107 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 163.47.30.254/32.5 of 673
Route object: none163.47.30.254/32No route object for it. A route object for 163.47.30.0/23 with origin AS149107 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS149107 in the RIR database for the space.5 of 673

Route objects not announced

Route objects with origin AS149107 whose prefix no peer sees AS149107 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.188.166.0/24APNICValid
103.188.167.0/24APNICValid
2001:df4:bbc0::/48APNICValid
2001:df4:fc40::/48APNICValid

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.