bgpreport

Network · data from 2026-11-12

AS9516 SAKURA

Registry name: SAKURALINK-AS-AP - SAKURA LINK LIMITED, HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9516, 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.
2401:f460:2100::/48 Valid RIR databaseAPNIC 634 100% 68
2401:f460:2200::/48 Valid RIR databaseAPNIC 634 100% 68
2401:f460:2300::/48 Valid RIR databaseAPNIC 623 98% 67

AS-SET

AS9516'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 38 are in fix.csv.

  • Route object: not announced38

Route objects not announced

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

23.148.40.0/24ARINValid
87.83.96.0/20RIPEValid
122.50.8.0/21NTTCOMNo ROA
122.50.8.0/22NTTCOMNo ROA
122.50.12.0/22NTTCOMNo ROA
202.47.89.0/24NTTCOMNo ROA
202.189.0.0/18RADBNo ROA
2405:84c0:ff20::/44APNICValid
2405:84c0:ff20::/45APNICValid
2405:84c0:ff20::/46APNICValid
2405:84c0:ff20::/47APNICValid
2405:84c0:ff20::/48APNICValid
2405:84c0:ff21::/48APNICValid
2405:84c0:ff22::/47APNICValid
2405:84c0:ff22::/48APNICValid
2405:84c0:ff23::/48APNICValid
2405:84c0:ff24::/46APNICValid
2405:84c0:ff24::/47APNICValid
2405:84c0:ff24::/48APNICValid
2405:84c0:ff25::/48APNICValid
2405:84c0:ff26::/47APNICValid
2405:84c0:ff26::/48APNICValid
2405:84c0:ff27::/48APNICValid
2405:84c0:ff28::/45APNICValid
2405:84c0:ff28::/46APNICValid
2405:84c0:ff28::/47APNICValid
2405:84c0:ff28::/48APNICValid
2405:84c0:ff29::/48APNICValid
2405:84c0:ff2a::/47APNICValid
2405:84c0:ff2a::/48APNICValid
2405:84c0:ff2b::/48APNICValid
2405:84c0:ff2c::/46APNICValid
2405:84c0:ff2c::/47APNICValid
2405:84c0:ff2c::/48APNICValid
2405:84c0:ff2d::/48APNICValid
2405:84c0:ff2e::/47APNICValid
2405:84c0:ff2e::/48APNICValid
2405:84c0:ff2f::/48APNICValid

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.