Around the time that Renegades was released, I started to experience severe lag spikes while playing Destiny 2. I primarily participate in Crucible, but this lag was persistent in other areas of the game. My frame rate would frequently fluctuate between 120 to 20 frames per second. This makes PVP and several PVE events unplayable. I thought that this was related to the game release. I went through several tutorials optimizing the game video settings to no avail, along with optimization on Steam. I then ran a ping test to the destiny 2 servers and found issues. I contacted my internet provider and had a technician work on the internet. He concluded that this was a problem with the routing from my home to the Destiny 2 server. We pinged many other servers with little to no issues. I then set my windows DNS manually to Cloud Fare 1.1.1.1 because its known to be very fast. Despite changes to the DNS, I still have the same lag issues with Destiny 2. I am located in Indiana. When running standard Ping tests using meter.net, I get the below results (server set to Los Angeles CA). Over the past week, my Jitter can get as high as low 70s and my max ping in the 700s, average is mid-90s, and minimum is mid-40s. The max FPS occur every 5 seconds or so. Please note that I have 1G service from Mediacom and the technician found it functioning within normal parameters. Trace Route Test for 172.97.56.7 - 30 hops and failed at 11 through 30. • Tracing route to 172.97.56.7 over a maximum of 30 hops • 1 5ms 2ms 7ms XXXXXXX (hiding as its my IP) • 2 5ms 14ms 15ms 173-30-160-1.client.mchsi.com [173.30.160.1] • 3 13ms 14ms 15ms 172.30.92.105 • 4 26ms 23ms 24ms 10.16.88.56 • 5 29ms 23ms 24ms 68-66-73-70.client.mchsi.com [68.66.73.70] • 6 23ms 27m2 29ms po10.chgil001erl.mchs.com [68.66.73.122] • 7 * * * Request timed out. • 8 21ms 24ms 24ms ae5.mcrl.ord7.us.zip.zayo.com [64.125.25.42] • 9 44ms 24ms 23ms ae3.ter2.ord7.us.zip.zayo.com [64.125.19.95] • 10 * * 26ms 208.185.3.30.IDIA-385485-901-ZYO.zip.zzayo.com [208.185.3.30] • 11 * * * Request timed out. PING Test for 20.42.182.110 • Pinging 20.42.182.110 with 32 bytes of data: • Reply from 20.42.182.110: bytes=32 time=66ms TTL=106 • Reply from 20.42.182.110: bytes=32 time=64ms TTL=106 • Reply from 20.42.182.110: bytes=32 time=71ms TTL=106 • Reply from 20.42.182.110: bytes=32 time=67ms TTL=106 • Ping statistics for 20.42.182.110: • Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), • Approximate round trip times in milli-seconds: • Minimum = 64ms, Maximum = 71ms, Average = 67ms Trace Route Test for 20.42.182.110 - 19 Hops. • 1 4ms 7ms 2ms XXXXXXX (hiding as its my IP) • 2 17ms 14ms 14ms 173-30-160-1.client.mchsi.com [173.30.160.1] • 3 23ms 32ms 21ms 172.30.92.105 • 4 34ms 24ms 24ms 10.16.88.56 • 5 25ms 27ms 29ms 68-66-73-70.client.mchsi.com [68.66.73.70] • 6 24ms 24ms 138ms po10.chgil00ler1.mchsi.com [68.66.73.122] • 7 29ms 29ms 25ms be-69-0.ier03.chg.ntwk.msn.net [104.44.199.27] • 8 24ms 24ms * 51.10.32.103 • 9 * * * Request Timed out. • 10 * * * Request Timed out. • 11 * * * Request Timed out. • 12 * * * Request Timed out. • 13 71ms 72ms 64ms 51.10.40.9 • 14 71ms 70ms 71ms 51.10.6.170 • 15 * * * Request Timed out. • 16 * * * Request Timed out. • 17 * * * Request Timed out. • 18 * * * Request Timed out. • 19 66ms 64ms 63ms 20.42.182.110 • Trace Complete.