bgpreport

Network · data from 2026-11-12

AS6404 FACTSET - FactSet Research Systems, Inc.

Registry name: FACTSET - FactSet Research Systems, Inc., US · not in PeeringDB

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

Announced routes

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

119.27.58.0/27 Invalid: origin None 1 0%low visibility 1
164.55.242.0/24 No ROA Nonecovered by 164.55.0.0/16 673 100% 67
164.55.245.0/24 No ROA Nonecovered by 164.55.0.0/16 673 100% 67
164.55.251.0/24 No ROA Nonecovered by 164.55.0.0/16 673 100% 67
164.55.252.0/23 No ROA Nonecovered by 164.55.0.0/16 673 100% 67
164.55.254.0/24 No ROA Other IRR onlyALTDB 673 100% 67
164.55.249.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
164.55.250.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
164.55.248.0/24 No ROA Other IRR onlyNTTCOM 671 100% 67
164.55.246.0/24 No ROA Other IRR onlyRADB, RIPE-NONAUTH 669 99% 67
64.209.89.0/24 Valid Other origin only 673 100% 67

AS-SET

AS6404 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 23 are in fix.csv.

  • ROA: origin1
  • ROA: none9
  • Route object: none6
  • Route object: RIR5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin119.27.58.0/27ROAs covering it name AS15830, not AS6404. If AS6404 should announce it, add a ROA for AS6404.1 of 673
Route object: none119.27.58.0/27No route object for it. Add a route object with origin AS6404 in the RIR database for the space.1 of 673
ROA: none164.55.242.0/24No ROA covers it. Add a ROA for AS6404, maxLength 24.673 of 673
Route object: none164.55.242.0/24No route object for it. A route object for 164.55.0.0/16 with origin AS6404 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6404 in the RIR database for the space.673 of 673
ROA: none164.55.245.0/24No ROA covers it. Add a ROA for AS6404, maxLength 24.673 of 673
Route object: none164.55.245.0/24No route object for it. A route object for 164.55.0.0/16 with origin AS6404 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6404 in the RIR database for the space.673 of 673
ROA: none164.55.251.0/24No ROA covers it. Add a ROA for AS6404, maxLength 24.673 of 673
Route object: none164.55.251.0/24No route object for it. A route object for 164.55.0.0/16 with origin AS6404 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6404 in the RIR database for the space.673 of 673
ROA: none164.55.252.0/23No ROA covers it. Add a ROA for AS6404, maxLength 23.673 of 673
Route object: none164.55.252.0/23No route object for it. A route object for 164.55.0.0/16 with origin AS6404 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6404 in the RIR database for the space.673 of 673
ROA: none164.55.254.0/24No ROA covers it. Add a ROA for AS6404, maxLength 24.673 of 673
Route object: RIR164.55.254.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none164.55.249.0/24No ROA covers it. Add a ROA for AS6404, maxLength 24.672 of 673
Route object: RIR164.55.249.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none164.55.250.0/24No ROA covers it. Add a ROA for AS6404, maxLength 24.672 of 673
Route object: RIR164.55.250.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none164.55.248.0/24No ROA covers it. Add a ROA for AS6404, maxLength 24.671 of 673
Route object: RIR164.55.248.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none164.55.246.0/24No ROA covers it. Add a ROA for AS6404, maxLength 24.669 of 673
Route object: RIR164.55.246.0/24Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.669 of 673
Route object: none64.209.89.0/24Route objects for it name AS19905. Add a route object with origin AS6404 in the RIR database for the space.673 of 673

Route objects not announced

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

164.55.0.0/16RADBNo ROA
164.55.232.0/24RADBNo 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.