bgpreport

Network · data from 2026-11-12

AS45538 Online Data Services

Registry name: ODSJSC-AS-VN - ODS Joint Stock Company, VN · PeeringDB

82IPv4 routes 85.4% RPKI valid · 85.4% with a route object
4IPv6 routes 100.0% RPKI valid · 100.0% with a route object
12RPKI invalid 2 origin · 10 maxLength
0No ROA 12 with no route object for this origin
13Low visibility seen by under 10% of full-table peers
119Route objects not announced registered with origin AS45538, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS45538, 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.129.88.0/24 Invalid: origin Other origin only 24 4%low visibility 14
103.129.89.0/24 Invalid: origin Other origin only 24 4%low visibility 14
45.117.167.48/32 Invalid: maxLength Nonecovered by 45.117.167.0/24 2 0%low visibility 6
45.117.167.58/32 Invalid: maxLength Nonecovered by 45.117.167.0/24 2 0%low visibility 6
112.78.4.87/32 Invalid: maxLength Nonecovered by 112.78.4.0/24 2 0%low visibility 6
112.78.7.30/32 Invalid: maxLength Nonecovered by 112.78.7.0/24 2 0%low visibility 6
112.78.10.55/32 Invalid: maxLength Nonecovered by 112.78.10.0/24 2 0%low visibility 6
125.253.121.198/32 Invalid: maxLength Nonecovered by 125.253.121.0/24 2 0%low visibility 6
125.253.121.206/32 Invalid: maxLength Nonecovered by 125.253.121.0/24 2 0%low visibility 6
125.253.121.238/32 Invalid: maxLength Nonecovered by 125.253.121.0/24 2 0%low visibility 6
125.253.121.251/32 Invalid: maxLength Nonecovered by 125.253.121.0/24 2 0%low visibility 6
112.78.8.14/32 Invalid: maxLength Nonecovered by 112.78.8.0/24 0 0%low visibility 1
43.239.224.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
43.239.224.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
43.239.225.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
43.239.226.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
43.239.227.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.15.48.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.130.56.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.234.36.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.234.36.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.234.37.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.234.38.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.234.39.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.237.149.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.249.101.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.249.102.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
112.78.8.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
112.78.9.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
112.78.14.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
125.253.112.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
125.253.115.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
125.253.118.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
125.253.122.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.15.48.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.15.49.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.15.50.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.15.51.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.54.248.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.54.248.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.54.249.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.54.250.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.54.251.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.130.56.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.130.57.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.130.58.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.130.59.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.237.148.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.237.148.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.237.150.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.237.151.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.249.100.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.249.100.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.249.103.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
112.78.0.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
112.78.1.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
112.78.3.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
112.78.4.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
112.78.5.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
112.78.6.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
112.78.7.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
112.78.10.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
112.78.11.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
112.78.12.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
112.78.13.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
112.78.15.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
125.253.113.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
125.253.116.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
125.253.117.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
125.253.119.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
125.253.120.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
125.253.121.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
125.253.123.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
125.253.124.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
125.253.125.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
125.253.126.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
125.253.127.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
160.191.248.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
160.191.248.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
160.191.249.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
45.117.167.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
112.78.2.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
2405:7bc0::/48 Valid RIR databaseAPNIC, RADB 636 100% 69
2405:9d80::/32 Valid RIR databaseAPNIC, RADB 636 100% 69
2405:9d80:f000::/36 Valid RIR databaseAPNIC 635 100% 69
2401:75a0::/48 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

AS45538'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 143 are in fix.csv.

  • ROA: origin2
  • ROA: maxLength10
  • Route object: none12
  • Route object: not announced119
