Announced routes
Every prefix a peer of the route collectors sees with origin AS63727, 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.
| 116.196.218.0/23 | Valid | Other origin only | 119 18% |
| 116.196.220.0/22 | Valid | Other origin only | 119 18% |
| 139.159.166.0/23 | Valid | Other origin only | 119 18% |
| 2409:27fa:f000::/48 | Valid | Other origin only | 1 0%low visibility |
| 49.4.32.0/20 | Valid | RIR databaseAPNIC | 146 22% |
| 49.4.111.0/24 | Valid | RIR databaseAPNIC | 8 1%low visibility |
AS-SET
PeeringDB's irr_as_set for AS63727: AS-HUAWEI. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS63727 isn't in the set, or no route object for AS63727 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS63727 in it | Not covered |
|---|---|---|---|---|---|
| AS-HUAWEI | RADB | 7 | 1 | No | 6 |
| APNIC (also) | 7 | 1 | No | 6 |
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 6 are in fix.csv.
- Route object: none4
- AS-SET: own ASN1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 116.196.218.0/23 | Route objects for it name AS23724. Add a route object with origin AS63727 in the RIR database for the space. |
| Route object: none | 116.196.220.0/22 | Route objects for it name AS23724. Add a route object with origin AS63727 in the RIR database for the space. |
| Route object: none | 139.159.166.0/23 | Route objects for it name AS23724. Add a route object with origin AS63727 in the RIR database for the space. |
| Route object: none | 2409:27fa:f000::/48 | Route objects for it name AS23724. Add a route object with origin AS63727 in the RIR database for the space. |
| AS-SET: own ASN | AS-HUAWEI | AS63727 isn't in AS-HUAWEI (RADB) once expanded. Add AS63727 to it. |
Route objects not announced
Route objects with origin AS63727 whose prefix no peer sees AS63727 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2407:c080:1400::/40 | RADB | 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.