Due to the odd nature of this issue, one of our developers has asked us to post this on his behalf in order to clarify what is happening:
The network call in question is from a 3rd party library we use as part of our launching system. The call is intended to optimize the performance of a P2P feature of this library which we do not use and do not intend to use. Note that the call is to a public stun protocol server which is, in fact, hosted by the University of New Hampshire. A future update to our launcher will disable this completely.