4 ms·
It was mainly due to the poorly coded snapshat program: https://news.ntppool.org/2016/12/load/ https://news.ntppool.org/2016/12/load/ EDIT: this post was indee
by Faaak 10y ago
It was mainly due to the poorly coded snapshat program: https://news.ntppool.org/2016/12/load/ https://news.ntppool.org/2016/12/load/
EDIT: this post was indeed from 2014. My bad then. however the same issue started again two weeks ago (~17 dec 2016).
- mw6621 10y agoSeems like the post was written in 2014 while the Snapchat NTP issue was more recent.
- sigio 10y agothis post was from 2014, so I doubt it was this months snapchat issue
- minsight 10y agoIt was mainly due to Virtualbox querying every 64 seconds.
- brian_cunnie 10y agoHere is a visual representation of the affect of the snapchat broken-ness on my NTP server: https://cloud.githubusercontent.com/assets/1020675/21468123/ac026274-c9d2-11e6-8334-2f56e9c9d20f.png https://cloud.githubusercontent.com/assets/1020675/21468123/... Note that inbound traffic which was steady at ~4k packets/sec spikes as high as five times as much. Also note that the snapchat traffic followed a circadian rhythm (much higher traffic during the daytime).