Remember in 2003 when netgear hardcoded a university's NTP server into a ton of their products? Well....

https://www.google.com/search?&q=university+ntp+server+netge...

https://pages.cs.wisc.edu/~plonka/netgear-sntp/

Apparently they didn't just do that, they also had them make requests way more frequently than they needed to (I guess particularly surprising given that they'd already have to be fairly negligent to have the server hard-coded):

> We learned that these packets appeared to be legitimate, well-formed Simple Network Time Protocol (SNTP) version 1 queries, albeit at an inexplicably high rate from each client host. For instance, during one trace, many clients produced about one query per second. This would be highly unusual for a properly constructed SNTP client, since an application which uses SNTP is merely interested in setting its own clock relatively accurately so that its host has some reasonable notion of the current time. One query per second is ridiculous, and is far from best practice for NTP client behavior.

This was a great read, thank you for posting!

I love articles like that.

Hijacking the highest ranking comment for an update from the blogger:

"UPDATE: RESOLVED

Patrik from Assetnote reached out to me with a very gracious message, it has been resolved. Thank you!"