bgpreport

Network · data from 2026-11-12

AS151202 Suzhou Honoka Technology Co Ltd

Registry name: HONOKA-AS-AP - Suzhou Honoka Technology Co Ltd, CN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS151202, 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.
2a10:ccc0:cc2::/48 Valid Nonecovered by 2a10:ccc0:cc0::/44 632 99% 68
2406:840:f0aa::/48 Valid RIR databaseAPNIC 634 100% 70
2a10:ccc0:ccc::/48 Valid RIR databaseRIPE 634 100% 70
2406:840:f0a1::/48 Valid RIR databaseAPNIC 633 100% 68
2a10:ccc0:cc1::/48 Valid RIR databaseRIPE 632 99% 68

AS-SET

AS151202'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 32 are in fix.csv.

  • Route object: none1
  • Route object: not announced31
ChangePrefix or setDetailFull-table peers
Route object: none2a10:ccc0:cc2::/48No route object for it. A route object for 2a10:ccc0:cc0::/44 with origin AS151202 covers it (filters allowing more-specifics accept it). Add a route object with origin AS151202 in the RIR database for the space.632 of 636

Route objects not announced

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

2406:840:f0a0::/44APNIC, RADBValid
2406:840:f0a0::/45APNICValid
2406:840:f0a0::/46APNICValid
2406:840:f0a0::/47APNICValid
2406:840:f0a0::/48APNICValid
2406:840:f0a2::/47APNICValid
2406:840:f0a2::/48APNICValid
2406:840:f0a3::/48APNICValid
2406:840:f0a4::/46APNICValid
2406:840:f0a4::/47APNICValid
2406:840:f0a4::/48APNICValid
2406:840:f0a5::/48APNICValid
2406:840:f0a6::/47APNICValid
2406:840:f0a6::/48APNICValid
2406:840:f0a7::/48APNICValid
2406:840:f0a8::/45APNICValid
2406:840:f0a8::/46APNICValid
2406:840:f0a8::/47APNICValid
2406:840:f0a8::/48APNICValid
2406:840:f0a9::/48APNICValid
2406:840:f0aa::/47APNICValid
2406:840:f0ab::/48APNICValid
2406:840:f0ac::/46APNICValid
2406:840:f0ac::/47APNICValid
2406:840:f0ac::/48APNICValid
2406:840:f0ad::/48APNICValid
2406:840:f0ae::/47APNICValid
2406:840:f0ae::/48APNICValid
2406:840:f0af::/48APNICValid
2406:840:feb5::/48APNICValid
2a10:ccc0:cc0::/44RADBValid

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.