For the past week-and-a-half have been getting persistent 'Beaver' networking issues that have resulted in either getting ported back to a spawn point or kicked out to the Director. During tonight's, attempted, session I pulled up resource monitor on the second screen to track the latency to the Destiny server(s) and noticed that some of the connections (there appeared to be four in total for the executable) were reaching the 600-700's. When I ran a Trace Route on two of the 'problem' connections, they both got timed out on the same hop: 64.125.28.111, which is hosted/controlled by Zayo(dot)com. For reference, I use Comcast, have a wired connection, do not normally have any background internet connections and have attempted local networking troubleshooting (I.e. flushed DNS cache, reset Gateway, et cetera). Any help would be appreciated.