# chnroutes2: Hourly Aggregated CN Routes from Multiple BGP Feeds > chnroutes2 is a data project that aggregates China-related BGP routes from several providers into a single, frequently updated route set. It is aimed at network operators and developers who need current CN route information without running their own collectors. **misakaio/chnroutes2** — Better aggregated chnroutes - Repository: https://github.com/misakaio/chnroutes2 - Stars: 876 · Forks: 76 - Language: Unknown - License: CC-BY-SA-4.0 - Published: 2026-08-22 · Updated: 2026-08-22 · Language: en - Canonical page: https://hysenlabs.com/projects/misakaio-chnroutes2 ## What chnroutes2 Actually Provides chnroutes2 is a data repository, not a software tool. It publishes a set of China-related IP prefixes derived from BGP feeds. The README states that the project uses BGP feeds from various sources to provide more accurate and up-to-date CN routes. The key word is aggregated: it combines routes from multiple providers into one list. This is useful for anyone who needs a current view of Chinese IP space, such as firewall rule generators, routing policy scripts, or network monitoring dashboards. The project does not include a tool to consume the data; it is just the data itself. ## The Mechanism: BGP Feeds and Hourly Updates The README says the project updates every hour from a route collector. This is the core mechanism: a collector receives BGP announcements from the listed feed providers, extracts the prefixes, and publishes them in the repository. The aggregation step is what distinguishes chnroutes2 from a raw BGP dump. By combining feeds, it aims to reduce noise and inconsistencies that come from relying on a single source. The hourly cadence is a strong point, as many similar datasets update daily or weekly. However, the README does not specify the format of the published data, the exact aggregation algorithm, or how conflicts between feeds are resolved. Those details would matter for anyone integrating the data into automation. ## Getting the Data and Running It Since chnroutes2 is a repository, the primary way to get the data is to clone it or download the files directly. The README does not list installation steps, because there is nothing to install. A typical usage would be: git clone https://github.com/misakaio/chnroutes2.git, then inspect the files in the repository. The README also does not mention any configuration keys or command-line options. This is a data-only project. If you want to use the routes in a router or firewall, you would need to write your own script to parse the files and generate rules. The lack of a built-in tool or documentation on the file format is a limitation, but for a data repository it is acceptable. ## Licensing and Attribution The data is licensed under CC-BY-SA, as stated in the README. The license requires attribution and share-alike if you redistribute modified versions. This has practical implications. If you incorporate the route list into a product, you may need to attribute the source and license your derived data under the same terms. This is not legal advice, but it is a real constraint. The README also lists the feed providers: AS917 (Misaka Network), AS906 (DMIT), AS131477 (Shanghai Huajuan), and AS138195 (MOACK). These are the sources that make the dataset possible. If any provider drops out, the coverage may change. ## Limitations and Failure Modes The most obvious limitation is that the README gives no details on the data format, the aggregation logic, or how to verify the accuracy of the route set. There is no mention of how often the feed providers update their own BGP announcements, so the hourly refresh may not reflect real-time changes if the upstream feeds lag. Another failure mode is the dependency on a single route collector. If the collector goes down, the updates stop, and the repository becomes stale. The README does not state what happens in that case. Additionally, the project only covers routes from the listed providers, which are not the only sources of CN routes. It may miss prefixes that are not announced by these ASes. ## Alternatives and How They Differ A common alternative is to use public BGP route collectors like RouteViews or RIPE RIS. These provide raw BGP data from many ASes, and you can filter for CN prefixes yourself. The difference is that RouteViews and RIPE RIS are passive collectors that do not aggregate or curate the data. chnroutes2 does the aggregation for you, saving time, but it relies on a smaller set of feeds. Another alternative is to use the APNIC delegated statistics file, which lists IP allocations by country. That file is updated daily and is authoritative for allocations, but it does not reflect actual routing announcements. chnroutes2 is more dynamic but less comprehensive than the delegated file. ## Maintenance and Upgrade Cost The README does not state the maintenance history or the frequency of commits, so the upgrade cost is hard to assess. The project is not archived, which suggests it is still active, but the last push date is unknown. For a data repository, the maintenance cost is low for users: you just re-download the data. However, you need to monitor the repository for changes in the data format or the feed provider list, which could break your scripts. The license also means that if you modify the data, you must keep it under CC-BY-SA, which could be a burden if you want to combine it with other data under different licenses. ## Conclusion Adopt chnroutes2 if you need a current, aggregated set of CN routes without operating your own BGP collector. It is not for you if you require formal SLA-backed data, per-prefix origin details, or if the CC-BY-SA license conflicts with your use case. Verify the freshness of the hourly updates and the exact list of feed providers before relying on it in production. The project's value depends entirely on the continued participation of the listed ASes, so check the repository's history for any gaps in updates. ## FAQ ### What does chnroutes2 provide? CN routes aggregated from BGP feeds at four providers, refreshed every hour from the maintainer's route collector. The repository publishes the data as chnroutes.txt and as chnroutes.mmdb, alongside a LICENSE, a short README and an ignore-asns.txt file that the page does not describe. ### Which BGP sources feed chnroutes2? Four, each listed with its AS number: AS917 from Misaka Network, AS906 from DMIT, AS131477 from Shanghai Huajuan Information Technology, and AS138195 from MOACK. The repository owner operates AS917, so one of the four inputs is the publisher's own network. ### How often does chnroutes2 update and does it publish releases? Every hour, according to the page, and no, it publishes no GitHub releases. There is no tag to depend on, so a consumer who needs reproducibility has to pin the commit the data was read at. ### What license applies to chnroutes2 data? The repository record reports CC-BY-SA-4.0, while the page says the data is licensed under CC-BY-SA and links the version 2.0 deed. A LICENSE file exists at the root, so the authoritative terms are in the tree rather than in either summary. ### Is the route collector that feeds chnroutes2 published? No. The repository contains only the generated data and no source code, build files or scripts, so the collector that produces the hourly output is not available to inspect or run. ## Sources - [Official README](https://github.com/misakaio/chnroutes2#readme) - [Project repository](https://github.com/misakaio/chnroutes2) - [README](https://github.com/misakaio/chnroutes2/blob/master/README.md) - [Releases](https://github.com/misakaio/chnroutes2/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/misakaio-chnroutes2