Network · data from 2026-11-12
AS19477 FLYINGJ - F J Management Inc.
Registry name: FLYINGJ - F J Management Inc., US · not in PeeringDB
11IPv4 routes
0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
11No ROA
11 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
4Route objects not announced
registered with origin AS19477, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS19477, 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.
| 204.110.224.0/24 | No ROA | Nonecovered by 204.110.224.0/20 | 673 100% |
| 204.110.225.0/24 | No ROA | Nonecovered by 204.110.224.0/20 | 673 100% |
| 204.110.226.0/24 | No ROA | Nonecovered by 204.110.224.0/20 | 673 100% |
| 204.110.227.0/24 | No ROA | Nonecovered by 204.110.224.0/20 | 673 100% |
| 204.110.229.0/24 | No ROA | Nonecovered by 204.110.224.0/20 | 673 100% |
| 204.110.230.0/24 | No ROA | Nonecovered by 204.110.224.0/20 | 673 100% |
| 204.110.231.0/24 | No ROA | Nonecovered by 204.110.224.0/20 | 673 100% |
| 204.110.232.0/24 | No ROA | Nonecovered by 204.110.224.0/20 | 673 100% |
| 204.110.233.0/24 | No ROA | Nonecovered by 204.110.224.0/20 | 673 100% |
| 204.110.235.0/24 | No ROA | Nonecovered by 204.110.224.0/20 | 673 100% |
| 204.110.236.0/24 | No ROA | Nonecovered by 204.110.224.0/20 | 673 100% |
AS-SET
AS19477 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 26 are in fix.csv.
- ROA: none11
- Route object: none11
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 204.110.224.0/24 | No ROA covers it. Add a ROA for AS19477, maxLength 24. |
| Route object: none | 204.110.224.0/24 | No route object for it. A route object for 204.110.224.0/20 with origin AS19477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19477 in the RIR database for the space. |
| ROA: none | 204.110.225.0/24 | No ROA covers it. Add a ROA for AS19477, maxLength 24. |
| Route object: none | 204.110.225.0/24 | No route object for it. A route object for 204.110.224.0/20 with origin AS19477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19477 in the RIR database for the space. |
| ROA: none | 204.110.226.0/24 | No ROA covers it. Add a ROA for AS19477, maxLength 24. |
| Route object: none | 204.110.226.0/24 | No route object for it. A route object for 204.110.224.0/20 with origin AS19477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19477 in the RIR database for the space. |
| ROA: none | 204.110.227.0/24 | No ROA covers it. Add a ROA for AS19477, maxLength 24. |
| Route object: none | 204.110.227.0/24 | No route object for it. A route object for 204.110.224.0/20 with origin AS19477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19477 in the RIR database for the space. |
| ROA: none | 204.110.229.0/24 | No ROA covers it. Add a ROA for AS19477, maxLength 24. |
| Route object: none | 204.110.229.0/24 | No route object for it. A route object for 204.110.224.0/20 with origin AS19477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19477 in the RIR database for the space. |
| ROA: none | 204.110.230.0/24 | No ROA covers it. Add a ROA for AS19477, maxLength 24. |
| Route object: none | 204.110.230.0/24 | No route object for it. A route object for 204.110.224.0/20 with origin AS19477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19477 in the RIR database for the space. |
| ROA: none | 204.110.231.0/24 | No ROA covers it. Add a ROA for AS19477, maxLength 24. |
| Route object: none | 204.110.231.0/24 | No route object for it. A route object for 204.110.224.0/20 with origin AS19477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19477 in the RIR database for the space. |
| ROA: none | 204.110.232.0/24 | No ROA covers it. Add a ROA for AS19477, maxLength 24. |
| Route object: none | 204.110.232.0/24 | No route object for it. A route object for 204.110.224.0/20 with origin AS19477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19477 in the RIR database for the space. |
| ROA: none | 204.110.233.0/24 | No ROA covers it. Add a ROA for AS19477, maxLength 24. |
| Route object: none | 204.110.233.0/24 | No route object for it. A route object for 204.110.224.0/20 with origin AS19477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19477 in the RIR database for the space. |
| ROA: none | 204.110.235.0/24 | No ROA covers it. Add a ROA for AS19477, maxLength 24. |
| Route object: none | 204.110.235.0/24 | No route object for it. A route object for 204.110.224.0/20 with origin AS19477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19477 in the RIR database for the space. |
| ROA: none | 204.110.236.0/24 | No ROA covers it. Add a ROA for AS19477, maxLength 24. |
| Route object: none | 204.110.236.0/24 | No route object for it. A route object for 204.110.224.0/20 with origin AS19477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19477 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS19477 whose prefix no peer sees AS19477 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.16.177.0/24 | RADB | No ROA |
| 192.233.116.0/24 | RADB | No ROA |
| 199.233.116.0/24 | RADB | No ROA |
| 204.110.224.0/20 | RADB | No ROA |
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.