bgpreport

Network · data from 2026-11-12

AS218911 ORION-LIMITED ORION LIMITED

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

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

Announced routes

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

68.164.142.0/24 Invalid: origin Other origin only 2 0%low visibility 1
68.164.219.0/24 Invalid: origin Other origin only 2 0%low visibility 1
87.84.23.0/24 Valid Other IRR onlyRADB 673 100% 66
165.49.102.0/24 Valid Other IRR onlyRADB 672 100% 67
212.134.158.0/24 Valid Other IRR onlyRADB 671 100% 67
62.144.63.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
64.205.65.0/24 Valid RIR databaseARIN, RADB 673 100% 66
61.15.206.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
61.15.215.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
61.18.178.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
61.18.180.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
61.18.182.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
61.18.188.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
61.18.196.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
91.124.107.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
144.56.72.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
200.149.183.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
61.18.168.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
64.204.30.0/24 Valid RIR databaseARIN, RADB 671 100% 67
65.86.220.0/24 Valid RIR databaseARIN, RADB 671 100% 67
177.177.233.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
178.83.142.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
217.25.15.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
87.83.114.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
82.108.214.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
87.86.93.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1

AS-SET

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

  • ROA: origin2
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced50
ChangePrefix or setDetailFull-table peers
ROA: origin68.164.142.0/24ROAs covering it name AS834, not AS218911. If AS218911 should announce it, add a ROA for AS218911.2 of 673
Route object: none68.164.142.0/24Route objects for it name AS834. Add a route object with origin AS218911 in the RIR database for the space.2 of 673
ROA: origin68.164.219.0/24ROAs covering it name AS834, not AS218911. If AS218911 should announce it, add a ROA for AS218911.2 of 673
Route object: none68.164.219.0/24Route objects for it name AS834. Add a route object with origin AS218911 in the RIR database for the space.2 of 673
Route object: RIR87.84.23.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR165.49.102.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR212.134.158.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

37.235.238.0/24RADB, RIPEValid
51.146.238.0/24RADB, RIPEValid
51.241.163.0/24RADB, RIPEValid
61.15.198.0/24APNIC, RADBValid
61.15.203.0/24APNIC, RADBValid
61.15.205.0/24APNIC, RADBValid
61.15.211.0/24APNIC, RADBValid
61.15.213.0/24APNIC, RADBValid
61.15.218.0/24APNIC, RADBValid
61.15.220.0/24APNIC, RADBValid
61.15.221.0/24APNIC, RADBValid
61.15.222.0/24APNIC, RADBValid
61.18.132.0/24APNIC, RADBValid
61.18.145.0/24APNIC, RADBValid
61.18.166.0/24APNIC, RADBValid
61.18.167.0/24APNIC, RADBValid
61.18.176.0/24APNIC, RADBValid
61.18.192.0/24APNIC, RADBValid
61.18.194.0/24APNIC, RADBValid
62.144.37.0/24RADB, RIPEValid
64.204.29.0/24ARIN, RADBValid
64.204.31.0/24ARIN, RADBValid
65.86.216.0/24ARIN, RADBValid
65.86.218.0/24ARIN, RADBValid
72.244.247.0/24ARIN, RADBValid
72.244.249.0/24ARIN, RADBValid
79.98.244.0/24RADB, RIPEValid
80.246.231.0/24RADB, RIPEValid
87.84.19.0/24RADBValid
87.84.21.0/24RADBValid
103.196.124.0/24RADBValid
118.103.240.0/24APNIC, RADBValid
139.165.92.0/24RADBValid
144.56.81.0/24RADB, RIPEValid
151.247.92.0/24RADB, RIPEValid
163.5.250.0/24RADB, RIPEValid
163.8.198.0/24APNIC, RADBValid
165.49.89.0/24RADBValid
178.93.208.0/24RADB, RIPEValid
185.13.227.0/24RADBValid
187.55.7.0/24RADB, RIPEValid
189.31.3.0/24RADB, RIPEValid
194.38.51.0/24RADB, RIPEValid
194.163.192.0/24RADB, RIPEValid
194.163.194.0/24RADB, RIPEValid
194.169.48.0/24RADB, RIPEValid
200.149.180.0/24RADB, RIPEValid
200.149.181.0/24RADB, RIPEValid
200.149.182.0/24RADB, RIPEValid
217.217.223.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.