i decided to start levelling my Titan through Forsaken, and during the first mission i got a Moose error and decided to check my ping when the Moose error occured. Such as when stuff stopped moving and then when i finally got booted to Orbit. I'm trying to figure out a way to fix this if there is anyone from Bungie to assist me, I've been plagued by the bug since Beta and haven't been able to play regularly cause of it.
Pinging www.bungie.net [104.20.28.30] with 32 bytes of data:
Reply from 104.20.28.30: bytes=32 time=27ms TTL=54
Reply from 104.20.28.30: bytes=32 time=25ms TTL=54
Reply from 104.20.28.30: bytes=32 time=161ms TTL=54
Reply from 104.20.28.30: bytes=32 time=68ms TTL=54
Reply from 104.20.28.30: bytes=32 time=244ms TTL=54 -Entered Security Room with Cayde
Reply from 104.20.28.30: bytes=32 time=176ms TTL=54
Reply from 104.20.28.30: bytes=32 time=145ms TTL=54
Reply from 104.20.28.30: bytes=32 time=100ms TTL=54
Reply from 104.20.28.30: bytes=32 time=200ms TTL=54
Reply from 104.20.28.30: bytes=32 time=257ms TTL=54
Reply from 104.20.28.30: bytes=32 time=42ms TTL=54
Reply from 104.20.28.30: bytes=32 time=142ms TTL=54
Reply from 104.20.28.30: bytes=32 time=248ms TTL=54
Reply from 104.20.28.30: bytes=32 time=197ms TTL=54
Reply from 104.20.28.30: bytes=32 time=77ms TTL=54
Reply from 104.20.28.30: bytes=32 time=89ms TTL=54
Reply from 104.20.28.30: bytes=32 time=61ms TTL=54
Reply from 104.20.28.30: bytes=32 time=139ms TTL=54
Reply from 104.20.28.30: bytes=32 time=37ms TTL=54
Reply from 104.20.28.30: bytes=32 time=39ms TTL=54
Reply from 104.20.28.30: bytes=32 time=94ms TTL=54
Reply from 104.20.28.30: bytes=32 time=216ms TTL=54
Reply from 104.20.28.30: bytes=32 time=102ms TTL=54
Reply from 104.20.28.30: bytes=32 time=25ms TTL=54
Reply from 104.20.28.30: bytes=32 time=40ms TTL=54
Reply from 104.20.28.30: bytes=32 time=28ms TTL=54
Reply from 104.20.28.30: bytes=32 time=85ms TTL=54
Reply from 104.20.28.30: bytes=32 time=35ms TTL=54
Reply from 104.20.28.30: bytes=32 time=33ms TTL=54
Reply from 104.20.28.30: bytes=32 time=58ms TTL=54
Reply from 104.20.28.30: bytes=32 time=78ms TTL=54
Reply from 104.20.28.30: bytes=32 time=63ms TTL=54
Reply from 104.20.28.30: bytes=32 time=37ms TTL=54
Reply from 104.20.28.30: bytes=32 time=190ms TTL=54
Reply from 104.20.28.30: bytes=32 time=58ms TTL=54
Reply from 104.20.28.30: bytes=32 time=169ms TTL=54
Reply from 104.20.28.30: bytes=32 time=138ms TTL=54
Reply from 104.20.28.30: bytes=32 time=72ms TTL=54
Reply from 104.20.28.30: bytes=32 time=185ms TTL=54
Reply from 104.20.28.30: bytes=32 time=106ms TTL=54
Reply from 104.20.28.30: bytes=32 time=169ms TTL=54
Reply from 104.20.28.30: bytes=32 time=95ms TTL=54
Reply from 104.20.28.30: bytes=32 time=66ms TTL=54
Reply from 104.20.28.30: bytes=32 time=70ms TTL=54
Reply from 104.20.28.30: bytes=32 time=123ms TTL=54
Reply from 104.20.28.30: bytes=32 time=44ms TTL=54
Reply from 104.20.28.30: bytes=32 time=44ms TTL=54
Reply from 104.20.28.30: bytes=32 time=63ms TTL=54
Reply from 104.20.28.30: bytes=32 time=139ms TTL=54
Reply from 104.20.28.30: bytes=32 time=143ms TTL=54
Reply from 104.20.28.30: bytes=32 time=34ms TTL=54
Reply from 104.20.28.30: bytes=32 time=134ms TTL=54
Reply from 104.20.28.30: bytes=32 time=43ms TTL=54
Reply from 104.20.28.30: bytes=32 time=52ms TTL=54
Reply from 104.20.28.30: bytes=32 time=36ms TTL=54
Reply from 104.20.28.30: bytes=32 time=89ms TTL=54
Reply from 104.20.28.30: bytes=32 time=47ms TTL=54
Reply from 104.20.28.30: bytes=32 time=67ms TTL=54
Reply from 104.20.28.30: bytes=32 time=80ms TTL=54
Reply from 104.20.28.30: bytes=32 time=61ms TTL=54
Reply from 104.20.28.30: bytes=32 time=60ms TTL=54
Reply from 104.20.28.30: bytes=32 time=139ms TTL=54
Reply from 104.20.28.30: bytes=32 time=33ms TTL=54
Reply from 104.20.28.30: bytes=32 time=34ms TTL=54
Reply from 104.20.28.30: bytes=32 time=46ms TTL=54
Reply from 104.20.28.30: bytes=32 time=173ms TTL=54
Reply from 104.20.28.30: bytes=32 time=25ms TTL=54
Reply from 104.20.28.30: bytes=32 time=31ms TTL=54
Reply from 104.20.28.30: bytes=32 time=189ms TTL=54
Reply from 104.20.28.30: bytes=32 time=28ms TTL=54
Reply from 104.20.28.30: bytes=32 time=81ms TTL=54
Reply from 104.20.28.30: bytes=32 time=49ms TTL=54
Reply from 104.20.28.30: bytes=32 time=161ms TTL=54
Reply from 104.20.28.30: bytes=32 time=198ms TTL=54
Reply from 104.20.28.30: bytes=32 time=100ms TTL=54
Reply from 104.20.28.30: bytes=32 time=158ms TTL=54
Reply from 104.20.28.30: bytes=32 time=37ms TTL=54
Reply from 104.20.28.30: bytes=32 time=106ms TTL=54
Reply from 104.20.28.30: bytes=32 time=236ms TTL=54 -3 things are supposed to lift for me to kill Hive, nothing happens and Moose error begins
Reply from 104.20.28.30: bytes=32 time=46ms TTL=54
Reply from 104.20.28.30: bytes=32 time=139ms TTL=54
Reply from 104.20.28.30: bytes=32 time=222ms TTL=54
Reply from 104.20.28.30: bytes=32 time=195ms TTL=54
Reply from 104.20.28.30: bytes=32 time=199ms TTL=54
Reply from 104.20.28.30: bytes=32 time=101ms TTL=54
Reply from 104.20.28.30: bytes=32 time=27ms TTL=54
Reply from 104.20.28.30: bytes=32 time=28ms TTL=54
Reply from 104.20.28.30: bytes=32 time=31ms TTL=54
Reply from 104.20.28.30: bytes=32 time=29ms TTL=54
Reply from 104.20.28.30: bytes=32 time=26ms TTL=54
Reply from 104.20.28.30: bytes=32 time=28ms TTL=54
Reply from 104.20.28.30: bytes=32 time=26ms TTL=54
Reply from 104.20.28.30: bytes=32 time=30ms TTL=54
Reply from 104.20.28.30: bytes=32 time=28ms TTL=54
Reply from 104.20.28.30: bytes=32 time=24ms TTL=54
Reply from 104.20.28.30: bytes=32 time=27ms TTL=54
Reply from 104.20.28.30: bytes=32 time=24ms TTL=54
Reply from 104.20.28.30: bytes=32 time=36ms TTL=54
Reply from 104.20.28.30: bytes=32 time=27ms TTL=54
Reply from 104.20.28.30: bytes=32 time=24ms TTL=54
Reply from 104.20.28.30: bytes=32 time=158ms TTL=54
Reply from 104.20.28.30: bytes=32 time=136ms TTL=54
Reply from 104.20.28.30: bytes=32 time=132ms TTL=54
Reply from 104.20.28.30: bytes=32 time=94ms TTL=54
Reply from 104.20.28.30: bytes=32 time=78ms TTL=54
Reply from 104.20.28.30: bytes=32 time=78ms TTL=54
Reply from 104.20.28.30: bytes=32 time=371ms TTL=54 - Booted to Orbit
Reply from 104.20.28.30: bytes=32 time=96ms TTL=54
Reply from 104.20.28.30: bytes=32 time=142ms TTL=54
Reply from 104.20.28.30: bytes=32 time=91ms TTL=54
Reply from 104.20.28.30: bytes=32 time=230ms TTL=54
Reply from 104.20.28.30: bytes=32 time=226ms TTL=54
Reply from 104.20.28.30: bytes=32 time=117ms TTL=54
Reply from 104.20.28.30: bytes=32 time=294ms TTL=54
Reply from 104.20.28.30: bytes=32 time=77ms TTL=54
Reply from 104.20.28.30: bytes=32 time=311ms TTL=54
Reply from 104.20.28.30: bytes=32 time=29ms TTL=54
Reply from 104.20.28.30: bytes=32 time=34ms TTL=54
Reply from 104.20.28.30: bytes=32 time=28ms TTL=54
Reply from 104.20.28.30: bytes=32 time=36ms TTL=54
Reply from 104.20.28.30: bytes=32 time=27ms TTL=54
Reply from 104.20.28.30: bytes=32 time=27ms TTL=54
Reply from 104.20.28.30: bytes=32 time=31ms TTL=54
Reply from 104.20.28.30: bytes=32 time=29ms TTL=54
Ping statistics for 104.20.28.30:
Packets: Sent = 200, Received = 200, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 371ms, Average = 72ms
-
Hey there, Appreciate you reaching out to us with this issue. Are you still currently still being impacted by this error?