# Help with odd spike in Apollo Router query\_planning time

**URL:** https://community.apollographql.com/t/help-with-odd-spike-in-apollo-router-query-planning-time/8164
**Category:** Router
**Tags:** router, graphos
**Created:** [January 17, 2025, 8:36am UTC](https://community.apollographql.com/t/help-with-odd-spike-in-apollo-router-query-planning-time/8164 "2025-01-17T08:36:34Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Ash\_Marchington](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/ash_marchington/32/5486_2.png) [@Ash\_Marchington](https://community.apollographql.com/u/Ash_Marchington)
#### Post date: [January 17, 2025, 8:36am UTC](https://community.apollographql.com/t/help-with-odd-spike-in-apollo-router-query-planning-time/8164/1 "2025-01-17T08:36:34Z")

</div>

Hi,

I have been testing using apollo router in place of grafbase-gateway to route to my subgraphs, but I started running into issues with the query planner of the apollo router.

I have 13 subgraphs running locally, all written in Rust in case that changes anything, and if I query them through apollo router the query planning stage takes 30 seconds to complete.

 ![image](https://us1.discourse-cdn.com/flex019/uploads/apollographql/original/2X/c/c3375d82a9d5a6f44a2d1c3ceac1bdce4f797562.png)

The same query is instant with grafbase-gateway.

Is there anyway to get more log information from the query planner to see what is happening here?

This is with the latest router release as well `1.59.1`

Kind Regards,

Ashley

---

<div class="post-metadata">

### Author: ![shanemyrick](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/shanemyrick/32/5474_2.png) [@shanemyrick](https://community.apollographql.com/u/shanemyrick)
#### Post date: [January 17, 2025, 8:31pm UTC](https://community.apollographql.com/t/help-with-odd-spike-in-apollo-router-query-planning-time/8164/2 "2025-01-17T20:31:34Z")

</div>

Using the Otel attributes provides the details for time. which is what you have already. There is also the aggregated [metrics](https://www.apollographql.com/docs/graphos/reference/router/telemetry/instrumentation/standard-instruments).

What is interesting is that the busy time of that plan was `0.139ms`, so pretty quick. There was just a lot of idle time.

What helps with all issues is actually a link to reproduce the error or at a mimimum the operation and supergraph you used that caused a long planning time.

Were you running other significant load through the Router at the time of operation?