bgpreport

Network · data from 2026-11-12

AS63254 NASSAU-COUNTY-NY - Department of Information Technology

Registry name: NASSAU-COUNTY-NY - Department of Information Technology, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63254, 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.76.145.0/24 No ROA Other origin onlycovered by 204.76.144.0/21 673 100% 67
204.76.149.0/24 No ROA Other origin onlycovered by 204.76.144.0/21 672 100% 67
204.76.150.0/24 No ROA Other origin onlycovered by 204.76.144.0/21 672 100% 67
204.76.151.0/24 No ROA Other origin onlycovered by 204.76.144.0/21 672 100% 67
204.76.144.0/21 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS63254 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 10 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none204.76.145.0/24No ROA covers it. Add a ROA for AS63254, maxLength 24.673 of 673
Route object: none204.76.145.0/24Route objects for it name AS46887. A route object for 204.76.144.0/21 with origin AS63254 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63254 in the RIR database for the space.673 of 673
ROA: none204.76.149.0/24No ROA covers it. Add a ROA for AS63254, maxLength 24.672 of 673
Route object: none204.76.149.0/24Route objects for it name AS46887. A route object for 204.76.144.0/21 with origin AS63254 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63254 in the RIR database for the space.672 of 673
ROA: none204.76.150.0/24No ROA covers it. Add a ROA for AS63254, maxLength 24.672 of 673
Route object: none204.76.150.0/24Route objects for it name AS46887. A route object for 204.76.144.0/21 with origin AS63254 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63254 in the RIR database for the space.672 of 673
ROA: none204.76.151.0/24No ROA covers it. Add a ROA for AS63254, maxLength 24.672 of 673
Route object: none204.76.151.0/24Route objects for it name AS46887. A route object for 204.76.144.0/21 with origin AS63254 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63254 in the RIR database for the space.672 of 673
ROA: none204.76.144.0/21No ROA covers it. Add a ROA for AS63254, maxLength 21.673 of 673
Route object: RIR204.76.144.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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