bgpreport

Network · data from 2026-11-12

AS33397 GENSOCIETYUTAH - Genealogical Society of Utah

Registry name: GENSOCIETYUTAH - Genealogical Society of Utah, US · not in PeeringDB

2IPv4 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
4No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS33397, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS33397, 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.
2632:1:400::/40 No ROA None 630 99% 67
2632:104::/32 No ROA None 630 99% 67
216.49.189.0/24 No ROA Other origin only 194 29% 58
204.9.224.0/22 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS33397 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 12 are in fix.csv.

  • ROA: none4
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2632:1:400::/40No ROA covers it. Add a ROA for AS33397, maxLength 40.630 of 636
Route object: none2632:1:400::/40No route object for it. Add a route object with origin AS33397 in the RIR database for the space.630 of 636
ROA: none2632:104::/32No ROA covers it. Add a ROA for AS33397, maxLength 32.630 of 636
Route object: none2632:104::/32No route object for it. Add a route object with origin AS33397 in the RIR database for the space.630 of 636
ROA: none216.49.189.0/24No ROA covers it. Add a ROA for AS33397, maxLength 24.194 of 673
Route object: none216.49.189.0/24Route objects for it name AS19648. Add a route object with origin AS33397 in the RIR database for the space.194 of 673
ROA: none204.9.224.0/22No ROA covers it. Add a ROA for AS33397, maxLength 22.673 of 673
Route object: RIR204.9.224.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

204.9.224.0/21RADBNo ROA
204.9.228.0/22RADBNo ROA
2620:10e:1000::/47RADBNo ROA
2620:10e:1002::/47RADBNo 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.