bgpreport

Network · data from 2026-11-12

AS218910 ASHORE-LIMITED ASHORE LIMITED

Registry name: ASHORE-LIMITED ASHORE LIMITED, HK · not in PeeringDB

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

Announced routes

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

64.205.63.0/24 Invalid: origin Other origin only 2 0%low visibility 1
68.164.63.0/24 Invalid: origin None 2 0%low visibility 1
68.164.133.0/24 Invalid: origin Other origin only 2 0%low visibility 1
69.33.163.0/24 Invalid: origin None 2 0%low visibility 1
94.118.7.0/24 Invalid: origin Other origin only 2 0%low visibility 1
94.118.21.0/24 Invalid: origin Other origin only 2 0%low visibility 1
61.18.217.0/24 Invalid: origin Other origin only 1 0%low visibility 1
61.18.219.0/24 Invalid: origin Other origin only 1 0%low visibility 1
61.18.223.0/24 Invalid: origin Other origin only 1 0%low visibility 1
82.206.3.0/24 Invalid: origin None 1 0%low visibility 1
134.49.206.0/24 Invalid: origin Other origin only 1 0%low visibility 1
61.18.221.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66

AS-SET

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

  • ROA: origin11
  • Route object: none11
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin64.205.63.0/24ROAs covering it name AS834, AS11059, not AS218910. If AS218910 should announce it, add a ROA for AS218910.2 of 673
Route object: none64.205.63.0/24Route objects for it name AS834. Add a route object with origin AS218910 in the RIR database for the space.2 of 673
ROA: origin68.164.63.0/24ROAs covering it name AS834, not AS218910. If AS218910 should announce it, add a ROA for AS218910.2 of 673
Route object: none68.164.63.0/24No route object for it. Add a route object with origin AS218910 in the RIR database for the space.2 of 673
ROA: origin68.164.133.0/24ROAs covering it name AS834, not AS218910. If AS218910 should announce it, add a ROA for AS218910.2 of 673
Route object: none68.164.133.0/24Route objects for it name AS834. Add a route object with origin AS218910 in the RIR database for the space.2 of 673
ROA: origin69.33.163.0/24ROAs covering it name AS834, not AS218910. If AS218910 should announce it, add a ROA for AS218910.2 of 673
Route object: none69.33.163.0/24No route object for it. Add a route object with origin AS218910 in the RIR database for the space.2 of 673
ROA: origin94.118.7.0/24ROAs covering it name AS834, not AS218910. If AS218910 should announce it, add a ROA for AS218910.2 of 673
Route object: none94.118.7.0/24Route objects for it name AS834. Add a route object with origin AS218910 in the RIR database for the space.2 of 673
ROA: origin94.118.21.0/24ROAs covering it name AS834, not AS218910. If AS218910 should announce it, add a ROA for AS218910.2 of 673
Route object: none94.118.21.0/24Route objects for it name AS834. Add a route object with origin AS218910 in the RIR database for the space.2 of 673
ROA: origin61.18.217.0/24ROAs covering it name AS834, not AS218910. If AS218910 should announce it, add a ROA for AS218910.1 of 673
Route object: none61.18.217.0/24Route objects for it name AS834. Add a route object with origin AS218910 in the RIR database for the space.1 of 673
ROA: origin61.18.219.0/24ROAs covering it name AS834, not AS218910. If AS218910 should announce it, add a ROA for AS218910.1 of 673
Route object: none61.18.219.0/24Route objects for it name AS834. Add a route object with origin AS218910 in the RIR database for the space.1 of 673
ROA: origin61.18.223.0/24ROAs covering it name AS834, not AS218910. If AS218910 should announce it, add a ROA for AS218910.1 of 673
Route object: none61.18.223.0/24Route objects for it name AS834. Add a route object with origin AS218910 in the RIR database for the space.1 of 673
ROA: origin82.206.3.0/24ROAs covering it name AS834, not AS218910. If AS218910 should announce it, add a ROA for AS218910.1 of 673
Route object: none82.206.3.0/24No route object for it. Add a route object with origin AS218910 in the RIR database for the space.1 of 673
ROA: origin134.49.206.0/24ROAs covering it name AS152606, not AS218910. If AS218910 should announce it, add a ROA for AS218910.1 of 673
Route object: none134.49.206.0/24Route objects for it name AS152606. Add a route object with origin AS218910 in the RIR database for the space.1 of 673

Route objects not announced

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

64.205.65.0/24ARIN, RADBValid
217.216.132.0/24RADB, RIPEValid

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.