Network · data from 2026-11-12
AS55991 AS55991-36 - CNNIC ASN block
Registry name: AS55991-36 - CNNIC ASN block, CN · not in PeeringDB
21IPv4 routes
100.0% RPKI valid · 61.9% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
8 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
3Route objects not announced
registered with origin AS55991, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS55991, 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.43.134.0/24 | Valid | None | 672 100% |
| 103.43.135.0/24 | Valid | None | 672 100% |
| 103.192.208.0/24 | Valid | Nonecovered by 103.192.208.0/22 | 672 100% |
| 103.192.209.0/24 | Valid | Nonecovered by 103.192.208.0/22 | 672 100% |
| 103.192.210.0/24 | Valid | Nonecovered by 103.192.208.0/22 | 672 100% |
| 103.192.211.0/24 | Valid | Nonecovered by 103.192.208.0/22 | 672 100% |
| 103.235.100.0/24 | Valid | Nonecovered by 103.235.100.0/22 | 28 4%low visibility |
| 103.235.101.0/24 | Valid | Nonecovered by 103.235.100.0/22 | 28 4%low visibility |
| 43.228.204.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 43.228.240.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 103.41.116.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 103.56.100.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 103.56.104.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 103.192.208.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 103.235.102.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.235.103.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.124.76.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.124.77.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.124.78.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.124.79.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 103.43.132.0/24 | Valid | Other IRR onlyRADB | 28 4%low visibility |
AS-SET
AS55991 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 24 are in fix.csv.
- Route object: none8
- Route object: RIR13
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.43.134.0/24 | No route object for it. Add a route object with origin AS55991 in the RIR database for the space. |
| Route object: none | 103.43.135.0/24 | No route object for it. Add a route object with origin AS55991 in the RIR database for the space. |
| Route object: none | 103.192.208.0/24 | No route object for it. A route object for 103.192.208.0/22 with origin AS55991 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55991 in the RIR database for the space. |
| Route object: none | 103.192.209.0/24 | No route object for it. A route object for 103.192.208.0/22 with origin AS55991 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55991 in the RIR database for the space. |
| Route object: none | 103.192.210.0/24 | No route object for it. A route object for 103.192.208.0/22 with origin AS55991 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55991 in the RIR database for the space. |
| Route object: none | 103.192.211.0/24 | No route object for it. A route object for 103.192.208.0/22 with origin AS55991 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55991 in the RIR database for the space. |
| Route object: none | 103.235.100.0/24 | No route object for it. A route object for 103.235.100.0/22 with origin AS55991 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55991 in the RIR database for the space. |
| Route object: none | 103.235.101.0/24 | No route object for it. A route object for 103.235.100.0/22 with origin AS55991 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55991 in the RIR database for the space. |
| Route object: RIR | 43.228.204.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.228.240.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.41.116.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.56.100.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.56.104.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.192.208.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.235.102.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.235.103.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.124.76.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.124.77.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.124.78.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.124.79.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.43.132.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS55991 whose prefix no peer sees AS55991 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.228.0.0/21 | RADB | No ROA |
| 103.43.133.0/24 | RADB | Valid |
| 103.235.100.0/22 | 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.