bgpreport

Network · data from 2026-11-12

AS58424 Xinwei Telecom Cambodia

Registry name: XINWEITELECOM-KH - Xinwei (Cambodia) Telecom Co. Ltd, KH · PeeringDB

28IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
18Route objects not announced registered with origin AS58424, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS58424, 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.
43.255.112.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
43.255.112.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
43.255.113.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.5.124.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.5.124.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.5.125.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.5.126.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.5.127.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.206.200.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.206.200.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.206.201.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.206.202.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.206.203.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
116.214.24.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
116.214.24.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
116.214.25.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
116.214.30.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
116.214.30.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
116.214.31.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
146.88.202.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
146.88.202.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
146.88.203.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
146.88.206.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
146.88.206.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
146.88.207.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
167.179.0.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
167.179.0.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
167.179.1.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68

AS-SET

AS58424's PeeringDB record names no 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 18 are in fix.csv.

  • Route object: not announced18

Route objects not announced

Route objects with origin AS58424 whose prefix no peer sees AS58424 announce. Many are kept on purpose (backup routes, space announced only in some places).

43.255.112.0/22NTTCOM, RADBNo ROA
103.5.124.0/23APNIC, NTTCOM, RADBValid
103.5.126.0/23APNIC, NTTCOM, RADBValid
103.6.244.0/22NTTCOM, RADBNo ROA
103.6.244.0/24NTTCOM, RADBNo ROA
103.6.245.0/24NTTCOM, RADBNo ROA
103.6.246.0/24NTTCOM, RADBNo ROA
103.6.247.0/24NTTCOM, RADBNo ROA
103.206.200.0/23APNIC, NTTCOM, RADBValid
103.206.202.0/23APNIC, NTTCOM, RADBValid
116.214.24.0/21NTTCOM, RADBNo ROA
116.214.24.0/22NTTCOM, RADBNo ROA
116.214.28.0/22NTTCOM, RADBNo ROA
146.88.200.0/21NTTCOM, RADBNo ROA
146.88.200.0/22NTTCOM, RADBNo ROA
146.88.204.0/22NTTCOM, RADBNo ROA
202.58.16.0/22NTTCOM, RADBNo ROA
2407:8180::/32APNICValid

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.