bgpreport

Network · data from 2026-11-12

AS218868 HIIL-AS Hongning Intelligent International Limited

Registry name: HIIL-AS Hongning Intelligent International Limited, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS218868, 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.
2a0c:7444::/30 No ROA None 3 0%low visibility 3
2a0d:2cc4::/30 No ROA None 3 0%low visibility 3
2a0f:7104::/31 No ROA None 3 0%low visibility 3
2a0c:7440::/30 No ROA None 1 0%low visibility 1
2a0d:2cc0::/30 No ROA None 1 0%low visibility 1
2a0f:7100::/30 No ROA None 1 0%low visibility 1
2a09:3f00:4400::/39 Valid RIR databaseRIPE 636 100% 67
2a0f:9400:e00::/40 Valid RIR databaseRIPE 636 100% 67
2a13:9500:1fd::/48 Valid RIR databaseRIPE 634 100% 67
2602:f2dc:bc::/48 Valid RIR databaseARIN 631 99% 67
2a0f:6280:7600::/39 Valid RIR databaseRIPE 631 99% 67

AS-SET

AS218868 isn't in PeeringDB, where networks name their 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 13 are in fix.csv.

  • ROA: none6
  • Route object: none6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a0c:7444::/30No ROA covers it. Add a ROA for AS218868, maxLength 30.3 of 636
Route object: none2a0c:7444::/30No route object for it. Add a route object with origin AS218868 in the RIR database for the space.3 of 636
ROA: none2a0d:2cc4::/30No ROA covers it. Add a ROA for AS218868, maxLength 30.3 of 636
Route object: none2a0d:2cc4::/30No route object for it. Add a route object with origin AS218868 in the RIR database for the space.3 of 636
ROA: none2a0f:7104::/31No ROA covers it. Add a ROA for AS218868, maxLength 31.3 of 636
Route object: none2a0f:7104::/31No route object for it. Add a route object with origin AS218868 in the RIR database for the space.3 of 636
ROA: none2a0c:7440::/30No ROA covers it. Add a ROA for AS218868, maxLength 30.1 of 636
Route object: none2a0c:7440::/30No route object for it. Add a route object with origin AS218868 in the RIR database for the space.1 of 636
ROA: none2a0d:2cc0::/30No ROA covers it. Add a ROA for AS218868, maxLength 30.1 of 636
Route object: none2a0d:2cc0::/30No route object for it. Add a route object with origin AS218868 in the RIR database for the space.1 of 636
ROA: none2a0f:7100::/30No ROA covers it. Add a ROA for AS218868, maxLength 30.1 of 636
Route object: none2a0f:7100::/30No route object for it. Add a route object with origin AS218868 in the RIR database for the space.1 of 636

Route objects not announced

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

2a0a:d687:ff04::/48RIPEValid

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.