bgpreport

Network · data from 2026-11-12

AS38345 ZDNS - Internet Domain Name System Beijing Engineering Resrarch Center Ltd.

Registry name: ZDNS - Internet Domain Name System Beijing Engineering Resrarch Center Ltd., CN · not in PeeringDB

24IPv4 routes 91.7% RPKI valid · 100.0% with a route object
14IPv6 routes 78.6% RPKI valid · 85.7% with a route object
2RPKI invalid 2 origin · 0 maxLength
3No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
47Route objects not announced registered with origin AS38345, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38345, 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.
2620:57:4004::/48 Invalid: origin None 7 1%low visibility 5
2620:57:4005::/48 Invalid: origin Other origin only 7 1%low visibility 5
1.8.1.0/24 No ROA RIR databaseAPNIC 673 100% 67
1.8.8.0/24 No ROA RIR databaseAPNIC 673 100% 67
2401:8d00:5::/48 No ROA RIR databaseAPNIC 605 95% 67
202.173.8.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.173.9.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.173.10.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.173.11.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.173.14.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.173.15.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.99.20.0/24 Valid RIR databaseAPNIC 673 100% 67
203.99.29.0/24 Valid RIR databaseAPNIC 673 100% 67
203.99.30.0/24 Valid RIR databaseAPNIC 673 100% 67
203.99.31.0/24 Valid RIR databaseAPNIC 673 100% 67
203.119.80.0/24 Valid RIR databaseAPNIC 673 100% 67
203.119.83.0/24 Valid RIR databaseAPNIC 673 100% 67
150.242.156.0/24 Valid RIR databaseAPNIC 671 100% 67
150.242.157.0/24 Valid RIR databaseAPNIC 671 100% 67
203.99.21.0/24 Valid RIR databaseAPNIC 671 100% 67
203.99.22.0/24 Valid RIR databaseAPNIC 671 100% 67
203.99.23.0/24 Valid RIR databaseAPNIC 671 100% 67
203.99.25.0/24 Valid RIR databaseAPNIC 671 100% 67
203.99.26.0/24 Valid RIR databaseAPNIC 671 100% 67
203.99.27.0/24 Valid RIR databaseAPNIC 671 100% 67
203.99.28.0/24 Valid RIR databaseAPNIC 671 100% 67
203.99.24.0/24 Valid RIR databaseAPNIC 668 99% 67
2401:8d00::/48 Valid RIR databaseAPNIC 636 100% 67
2401:8d00:8::/48 Valid RIR databaseAPNIC 636 100% 67
2401:8d00:3::/48 Valid RIR databaseAPNIC 635 100% 68
2401:8d00:4::/48 Valid RIR databaseAPNIC 635 100% 67
2401:8d00:7::/48 Valid RIR databaseAPNIC 635 100% 68
2401:8d00:9::/48 Valid RIR databaseAPNIC 635 100% 68
2401:8d00:b::/48 Valid RIR databaseAPNIC 635 100% 68
2401:8d00:c::/48 Valid RIR databaseAPNIC 635 100% 68
2401:8d00:f::/48 Valid RIR databaseAPNIC 635 100% 68
2401:8d00:1::/48 Valid RIR databaseAPNIC 632 99% 68
2401:8d00:12::/48 Valid RIR databaseAPNIC 604 95% 68

AS-SET

AS38345 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 54 are in fix.csv.

  • ROA: origin2
  • ROA: none3
  • Route object: none2
  • Route object: not announced47
ChangePrefix or setDetailFull-table peers
ROA: origin2620:57:4004::/48ROAs covering it name AS62831, not AS38345. If AS38345 should announce it, add a ROA for AS38345.7 of 636
Route object: none2620:57:4004::/48No route object for it. Add a route object with origin AS38345 in the RIR database for the space.7 of 636
ROA: origin2620:57:4005::/48ROAs covering it name AS62831, AS63363, not AS38345. If AS38345 should announce it, add a ROA for AS38345.7 of 636
Route object: none2620:57:4005::/48Route objects for it name AS63363. Add a route object with origin AS38345 in the RIR database for the space.7 of 636
ROA: none1.8.1.0/24No ROA covers it. Add a ROA for AS38345, maxLength 24.673 of 673
ROA: none1.8.8.0/24No ROA covers it. Add a ROA for AS38345, maxLength 24.673 of 673
ROA: none2401:8d00:5::/48No ROA covers it. Add a ROA for AS38345, maxLength 48.605 of 636

Route objects not announced

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

1.8.0.0/16APNICNo ROA
1.8.18.0/24APNIC, NTTCOM, RADBNo ROA
1.8.100.0/24APNICNo ROA
1.8.101.0/24APNIC, NTTCOM, RADBNo ROA
1.8.102.0/24APNICNo ROA
1.8.103.0/24APNICNo ROA
1.8.104.0/24APNICNo ROA
1.8.105.0/24APNICNo ROA
1.8.106.0/24APNICNo ROA
1.8.107.0/24APNICNo ROA
1.8.108.0/24APNICNo ROA
1.8.109.0/24APNICNo ROA
1.8.110.0/24APNICNo ROA
1.8.111.0/24APNICNo ROA
1.8.150.0/23RADBNo ROA
1.8.150.0/24APNIC, RADBNo ROA
1.8.151.0/24APNIC, RADBNo ROA
1.8.152.0/23RADBNo ROA
1.8.152.0/24APNIC, RADBNo ROA
1.8.153.0/24APNIC, RADBNo ROA
1.8.154.0/24APNICNo ROA
1.8.155.0/24APNICNo ROA
1.8.238.0/24APNIC, NTTCOM, RADBNo ROA
1.8.239.0/24APNIC, NTTCOM, RADBNo ROA
1.8.240.0/24APNICNo ROA
1.8.241.0/24APNICNo ROA
1.8.242.0/24APNICNo ROA
1.8.243.0/24APNICNo ROA
1.8.244.0/24APNICNo ROA
202.173.8.0/21APNIC, NTTCOM, RADBNo ROA
202.173.8.0/22RADBNo ROA
202.173.12.0/24APNIC, NTTCOM, RADBNo ROA
202.173.13.0/24APNIC, NTTCOM, RADBNo ROA
203.119.80.0/22RADBNo ROA
203.119.81.0/24APNICInvalid: origin
219.83.192.0/20NTTCOM, RADBNo ROA
2401:8d00::/64APNICInvalid: maxLength
2401:8d00:6::/48APNICNo ROA
2401:8d00:a::/48APNICNo ROA
2401:8d00:d::/48APNICNo ROA
2401:8d00:e::/48APNICNo ROA
2401:8d00:10::/48APNICNo ROA
2401:8d00:11::/48APNICNo ROA
2401:8d00:13::/48APNICNo ROA
2401:8d00:15::/48APNICInvalid: origin
2401:8d00:16::/48APNICInvalid: origin
2401:8d00:17::/48APNICNo 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.