bgpreport

Network · data from 2026-11-12

AS55928 NTTCT-AS-KH-AP - NTT Communications (Phnom Penh ISP POP)

Registry name: NTTCT-AS-KH-AP - NTT Communications (Phnom Penh ISP POP), KH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55928, 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.7.24.0/23 Valid RIR databaseAPNIC 673 100% 68
2403:7500::/32 Valid RIR databaseAPNIC 635 100% 69
36.255.144.0/22 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2
36.255.144.0/23 Valid RIR databaseAPNIC 2 0%low visibility 2
36.255.146.0/23 Valid RIR databaseAPNIC 2 0%low visibility 2
103.7.24.0/22 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2
103.7.26.0/23 Valid RIR databaseAPNIC 2 0%low visibility 2
103.7.27.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

AS55928 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS55928 is announced.

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.