# How to Troubleshoot Kibana Time-Outs **URL:** \ **Category:** Kibana\ **Created:** [April 18, 2016, 3:08pm UTC](https://discuss.elastic.co/t/how-to-troubleshoot-kibana-time-outs/47674 "2016-04-18T15:08:29Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Maxwell\_Flanders](https://avatars.discourse-cdn.com/v4/letter/m/eb8c5e/32.png) [@Maxwell\_Flanders](https://discuss.elastic.co/u/Maxwell_Flanders)\ **Post date:** [April 18, 2016, 3:08pm UTC](https://discuss.elastic.co/t/how-to-troubleshoot-kibana-time-outs/47674/1 "2016-04-18T15:08:29Z")
I have been experiencing an issue where occasionally my Kibana stops working stating a time-out trying to connect to elasticsearch as the cause. (I have marvel installed) Usually these go away by the next day, and occasionally i have been able to re-gain access to my data by increasing the timeout on kibana. However I can't figure out how to troubleshoot this issue. I suspect it may be that ES is storing some extremely large individual documents but I cannot find them, there's just too many logs to dig through by hand. What can I do to approach this issue?? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [April 18, 2016, 9:37pm UTC](https://discuss.elastic.co/t/how-to-troubleshoot-kibana-time-outs/47674/2 "2016-04-18T21:37:36Z")
If you have marvel installed, take a look at things around the time of the search and see if you can correlate anything. High heap/CPU, an increase in searches etc. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:55pm UTC](https://discuss.elastic.co/t/how-to-troubleshoot-kibana-time-outs/47674/3 "2017-07-06T13:55:43Z")