bgpreport

Network · data from 2026-11-12

AS7712 Sabay Digital (Cambodia)

Registry name: CNE-AS-AP - Cambodian Network Exchange Co., Ltd., KH · PeeringDB

5IPv4 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
4Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS7712, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS7712, 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.

118.67.200.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
2405:aa00::/32 Valid RIR databaseAPNIC, RADB 636 100% 67
118.67.200.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 35 5%low visibility 28
118.67.200.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 35 5%low visibility 28
118.67.202.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 35 5%low visibility 28
118.67.203.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 35 5%low visibility 28

AS-SET

PeeringDB's irr_as_set for AS7712: APNIC::AS7712:AS-TRANSIT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS7712 isn't in the set, or no route object for AS7712 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS7712 in itNot covered
APNIC::AS7712:AS-TRANSIT APNIC 3114 Yes 0

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 3 are in fix.csv.

  • Route object: not announced3

Route objects not announced

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

118.67.200.0/21NTTCOM, RADBNo ROA
118.67.201.0/24APNIC, NTTCOM, RADBValid
118.67.202.0/23APNIC, NTTCOM, RADBValid

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.