That's really hard to say without spending time understanding your schema, distribution of the relationships in that the schema, and what datastore you're using and how it's configured. Are those purely check latencies? If so, yes they are unreasonably high. If that's a combination of all API request types, then the distribution of those could be effecting the numbers (Expand, Lookup are quite expensive operations). If everything is "reasonable" from the perspective of your usage, then it's likely to simply be a lack of optimization in SpiceDB, which we'd need to the traces/profiles to identify in order to identify and create a GitHub issue for.