Network · data from 2026-11-12
AS58777 CT2 - ChinaTelecom Cybersecurity Tech
Registry name: CT2 - ChinaTelecom Cybersecurity Tech, CN · not in PeeringDB
25IPv4 routes
96.0% RPKI valid · 96.0% with a route object
65IPv6 routes
98.5% RPKI valid · 98.5% with a route object
1RPKI invalid
1 origin · 0 maxLength
1No ROA
2 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
5Route objects not announced
registered with origin AS58777, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS58777, 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.
| 206.109.75.0/24 | Invalid: origin | RIR databaseAPNIC | 402 60% |
| 240e:ff:c027::/48 | No ROA | Other origin only | 22 3%low visibility |
| 203.33.67.0/24 | Valid | None | 671 100% |
| 42.122.63.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 59.50.75.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 59.52.138.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 61.133.162.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 61.151.144.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 61.151.145.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 106.91.120.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 110.90.214.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 113.240.205.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 115.233.202.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 117.25.105.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 125.93.28.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 125.93.29.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 182.36.0.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 220.171.147.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 221.226.225.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 221.235.40.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 221.237.65.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 222.91.142.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 222.91.143.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 59.47.246.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 218.62.152.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 218.62.153.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 240e:108:4000::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4001::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4020::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4025::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4040::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4047::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4059::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4060::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4080::/48 | Valid | RIR databaseAPNIC, RADB | 636 100% |
| 240e:108:40a0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:40e0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:40ec::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4120::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4140::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4160::/48 | Valid | RIR databaseAPNIC, RADB | 636 100% |
| 240e:108:41c0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:41e0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4220::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4240::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4260::/48 | Valid | RIR databaseAPNIC, RADB | 636 100% |
| 240e:108:4280::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:42a0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:42c0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:42e0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4300::/48 | Valid | RIR databaseAPNIC, RADB | 636 100% |
| 240e:108:4320::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4340::/48 | Valid | RIR databaseAPNIC, RADB | 636 100% |
| 240e:108:4360::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4380::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:438c::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:43a0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:43c0::/48 | Valid | RIR databaseAPNIC, RADB | 636 100% |
| 240e:108:4800::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4801::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4820::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4825::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4840::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4847::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4859::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4860::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4880::/48 | Valid | RIR databaseAPNIC, RADB | 636 100% |
| 240e:108:48a0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:48e0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:48ec::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4920::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4940::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4960::/48 | Valid | RIR databaseAPNIC, RADB | 636 100% |
| 240e:108:49c0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:49e0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4a20::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4a40::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4a60::/48 | Valid | RIR databaseAPNIC, RADB | 636 100% |
| 240e:108:4a80::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4aa0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4ac0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4ae0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4b00::/48 | Valid | RIR databaseAPNIC, RADB | 636 100% |
| 240e:108:4b20::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4b40::/48 | Valid | RIR databaseAPNIC, RADB | 636 100% |
| 240e:108:4b60::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4b80::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4b8c::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4ba0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240e:108:4bc0::/48 | Valid | RIR databaseAPNIC, RADB | 636 100% |
AS-SET
AS58777 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 9 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 206.109.75.0/24 | ROAs covering it name AS17476, not AS58777. If AS58777 should announce it, add a ROA for AS58777. |
| ROA: none | 240e:ff:c027::/48 | No ROA covers it. Add a ROA for AS58777, maxLength 48. |
| Route object: none | 240e:ff:c027::/48 | Route objects for it name AS4809. Add a route object with origin AS58777 in the RIR database for the space. |
| Route object: none | 203.33.67.0/24 | No route object for it. Add a route object with origin AS58777 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS58777 whose prefix no peer sees AS58777 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 59.47.247.0/24 | APNIC | Valid |
| 171.221.53.0/24 | APNIC | Valid |
| 182.36.12.0/24 | APNIC | Valid |
| 240e:108:4200::/48 | APNIC | Valid |
| 240e:108:4a00::/48 | 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.