Network · data from 2026-11-12
AS199707 XINGTONGHUI HONGKONG XING TONG HUI TECHNOLOGY CO., LIMITED
Registry name: XINGTONGHUI HONGKONG XING TONG HUI TECHNOLOGY CO., LIMITED, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS199707, 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.
| 46.183.22.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 51.194.191.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 79.176.26.0/24 | Invalid: origin | None | 1 0%low visibility |
| 194.61.237.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 201.50.30.0/24 | Invalid: origin | None | 1 0%low visibility |
| 62.105.218.0/24 | No ROA | Other origin only | 2 0%low visibility |
| 82.108.125.0/24 | No ROA | Other origin only | 2 0%low visibility |
| 82.110.226.0/24 | No ROA | None | 2 0%low visibility |
| 194.77.229.0/24 | No ROA | Other origin only | 2 0%low visibility |
| 209.101.157.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 78.105.181.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 87.82.193.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 87.83.220.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 192.120.196.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 192.132.107.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 194.77.228.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 195.21.134.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 83.245.3.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 194.77.2.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 200.141.184.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 217.216.178.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 192.132.106.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
AS-SET
AS199707 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 25 are in fix.csv.
- ROA: origin5
- ROA: none4
- Route object: none9
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 46.183.22.0/24 | ROAs covering it name AS834, not AS199707. If AS199707 should announce it, add a ROA for AS199707. |
| Route object: none | 46.183.22.0/24 | Route objects for it name AS834. Add a route object with origin AS199707 in the RIR database for the space. |
| ROA: origin | 51.194.191.0/24 | ROAs covering it name AS834, not AS199707. If AS199707 should announce it, add a ROA for AS199707. |
| Route object: none | 51.194.191.0/24 | Route objects for it name AS834. Add a route object with origin AS199707 in the RIR database for the space. |
| ROA: origin | 79.176.26.0/24 | ROAs covering it name AS834, not AS199707. If AS199707 should announce it, add a ROA for AS199707. |
| Route object: none | 79.176.26.0/24 | No route object for it. Add a route object with origin AS199707 in the RIR database for the space. |
| ROA: origin | 194.61.237.0/24 | ROAs covering it name AS834, not AS199707. If AS199707 should announce it, add a ROA for AS199707. |
| Route object: none | 194.61.237.0/24 | Route objects for it name AS834. Add a route object with origin AS199707 in the RIR database for the space. |
| ROA: origin | 201.50.30.0/24 | ROAs covering it name AS834, not AS199707. If AS199707 should announce it, add a ROA for AS199707. |
| Route object: none | 201.50.30.0/24 | No route object for it. Add a route object with origin AS199707 in the RIR database for the space. |
| ROA: none | 62.105.218.0/24 | No ROA covers it. Add a ROA for AS199707, maxLength 24. |
| Route object: none | 62.105.218.0/24 | Route objects for it name AS834. Add a route object with origin AS199707 in the RIR database for the space. |
| ROA: none | 82.108.125.0/24 | No ROA covers it. Add a ROA for AS199707, maxLength 24. |
| Route object: none | 82.108.125.0/24 | Route objects for it name AS834. Add a route object with origin AS199707 in the RIR database for the space. |
| ROA: none | 82.110.226.0/24 | No ROA covers it. Add a ROA for AS199707, maxLength 24. |
| Route object: none | 82.110.226.0/24 | No route object for it. Add a route object with origin AS199707 in the RIR database for the space. |
| ROA: none | 194.77.229.0/24 | No ROA covers it. Add a ROA for AS199707, maxLength 24. |
| Route object: none | 194.77.229.0/24 | Route objects for it name AS834. Add a route object with origin AS199707 in the RIR database for the space. |
| Route object: RIR | 209.101.157.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS199707 whose prefix no peer sees AS199707 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 72.35.242.0/24 | RIPE | Invalid: origin |
| 108.165.144.0/23 | RADB | No ROA |
| 140.235.37.0/24 | ARIN | No ROA |
| 140.235.38.0/23 | ARIN | No ROA |
| 154.198.58.0/24 | AFRINIC | Invalid: origin |
| 2a12:bec0:162::/48 | RADB | 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.