bgpreport

Network · data from 2026-11-12

AS63614 QishangOnline - A4, 5th Floor, Tower C, Triumph Plaza, Unit A, No 143,

Registry name: QishangOnline - A4, 5th Floor, Tower C, Triumph Plaza, Unit A, No 143,, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63614, 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.
103.25.27.0/24 Invalid: maxLength None 134 20% 54
27.0.164.0/23 Valid None 672 100% 67
27.0.166.0/23 Valid None 672 100% 67
2402:e880::/48 Valid None 636 100% 67
43.227.140.0/22 Valid Other origin only 109 16% 44
45.127.144.0/21 Valid Other origin only 109 16% 44
103.25.24.0/22 Valid Other origin only 109 16% 44
103.196.88.0/21 Valid Other origin only 109 16% 44
114.113.224.0/20 Valid Other origin only 109 16% 44
122.115.32.0/19 Valid Other origin only 109 16% 44

AS-SET

AS63614 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 11 are in fix.csv.

  • ROA: maxLength1
  • Route object: none10
ChangePrefix or setDetailFull-table peers
ROA: maxLength103.25.27.0/24ROA 103.25.24.0/22 AS63614 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 103.25.27.0/24.134 of 673
Route object: none103.25.27.0/24No route object for it. Add a route object with origin AS63614 in the RIR database for the space.134 of 673
Route object: none27.0.164.0/23No route object for it. Add a route object with origin AS63614 in the RIR database for the space.672 of 673
Route object: none27.0.166.0/23No route object for it. Add a route object with origin AS63614 in the RIR database for the space.672 of 673
Route object: none2402:e880::/48No route object for it. Add a route object with origin AS63614 in the RIR database for the space.636 of 636
Route object: none43.227.140.0/22Route objects for it name AS4847. Add a route object with origin AS63614 in the RIR database for the space.109 of 673
Route object: none45.127.144.0/21Route objects for it name AS4847. Add a route object with origin AS63614 in the RIR database for the space.109 of 673
Route object: none103.25.24.0/22Route objects for it name AS4847. Add a route object with origin AS63614 in the RIR database for the space.109 of 673
Route object: none103.196.88.0/21Route objects for it name AS4847. Add a route object with origin AS63614 in the RIR database for the space.109 of 673
Route object: none114.113.224.0/20Route objects for it name AS4847. Add a route object with origin AS63614 in the RIR database for the space.109 of 673
Route object: none122.115.32.0/19Route objects for it name AS4847. Add a route object with origin AS63614 in the RIR database for the space.109 of 673

Route objects not announced

Every route object with origin AS63614 is announced.

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.