Adding servers to the China zone


Done! Thank you.

I’d like to add a feature to the site so you can self-add to a special “extra overflow” zone; or alternatively - as discussed elsewhere - just make the system “figure it out” based on which zones have extra capacity and which needs help (and then add from servers with a net speed above some number).


Thanks… Would be nice to be able to edit it.


That’s a good idea in theory, but it would be pretty rough for some people if their traffic goes way up as the system adjusts…


Could perhaps be an “opt-in” model?



You didnt even make a dent in the server by adding .br, .cn and .tr. - it only took a hit of 5-20Mbit :slight_smile:

It is one of Leo’s NTP servers and it has a dedicated 100mbit fiber connection. There is still capacity left, so if there is a need you can add it to other countries as well. What about eg. India? They seem to have only 5 NTP servers.


Hi @ask

Is there other countries in need of additional servers? I was thinking about India.

If so, please feel free to add to this one.



I would like to mention that the China zone would still benefit from new servers. One of my servers is in Singapore and also serves the China zone. Singapore itself seems to be a fairly busy zone as well. The server used to have a 2TB/month transfer limit, but seeing that the demand is much higher than that, I upgraded to a 4TB/month plan a few weeks ago. I switched my netspeed setting in the pool to 1000Mbit, and for the last week I have been sending 200+GB of NTP traffic per day. That would mean 6+TB/month, so I’ll need to adjust my netspeed setting a bit lower to stay below 4TB/month.

I would not mind if others took a slice of this traffic.


This one can be added to .cn


Done! I added it to in, too.

Any suggestions for what to name the “I volunteer my server to extra busy underserved zones”-zone? “overflow”? “overflow-optin”? (It will show up on the website next to the country/continent ones).


It was I volunteered to serve in the .in pool :blush:, should only be in .cn - it is an ordinary consumer ADSL router that cannot cope with this amount of traffic, so it is thrown out of the pool every time is has gained “10+”.

I am not sure overflow-optin is descriptive, what about “Assist underserved regions”.


Re naming. If you are looking for a short term to complement the current europe, north-america, oceania etc zones, perhaps just plain “extra”? overflow would also work. relief-valve? superhero? reserve? boost? servers-without-borders? reinforcement?

Zones: @ asia cn sg fill-in-the-word-here

I know this is difficult, sorry I can’t help you here.


What about “manually-added”?


It seems like the .cn zone is slowly failing again. If we look at the statistics from the last year there is been a significant drop in servers over the year.


Not only cn pool affected. Even jp pool shows obvious drop in ipv4 server counts over the last year (not counting the spike). Right now tw pool has only 3 ipv4 servers published; mine got kicked out at 768kbps… Several months before I could maintain publishing at 25mbps. Sigh.


In India zone is also a disaster. Even at the 384k setting in (IP 4 and 6) my Bangalore server is going to bust it’s 3TB traffic cap this month. With no way to keep it in budget I just scheduled it’s deletion from the IP4 pool.


In India there is even fewer servers than in China and a similar sized population, so traffic must be very high.

Right now, there is 7 servers operational in China and is receiving about 70Mbit/s of NTP traffic, so it will be very difficult for someone to join and maintain a position.


Two new China servers in Shanghai ( (

ref GPS


We have massive increase in traffic on two of our Chinese zone servers since last few days.
We have reached full wirespeed on the interfaces (over 100ksps)

Is anything significant going on with NTP in China?


I think it is because several servers has either left or has been kicked out due to the high demands.


We really need some mechanism to restrict times of a particular server entry being returned by pool dns to clients. Burdening those not-so-strong servers will result in eventual pool collapse.