Network · data from 2026-11-12
AS24423 FJGDWL - No. 207 Hualin Road, Fuzhou, Fujian, China
Registry name: FJGDWL - No. 207 Hualin Road, Fuzhou, Fujian, China, CN · not in PeeringDB
4IPv4 routes
100.0% RPKI valid · 0.0% with a route object
16IPv6 routes
100.0% RPKI valid · 0.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
20 with no route object for this origin
19Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS24423, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS24423, 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.
| 240a:41b0::/34 | Valid | None | 72 11% |
| 180.233.0.0/18 | Valid | None | 57 8%low visibility |
| 202.153.48.0/20 | Valid | None | 57 8%low visibility |
| 203.190.100.0/24 | Valid | None | 57 8%low visibility |
| 203.190.101.0/24 | Valid | None | 57 8%low visibility |
| 2402:4440:9000::/39 | Valid | None | 46 7%low visibility |
| 2402:4440:9200::/48 | Valid | None | 46 7%low visibility |
| 2402:4440:9600::/48 | Valid | None | 46 7%low visibility |
| 2402:4440:9800::/48 | Valid | None | 46 7%low visibility |
| 2402:4440:9900::/48 | Valid | None | 46 7%low visibility |
| 2402:4440:9a00::/48 | Valid | None | 46 7%low visibility |
| 2402:4440:9b00::/48 | Valid | None | 46 7%low visibility |
| 2402:4440:9c00::/48 | Valid | None | 46 7%low visibility |
| 2402:4440:9d00::/48 | Valid | None | 46 7%low visibility |
| 2402:4440:9e00::/48 | Valid | None | 46 7%low visibility |
| 2402:4440:a000::/39 | Valid | None | 46 7%low visibility |
| 2402:4440:a800::/46 | Valid | None | 46 7%low visibility |
| 2402:4440:9400::/48 | Valid | None | 43 7%low visibility |
| 2402:4440:9810::/48 | Valid | None | 43 7%low visibility |
| 2402:4440:a810::/46 | Valid | None | 43 7%low visibility |
AS-SET
AS24423 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 20 are in fix.csv.
- Route object: none20
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 240a:41b0::/34 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 180.233.0.0/18 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 202.153.48.0/20 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 203.190.100.0/24 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 203.190.101.0/24 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 2402:4440:9000::/39 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 2402:4440:9200::/48 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 2402:4440:9600::/48 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 2402:4440:9800::/48 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 2402:4440:9900::/48 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 2402:4440:9a00::/48 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 2402:4440:9b00::/48 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 2402:4440:9c00::/48 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 2402:4440:9d00::/48 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 2402:4440:9e00::/48 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 2402:4440:a000::/39 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 2402:4440:a800::/46 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 2402:4440:9400::/48 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 2402:4440:9810::/48 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
| Route object: none | 2402:4440:a810::/46 | No route object for it. Add a route object with origin AS24423 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS24423 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.