bgpreport

Network · data from 2026-11-12

AS23341 FITAS - Fashion Institute of Technology

Registry name: FITAS - Fashion Institute of Technology, US · not in PeeringDB

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

Announced routes

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

143.55.3.0/24 Valid None 672 100% 67
143.55.4.0/24 Valid None 672 100% 67
143.55.5.0/24 Valid None 672 100% 67
143.55.6.0/24 Valid None 672 100% 67
143.55.7.0/24 Valid None 672 100% 67
143.55.8.0/24 Valid None 672 100% 67
143.55.10.0/24 Valid None 672 100% 67
143.55.11.0/24 Valid None 672 100% 67
143.55.13.0/24 Valid None 672 100% 67
143.55.80.0/23 Valid None 672 100% 67
143.55.155.0/24 Valid None 672 100% 67
143.55.156.0/22 Valid None 672 100% 67
143.55.160.0/20 Valid None 672 100% 67
143.55.12.0/24 Valid None 2 0%low visibility 2

AS-SET

AS23341 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 14 are in fix.csv.

  • Route object: none14
ChangePrefix or setDetailFull-table peers
Route object: none143.55.3.0/24No route object for it. Add a route object with origin AS23341 in the RIR database for the space.672 of 673
Route object: none143.55.4.0/24No route object for it. Add a route object with origin AS23341 in the RIR database for the space.672 of 673
Route object: none143.55.5.0/24No route object for it. Add a route object with origin AS23341 in the RIR database for the space.672 of 673
Route object: none143.55.6.0/24No route object for it. Add a route object with origin AS23341 in the RIR database for the space.672 of 673
Route object: none143.55.7.0/24No route object for it. Add a route object with origin AS23341 in the RIR database for the space.672 of 673
Route object: none143.55.8.0/24No route object for it. Add a route object with origin AS23341 in the RIR database for the space.672 of 673
Route object: none143.55.10.0/24No route object for it. Add a route object with origin AS23341 in the RIR database for the space.672 of 673
Route object: none143.55.11.0/24No route object for it. Add a route object with origin AS23341 in the RIR database for the space.672 of 673
Route object: none143.55.13.0/24No route object for it. Add a route object with origin AS23341 in the RIR database for the space.672 of 673
Route object: none143.55.80.0/23No route object for it. Add a route object with origin AS23341 in the RIR database for the space.672 of 673
Route object: none143.55.155.0/24No route object for it. Add a route object with origin AS23341 in the RIR database for the space.672 of 673
Route object: none143.55.156.0/22No route object for it. Add a route object with origin AS23341 in the RIR database for the space.672 of 673
Route object: none143.55.160.0/20No route object for it. Add a route object with origin AS23341 in the RIR database for the space.672 of 673
Route object: none143.55.12.0/24No route object for it. Add a route object with origin AS23341 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS23341 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.