Network · data from 2026-11-12
AS24149 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
Announced routes
Every prefix a peer of the route collectors sees with origin AS24149, 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.
| 150.242.158.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 150.242.159.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 203.119.81.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 203.119.82.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 2401:8d00:14::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2401:8d00:2::/48 | Valid | RIR databaseAPNIC | 632 99% |
| 2401:8d00:15::/48 | Valid | RIR databaseAPNIC | 605 95% |
| 2401:8d00:16::/48 | Valid | RIR databaseAPNIC | 605 95% |
AS-SET
AS24149 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 1 are in fix.csv.
- Route object: not announced1
Route objects not announced
Route objects with origin AS24149 whose prefix no peer sees AS24149 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2401:8d00:17::/48 | APNIC | 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.