ChangePrefix or setDetailFull-table peers
ROA: origin103.129.88.0/24ROAs covering it name AS135949, not AS45538. If AS45538 should announce it, add a ROA for AS45538.24 of 673
Route object: none103.129.88.0/24Route objects for it name AS135949. Add a route object with origin AS45538 in the RIR database for the space.24 of 673
ROA: origin103.129.89.0/24ROAs covering it name AS135949, not AS45538. If AS45538 should announce it, add a ROA for AS45538.24 of 673
Route object: none103.129.89.0/24Route objects for it name AS135949. Add a route object with origin AS45538 in the RIR database for the space.24 of 673
ROA: maxLength45.117.167.48/32ROA 45.117.164.0/22 AS45538 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 45.117.167.48/32.2 of 673
Route object: none45.117.167.48/32No route object for it. A route object for 45.117.167.0/24 with origin AS45538 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45538 in the RIR database for the space.2 of 673
ROA: maxLength45.117.167.58/32ROA 45.117.164.0/22 AS45538 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 45.117.167.58/32.2 of 673
Route object: none45.117.167.58/32No route object for it. A route object for 45.117.167.0/24 with origin AS45538 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45538 in the RIR database for the space.2 of 673
ROA: maxLength112.78.4.87/32ROA 112.78.0.0/20 AS45538 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 112.78.4.87/32.2 of 673
Route object: none112.78.4.87/32No route object for it. A route object for 112.78.4.0/24 with origin AS45538 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45538 in the RIR database for the space.2 of 673
ROA: maxLength112.78.7.30/32ROA 112.78.0.0/20 AS45538 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 112.78.7.30/32.2 of 673
Route object: none112.78.7.30/32No route object for it. A route object for 112.78.7.0/24 with origin AS45538 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45538 in the RIR database for the space.2 of 673
ROA: maxLength112.78.10.55/32ROA 112.78.0.0/20 AS45538 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 112.78.10.55/32.2 of 673
Route object: none112.78.10.55/32No route object for it. A route object for 112.78.10.0/24 with origin AS45538 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45538 in the RIR database for the space.2 of 673
ROA: maxLength125.253.121.198/32ROA 125.253.112.0/20 AS45538 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 125.253.121.198/32.2 of 673
Route object: none125.253.121.198/32No route object for it. A route object for 125.253.121.0/24 with origin AS45538 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45538 in the RIR database for the space.2 of 673
ROA: maxLength125.253.121.206/32ROA 125.253.112.0/20 AS45538 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 125.253.121.206/32.2 of 673
Route object: none125.253.121.206/32No route object for it. A route object for 125.253.121.0/24 with origin AS45538 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45538 in the RIR database for the space.2 of 673
ROA: maxLength125.253.121.238/32ROA 125.253.112.0/20 AS45538 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 125.253.121.238/32.2 of 673
Route object: none125.253.121.238/32No route object for it. A route object for 125.253.121.0/24 with origin AS45538 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45538 in the RIR database for the space.2 of 673
ROA: maxLength125.253.121.251/32ROA 125.253.112.0/20 AS45538 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 125.253.121.251/32.2 of 673
Route object: none125.253.121.251/32No route object for it. A route object for 125.253.121.0/24 with origin AS45538 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45538 in the RIR database for the space.2 of 673
ROA: maxLength112.78.8.14/32ROA 112.78.0.0/20 AS45538 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 112.78.8.14/32.0 of 673
Route object: none112.78.8.14/32No route object for it. A route object for 112.78.8.0/24 with origin AS45538 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45538 in the RIR database for the space.0 of 673

Route objects not announced

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

