Network · data from 2026-11-12
AS55996 CYPRESSTEL - CYPRESS TELECOM (CHINA) LIMITED
Registry name: CYPRESSTEL - CYPRESS TELECOM (CHINA) LIMITED, CN · not in PeeringDB
28IPv4 routes
96.4% RPKI valid · 60.7% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
1No ROA
11 with no route object for this origin
8Low visibility
seen by under 10% of full-table peers
32Route objects not announced
registered with origin AS55996, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS55996, 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.40.173.0/24 | No ROA | Other origin only | 673 100% |
| 103.197.2.0/23 | Valid | Nonecovered by 103.197.0.0/22 | 671 100% |
| 123.108.89.0/24 | Valid | Nonecovered by 123.108.88.0/23 | 671 100% |
| 103.40.175.0/24 | Valid | Nonecovered by 103.40.174.0/23 | 668 99% |
| 123.108.88.0/24 | Valid | Nonecovered by 123.108.88.0/23 | 668 99% |
| 103.40.174.0/24 | Valid | Nonecovered by 103.40.174.0/23 | 649 96% |
| 103.197.0.0/23 | Valid | Nonecovered by 103.197.0.0/22 | 649 96% |
| 103.197.0.0/24 | Valid | Nonecovered by 103.197.0.0/22 | 5 1%low visibility |
| 103.197.2.0/24 | Valid | Other origin onlycovered by 103.197.0.0/22 | 5 1%low visibility |
| 103.197.3.0/24 | Valid | Other origin onlycovered by 103.197.0.0/22 | 5 1%low visibility |
| 103.197.1.0/24 | Valid | Nonecovered by 103.197.0.0/22 | 4 1%low visibility |
| 103.20.32.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 4 1%low visibility |
| 103.20.35.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.40.174.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.61.190.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.45.226.0/23 | Valid | RIR databaseAPNIC | 671 100% |
| 103.20.32.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 43.229.48.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 103.45.171.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 103.20.34.0/24 | Valid | RIR databaseAPNIC | 664 99% |
| 158.140.252.0/23 | Valid | RIR databaseAPNIC | 656 97% |
| 43.229.51.0/24 | Valid | RIR databaseAPNIC | 653 97% |
| 103.61.188.0/23 | Valid | RIR databaseAPNIC | 601 89% |
| 43.229.50.0/24 | Valid | RIR databaseAPNIC | 431 64% |
| 103.20.34.0/23 | Valid | RIR databaseAPNIC | 333 49% |
| 43.229.49.0/24 | Valid | RIR databaseAPNIC | 23 3%low visibility |
| 103.20.32.0/24 | Valid | RIR databaseAPNIC | 4 1%low visibility |
| 103.20.33.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
AS55996 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 45 are in fix.csv.
- ROA: none1
- Route object: none11
- Route object: RIR1
- Route object: not announced32
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.40.173.0/24 | No ROA covers it. Add a ROA for AS55996, maxLength 24. |
| Route object: none | 103.40.173.0/24 | Route objects for it name AS131274. Add a route object with origin AS55996 in the RIR database for the space. |
| Route object: none | 103.197.2.0/23 | No route object for it. A route object for 103.197.0.0/22 with origin AS55996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55996 in the RIR database for the space. |
| Route object: none | 123.108.89.0/24 | No route object for it. A route object for 123.108.88.0/23 with origin AS55996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55996 in the RIR database for the space. |
| Route object: none | 103.40.175.0/24 | No route object for it. A route object for 103.40.174.0/23 with origin AS55996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55996 in the RIR database for the space. |
| Route object: none | 123.108.88.0/24 | No route object for it. A route object for 123.108.88.0/23 with origin AS55996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55996 in the RIR database for the space. |
| Route object: none | 103.40.174.0/24 | No route object for it. A route object for 103.40.174.0/23 with origin AS55996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55996 in the RIR database for the space. |
| Route object: none | 103.197.0.0/23 | No route object for it. A route object for 103.197.0.0/22 with origin AS55996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55996 in the RIR database for the space. |
| Route object: none | 103.197.0.0/24 | No route object for it. A route object for 103.197.0.0/22 with origin AS55996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55996 in the RIR database for the space. |
| Route object: none | 103.197.2.0/24 | Route objects for it name AS58542. A route object for 103.197.0.0/22 with origin AS55996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55996 in the RIR database for the space. |
| Route object: none | 103.197.3.0/24 | Route objects for it name AS58542. A route object for 103.197.0.0/22 with origin AS55996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55996 in the RIR database for the space. |
| Route object: none | 103.197.1.0/24 | No route object for it. A route object for 103.197.0.0/22 with origin AS55996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55996 in the RIR database for the space. |
| Route object: RIR | 103.20.32.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS55996 whose prefix no peer sees AS55996 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.229.48.0/23 | APNIC | No ROA |
| 43.229.50.0/23 | APNIC | No ROA |
| 103.45.168.0/22 | APNIC | No ROA |
| 103.45.168.0/23 | APNIC | No ROA |
| 103.45.168.0/24 | APNIC | Invalid: origin |
| 103.45.169.0/24 | APNIC | Valid |
| 103.45.170.0/23 | APNIC | No ROA |
| 103.45.170.0/24 | APNIC | Valid |
| 103.45.224.0/22 | APNIC | Valid |
| 103.45.224.0/23 | APNIC | Valid |
| 103.45.224.0/24 | APNIC | Valid |
| 103.45.225.0/24 | APNIC | Valid |
| 103.45.226.0/24 | APNIC | Valid |
| 103.45.227.0/24 | APNIC | Valid |
| 103.61.188.0/22 | APNIC | No ROA |
| 103.61.188.0/24 | APNIC | Valid |
| 103.61.189.0/24 | APNIC | Valid |
| 103.61.190.0/24 | APNIC | Valid |
| 103.61.191.0/24 | APNIC | Valid |
| 103.197.0.0/22 | APNIC | No ROA |
| 103.248.100.0/22 | APNIC | Valid |
| 103.248.100.0/23 | APNIC | Valid |
| 103.248.100.0/24 | APNIC | Valid |
| 103.248.101.0/24 | APNIC | Valid |
| 123.108.88.0/23 | APNIC | No ROA |
| 158.140.252.0/22 | APNIC | No ROA |
| 158.140.252.0/24 | APNIC | Valid |
| 158.140.253.0/24 | APNIC | Valid |
| 158.140.254.0/23 | APNIC | No ROA |
| 158.140.254.0/24 | APNIC | Valid |
| 158.140.255.0/24 | APNIC | Invalid: origin |
| 2405:b300::/32 | APNIC | Valid |
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.