# Pingdom logging timeouts

**URL:** <https://community.prismic.io/t/pingdom-logging-timeouts/8854>\
**Category:** Developing with Prismic\
**Tags:** rest-api\
**Created:** [January 31, 2022, 11:17am UTC](https://community.prismic.io/t/pingdom-logging-timeouts/8854 "2022-01-31T11:17:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jake](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/jake/32/5120_2.png) [@jake](https://community.prismic.io/u/jake)\
**Post date:** [January 31, 2022, 11:17am UTC](https://community.prismic.io/t/pingdom-logging-timeouts/8854/1 "2022-01-31T11:17:40Z")

</div>

Hello and happy Monday!

We have pingdom setup to detect when our site is down, and it's logging quite regularly a timeout, we have checked the site and it's working/up and the Prismic API is also up and responsive. We're unsure what the problem is?

Pingdom is getting a timeout requesting the [www.Aspria.com](http://www.aspria.com/) site (Pingdom only waits 5 seconds). During the same time periods the Node app is logging timeouts between it and Prismic.

Please advise/pointers.

Thank you kindly  
Jake

```auto
2022-01-30T16:07:55.418104587Z ERROR request to https://aspria.cdn.prismic.io/api/v2?routes=%5B%7B%22type%22%3A%22journal_post%22%2C%22path%22%3A%22%2F%3Alang%2F%3Ajournal%2F%3Acategory%2F%3Auid%2F%22%2C%22resolvers%22%3A%7B%22category%22%3A%22category_relation%22%2C%22journal%22%3A%22category_relation.link_to_journal%22%7D%7D%2C%7B%22type%22%3A%22ondemand_post%22%2C%22path%22%3A%22%2F%3Alang%2F%3Aondemand%2F%3Acategory%2F%3Auid%2F%22%2C%22resolvers%22%3A%7B%22category%22%3A%22category_relation%22%2C%22ondemand%22%3A%22category_relation.link_to_ondemand%22%7D%7D%2C%7B%22type%22%3A%22press_post%22%2C%22path%22%3A%22%2F%3Alang%2Fpress%2F%3Acategory%2F%3Auid%2F%22%2C%22resolvers%22%3A%7B%22category%22%3A%22category_relation%22%7D%7D%2C%7B%22type%22%3A%22club_campaign%22%2C%22path%22%3A%22%2F%3Alang%2F%3Acontroller%2Fcampaigns%2F%3Auid%2F%22%2C%22resolvers%22%3A%7B%22controller%22%3A%22club_relation%22%7D%7D%2C%7B%22type%22%3A%22partner%22%2C%22path%22%3A%22%2F%3Alang%2Fpartner%2F%3Auid%2F%22%7D%5D failed, reason: connect ETIMEDOUT 108.156.28.57:443

```

---

<div class="post-metadata">

**Author:** ![Phil](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/phil/32/14_2.png) [@Phil](https://community.prismic.io/u/Phil)\
**Post date:** [January 31, 2022, 3:21pm UTC](https://community.prismic.io/t/pingdom-logging-timeouts/8854/3 "2022-01-31T15:21:31Z")

</div>

Hi Jake,

Good to see you.

Can you tell me if your website application is using any caching? Specifically on the master `ref`? It's usually the cause of issues like this.

Thanks.

---

<div class="post-metadata">

**Author:** ![jake](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/jake/32/5120_2.png) [@jake](https://community.prismic.io/u/jake)\
**Post date:** [January 31, 2022, 4:08pm UTC](https://community.prismic.io/t/pingdom-logging-timeouts/8854/4 "2022-01-31T16:08:25Z")

</div>

Hey Phil,

Ok thank you, this rings a bell with one of our setups, so will investigate and let you know if this fixes it.

Cheers