# Not able to add new server: IPv6 2003🅰47f:abe4::1

**URL:** <https://community.ntppool.org/t/not-able-to-add-new-server-ipv6-200347f-1/1663>\
**Category:** Server operators\
**Tags:** monitoring\
**Created:** [May 19, 2020, 5:09am UTC](https://community.ntppool.org/t/not-able-to-add-new-server-ipv6-200347f-1/1663 "2020-05-19T05:09:35Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Kashra](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/kashra/32/582_2.png) [@Kashra](https://community.ntppool.org/u/Kashra)\
**Post date:** [May 19, 2020, 11:28pm UTC](https://community.ntppool.org/t/not-able-to-add-new-server-ipv6-200347f-1/1663/5 "2020-05-19T23:28:43Z")

</div>

Well, the problem is, the servers worked just fine in the past, up to beginning of Feb. 2020 and stopped working all at once, with no changes made to the config for over a year by now.  
In addition to that my other servers are syncing to them just fine + they are in active production use with my customers, there are no restrictions which could cause this, even following the recommended config.

I tried this: Connected server to a Vodafone Business Cable static IPv6 subnet, see here:

```
https://www.ntppool.org/scores/2a02:8106:19::1

```

Works just fine.  
The very _same_ server hooked to a T-Systems (German Telekom IP) at 2003:a:157f:b76d::0

No luck at all.

Can anyone add/test 2003:a:157f:b76d::0 to verify?

I did `ntpsweep -l 2003:a:157f:b76d::0` from several locations, works fine.

---

_[View the full topic](https://community.ntppool.org/t/not-able-to-add-new-server-ipv6-200347f-1/1663)._
