bgpreport

Network · data from 2026-11-12

AS219447 FLASHSPEEDLIMITED HONG KONG FLASH SPEED LIMITED

Registry name: FLASHSPEEDLIMITED HONG KONG FLASH SPEED LIMITED, HK · not in PeeringDB

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

Announced routes

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

178.95.21.0/24 Invalid: origin None 3 0%low visibility 2
82.108.135.0/24 Invalid: origin None 2 0%low visibility 2
178.94.54.0/24 Invalid: origin None 1 0%low visibility 1
178.95.138.0/24 Invalid: origin Other origin only 0 0%low visibility 1
188.220.85.0/24 Invalid: origin Other origin only 0 0%low visibility 1
87.84.17.0/24 Valid Other IRR onlyRADB 673 100% 67
154.16.222.0/24 Valid Other IRR onlyRADB 673 100% 67
87.84.22.0/24 Valid Other IRR onlyRADB 672 100% 66
144.56.116.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
178.92.178.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
178.93.191.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
189.12.136.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
62.144.43.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
68.164.65.0/24 Valid RIR databaseARIN, RADB 672 100% 67
72.244.48.0/24 Valid RIR databaseARIN, RADB 672 100% 67
164.37.234.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
187.14.182.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
189.12.139.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
194.231.142.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
217.8.204.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
217.8.206.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
82.47.191.0/24 Valid RIR databaseRADB, RIPE 1 0%low visibility 1
82.47.255.0/24 Valid RIR databaseRADB, RIPE 1 0%low visibility 1

AS-SET

AS219447 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 34 are in fix.csv.

  • ROA: origin5
  • Route object: none5
  • Route object: RIR3
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
ROA: origin178.95.21.0/24ROAs covering it name AS834, not AS219447. If AS219447 should announce it, add a ROA for AS219447.3 of 673
Route object: none178.95.21.0/24No route object for it. Add a route object with origin AS219447 in the RIR database for the space.3 of 673
ROA: origin82.108.135.0/24ROAs covering it name AS834, not AS219447. If AS219447 should announce it, add a ROA for AS219447.2 of 673
Route object: none82.108.135.0/24No route object for it. Add a route object with origin AS219447 in the RIR database for the space.2 of 673
ROA: origin178.94.54.0/24ROAs covering it name AS834, not AS219447. If AS219447 should announce it, add a ROA for AS219447.1 of 673
Route object: none178.94.54.0/24No route object for it. Add a route object with origin AS219447 in the RIR database for the space.1 of 673
ROA: origin178.95.138.0/24ROAs covering it name AS834, not AS219447. If AS219447 should announce it, add a ROA for AS219447.0 of 673
Route object: none178.95.138.0/24Route objects for it name AS834. Add a route object with origin AS219447 in the RIR database for the space.0 of 673
ROA: origin188.220.85.0/24ROAs covering it name AS3257, not AS219447. If AS219447 should announce it, add a ROA for AS219447.0 of 673
Route object: none188.220.85.0/24Route objects for it name AS3257. Add a route object with origin AS219447 in the RIR database for the space.0 of 673
Route object: RIR87.84.17.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR154.16.222.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR87.84.22.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

5.199.37.0/24RADB, RIPEValid
62.144.45.0/24RADB, RIPEValid
68.164.11.0/24ARIN, RADBValid
68.164.66.0/24ARIN, RADBValid
68.164.69.0/24ARIN, RADBValid
79.180.147.0/24RADB, RIPEValid
91.124.105.0/24RADB, RIPEValid
91.124.106.0/24RADB, RIPEValid
141.11.67.0/24RADB, RIPEValid
143.203.135.0/24ARIN, RADBValid
152.234.134.0/24RADB, RIPEValid
156.230.158.0/24AFRINICValid
156.230.161.0/24AFRINICValid
178.93.169.0/24RADB, RIPEValid
178.94.116.0/24RADB, RIPEValid
187.14.183.0/24RADB, RIPEValid
189.12.130.0/24RADB, RIPEValid
189.12.133.0/24RADB, RIPEValid
189.12.135.0/24RADB, RIPEValid
217.8.205.0/24RADB, RIPEValid
217.8.207.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.