# Time server pool problems since mid February

**URL:** <https://community.ntppool.org/t/time-server-pool-problems-since-mid-february/250>\
**Category:** Server operators\
**Tags:** monitoring\
**Created:** [July 10, 2017, 9:06am UTC](https://community.ntppool.org/t/time-server-pool-problems-since-mid-february/250 "2017-07-10T09:06:26Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![jfrater](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/jfrater/32/109_2.png) [@jfrater](https://community.ntppool.org/u/jfrater)\
**Post date:** [July 25, 2017, 4:15pm UTC](https://community.ntppool.org/t/time-server-pool-problems-since-mid-february/250/9 "2017-07-25T16:15:14Z")

</div>

I had this issue and it only got resolved when I changed the upstream route. I have a post [here](https://community.ntppool.org/t/problems-with-the-los-angeles-ipv4-monitoring-station/238)

What you could do is set up a tunnel to some other router so that traffic going to 207.171.3.17 gets re-routed via some other ISP.

If that works then at least you know if that other ISP has no problems sending NTP replies.

As a test I offer my route if you want to try it out (now that it’s working)

---

_[View the full topic](https://community.ntppool.org/t/time-server-pool-problems-since-mid-february/250)._