43.239.224.0/23APNIC, NTTCOM, RADBValid
43.239.226.0/23APNIC, NTTCOM, RADBValid
45.117.164.0/22APNIC, NTTCOM, RADBValid
45.117.164.0/23APNIC, NTTCOM, RADBValid
45.117.164.0/24APNIC, NTTCOM, RADBValid
45.117.165.0/24APNIC, NTTCOM, RADBValid
45.117.166.0/23APNIC, NTTCOM, RADBValid
45.117.166.0/24APNIC, NTTCOM, RADBValid
45.125.236.0/24APNICInvalid: origin
45.125.237.0/24APNICInvalid: origin
103.15.48.0/23APNIC, NTTCOM, RADBValid
103.15.50.0/23APNIC, NTTCOM, RADBValid
103.47.194.0/24APNICInvalid: origin
103.47.195.0/24APNICInvalid: origin
103.54.248.0/23APNIC, NTTCOM, RADBValid
103.54.250.0/23APNIC, NTTCOM, RADBValid
103.56.164.0/22NTTCOM, RADBNo ROA
103.56.164.0/23NTTCOMNo ROA
103.56.164.0/24NTTCOM, RADBNo ROA
103.56.165.0/24NTTCOM, RADBNo ROA
103.56.166.0/23NTTCOM, RADBNo ROA
103.56.166.0/24NTTCOM, RADBNo ROA
103.56.167.0/24NTTCOM, RADBNo ROA
103.68.80.0/22APNICInvalid: origin
103.118.30.0/23APNIC, NTTCOM, RADBValid
103.118.30.0/24APNIC, NTTCOM, RADBValid
103.118.31.0/24APNIC, NTTCOM, RADBValid
103.130.56.0/23APNIC, NTTCOM, RADBValid
103.130.58.0/23APNIC, NTTCOM, RADBValid
103.138.88.0/23NTTCOM, RADBNo ROA
103.138.88.0/24NTTCOM, RADBNo ROA
103.138.89.0/24NTTCOM, RADBNo ROA
103.200.20.0/23APNICNo ROA
103.200.20.0/24NTTCOM, RADBNo ROA
103.200.21.0/24NTTCOM, RADBNo ROA
103.234.36.0/23APNIC, NTTCOM, RADBValid
103.234.38.0/23APNIC, NTTCOM, RADBValid
103.237.148.0/23APNIC, NTTCOM, RADBValid
103.237.150.0/23APNIC, NTTCOM, RADBValid
103.238.76.0/22APNIC, NTTCOM, RADBNo ROA
103.238.76.0/23NTTCOM, RADBNo ROA
103.238.76.0/24NTTCOM, RADBNo ROA
103.238.77.0/24NTTCOM, RADBNo ROA
103.238.78.0/23NTTCOM, RADBNo ROA
103.238.78.0/24NTTCOM, RADBNo ROA
103.238.79.0/24NTTCOM, RADBNo ROA
103.238.212.0/22NTTCOM, RADBNo ROA
103.238.212.0/23NTTCOM, RADBNo ROA
103.238.214.0/23NTTCOM, RADBNo ROA
103.238.214.0/24NTTCOM, RADBNo ROA
103.238.215.0/24NTTCOM, RADBNo ROA
103.249.100.0/23APNIC, NTTCOM, RADBValid
103.249.102.0/23APNIC, NTTCOM, RADBValid
103.255.236.0/22APNIC, NTTCOM, RADBNo ROA
103.255.236.0/23NTTCOM, RADBNo ROA
103.255.236.0/24NTTCOM, RADBNo ROA
103.255.237.0/24NTTCOM, RADBNo ROA
103.255.238.0/23NTTCOM, RADBNo ROA
103.255.239.0/24NTTCOM, RADBNo ROA
112.78.0.0/20APNIC, NTTCOM, RADBValid
112.78.0.0/21APNIC, NTTCOM, RADBValid
112.78.0.0/22APNIC, NTTCOM, RADBValid
112.78.0.0/23APNIC, NTTCOM, RADBValid
112.78.2.0/23APNIC, NTTCOM, RADBValid
112.78.4.0/22APNIC, NTTCOM, RADBValid
112.78.4.0/23APNIC, NTTCOM, RADBValid
112.78.6.0/23APNIC, NTTCOM, RADBValid
112.78.8.0/21APNIC, NTTCOM, RADBValid
112.78.8.0/22APNIC, NTTCOM, RADBValid
112.78.8.0/23APNIC, NTTCOM, RADBValid
112.78.10.0/23APNIC, NTTCOM, RADBValid
112.78.12.0/22APNIC, NTTCOM, RADBValid
112.78.12.0/23APNIC, NTTCOM, RADBValid
112.78.14.0/23APNIC, NTTCOM, RADBValid
125.253.112.0/20APNIC, NTTCOM, RADBValid
125.253.112.0/21APNIC, NTTCOM, RADBValid
125.253.112.0/22APNIC, NTTCOM, RADBValid
125.253.112.0/23APNIC, NTTCOM, RADBValid
125.253.114.0/23APNIC, NTTCOM, RADBValid
125.253.114.0/24APNIC, NTTCOM, RADBValid
125.253.116.0/22APNIC, NTTCOM, RADBValid
125.253.116.0/23APNIC, NTTCOM, RADBValid
125.253.118.0/23APNIC, NTTCOM, RADBValid
125.253.120.0/21APNIC, NTTCOM, RADBValid
125.253.120.0/22APNIC, NTTCOM, RADBValid
125.253.120.0/23APNIC, NTTCOM, RADBValid
125.253.122.0/23APNIC, NTTCOM, RADBValid
125.253.124.0/22APNIC, NTTCOM, RADBValid
125.253.124.0/23APNIC, NTTCOM, RADBValid
125.253.126.0/23APNIC, NTTCOM, RADBValid
2405:9d80::/33APNICValid
2405:9d80::/34APNICValid
2405:9d80::/35APNICValid
2405:9d80::/36APNICValid
2405:9d80:1000::/36APNICValid
2405:9d80:2000::/35APNICValid
2405:9d80:2000::/36APNICValid
2405:9d80:3000::/36APNICValid
2405:9d80:4000::/34APNICValid
2405:9d80:4000::/35APNICValid
2405:9d80:4000::/36APNICValid
2405:9d80:5000::/36APNICValid
2405:9d80:6000::/35APNICValid
2405:9d80:6000::/36APNICValid
2405:9d80:7000::/36APNICValid
2405:9d80:8000::/33APNICValid
2405:9d80:8000::/34APNICValid
2405:9d80:8000::/35APNICValid
2405:9d80:8000::/36APNICValid
2405:9d80:9000::/36APNICValid
2405:9d80:a000::/35APNICValid
2405:9d80:a000::/36APNICValid
2405:9d80:b000::/36APNICValid
2405:9d80:c000::/34APNICValid
2405:9d80:c000::/35APNICValid
2405:9d80:c000::/36APNICValid
2405:9d80:d000::/36APNICValid
2405:9d80:e000::/35APNICValid
2405:9d80:e000::/36APNICValid

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.