bgpreport

Network · data from 2026-11-12

AS36843 NORTHWEST-REGIONAL-DATACENTER - Florida State University

Registry name: NORTHWEST-REGIONAL-DATACENTER - Florida State University, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS36843, 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.
128.186.217.0/28 No ROA None 1 0%low visibility 1
146.201.218.0/24 No ROA Other IRR onlyRADB 666 99% 69
146.201.219.0/24 No ROA Other IRR onlyRADB 666 99% 69
199.44.67.0/24 No ROA Other IRR onlyRADB 666 99% 69
199.44.72.0/24 No ROA Other IRR onlyRADB 666 99% 69
206.224.200.0/21 No ROA Other IRR onlyALTDB 666 99% 69
206.224.208.0/20 No ROA Other IRR onlyALTDB 666 99% 69
64.56.80.0/23 Valid RIR databaseARIN, RADB 666 99% 69
108.59.20.0/24 Valid RIR databaseARIN, RADB 666 99% 69
108.59.23.0/24 Valid RIR databaseARIN, RADB 666 99% 69
162.223.23.0/24 Valid RIR databaseARIN, RADB 666 99% 69

AS-SET

AS36843 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: none7
  • Route object: none1
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none128.186.217.0/28No ROA covers it. Add a ROA for AS36843, maxLength 28.1 of 673
Route object: none128.186.217.0/28No route object for it. Add a route object with origin AS36843 in the RIR database for the space.1 of 673
ROA: none146.201.218.0/24No ROA covers it. Add a ROA for AS36843, maxLength 24.666 of 673
Route object: RIR146.201.218.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none146.201.219.0/24No ROA covers it. Add a ROA for AS36843, maxLength 24.666 of 673
Route object: RIR146.201.219.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none199.44.67.0/24No ROA covers it. Add a ROA for AS36843, maxLength 24.666 of 673
Route object: RIR199.44.67.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none199.44.72.0/24No ROA covers it. Add a ROA for AS36843, maxLength 24.666 of 673
Route object: RIR199.44.72.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none206.224.200.0/21No ROA covers it. Add a ROA for AS36843, maxLength 21.666 of 673
Route object: RIR206.224.200.0/21Route object only in ALTDB. Add it in the RIR database for the space.666 of 673
ROA: none206.224.208.0/20No ROA covers it. Add a ROA for AS36843, maxLength 20.666 of 673
Route object: RIR206.224.208.0/20Route object only in ALTDB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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

131.91.252.0/22ALTDBNo ROA
151.132.236.0/23RADBNo 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.