bgpreport

Network · data from 2026-11-12

AS21545 KCOENET - Kings County Office of Education

Registry name: KCOENET - Kings County Office of Education, US · not in PeeringDB

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

Announced routes

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

206.78.242.0/24 No ROA Nonecovered by 206.78.240.0/20 669 99% 68
137.164.13.88/30 No ROA None 1 0%low visibility 1
137.164.13.236/30 No ROA None 1 0%low visibility 1
2607:f380::118:9a40:d580/122 No ROA None 1 0%low visibility 1
2607:f380::118:9a40:dec0/122 No ROA None 1 0%low visibility 1
206.78.64.0/19 No ROA Other IRR onlyRADB 669 99% 68
206.78.96.0/20 No ROA Other IRR onlyRADB 669 99% 68
206.78.240.0/20 No ROA Other IRR onlyRADB 669 99% 68

AS-SET

AS21545 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 16 are in fix.csv.

  • ROA: none8
  • Route object: none5
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none206.78.242.0/24No ROA covers it. Add a ROA for AS21545, maxLength 24.669 of 673
Route object: none206.78.242.0/24No route object for it. A route object for 206.78.240.0/20 with origin AS21545 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21545 in the RIR database for the space.669 of 673
ROA: none137.164.13.88/30No ROA covers it. Add a ROA for AS21545, maxLength 30.1 of 673
Route object: none137.164.13.88/30No route object for it. Add a route object with origin AS21545 in the RIR database for the space.1 of 673
ROA: none137.164.13.236/30No ROA covers it. Add a ROA for AS21545, maxLength 30.1 of 673
Route object: none137.164.13.236/30No route object for it. Add a route object with origin AS21545 in the RIR database for the space.1 of 673
ROA: none2607:f380::118:9a40:d580/122No ROA covers it. Add a ROA for AS21545, maxLength 122.1 of 636
Route object: none2607:f380::118:9a40:d580/122No route object for it. Add a route object with origin AS21545 in the RIR database for the space.1 of 636
ROA: none2607:f380::118:9a40:dec0/122No ROA covers it. Add a ROA for AS21545, maxLength 122.1 of 636
Route object: none2607:f380::118:9a40:dec0/122No route object for it. Add a route object with origin AS21545 in the RIR database for the space.1 of 636
ROA: none206.78.64.0/19No ROA covers it. Add a ROA for AS21545, maxLength 19.669 of 673
Route object: RIR206.78.64.0/19Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none206.78.96.0/20No ROA covers it. Add a ROA for AS21545, maxLength 20.669 of 673
Route object: RIR206.78.96.0/20Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none206.78.240.0/20No ROA covers it. Add a ROA for AS21545, maxLength 20.669 of 673
Route object: RIR206.78.240.0/20Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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