If it's a view, then the spatial index parameters of the base table are what matters -- does Catalog report those correctly?
I do question the wisdom of using three levels of spatial index. I've only seen one table in the past fifteen years of SDE consulting which got a performance benefit from three vs two indexing levels, and the overall performance was so bad, the (very diiferent) data sources should really have been mapped to different tables.
Thanks for the reply Vince. The underlying table is reporting the same spatial index grid as what is shown when I do a sdelayer -o describe_long. The 3 levels of grid was created when I clicked the "recalculate" button so it wasn't a conscious choice by me or the company to have that. Should I delete level three after ArcCatalog recalculate the grid? The view is terribly slow which is why I thought it might be the spatial index to begin with.