[CLIENT] Cannot download Spectator data / massive packet loss to spectator server
After noticing substantial (25-50%) "Request timed out" when pinging the spectator server 192.64.174.163 (as gleaned from the r3dlog.txt), I decided to run a traceroute on it, and every time get something similar to this:
12 24 ms () 27 ms 104.160.130.52 13 () () () Request timed out. 14 69 ms 49 ms 52 ms 104.160.159.0 15 () 59 ms 48 ms 104.160.128.101 16 58 ms () () 10.142.246.118 17 46 ms 51 ms () 192.64.174.163 18 () 51 ms 49 ms 192.64.174.163
In which db-ip.com states that pretty much all of the 104.160.XXX.XXX ranges are owned by Riot Games. It seems like some of the hops within that range are randomly timing out on me, and oddly enough, are not messed up for my friend next door (whom has the same ISP, in the same complex, on the same modem, configured the same way).
I hate to be "that guy" but having worked with severs before I can't help but think that some of the internal routes are jacked and that my account somehow screwed with this connection route? Dunno if it's the fault of my ISP route through the tier 2 network or if it's some internal voodoo with Riot server hops.
Similarly the r3dlog.txt shows a rather long spam of: 000001.642| 0.0000kb| 0.0000kb added| ALWAYS| Start processing App Update 000001.642| 0.0000kb| 0.0000kb added| ALWAYS| End processing App Update 000001.642| 0.0000kb| 0.0000kb added| ALWAYS| Sleeping
With a rather smoking gun of:
000031.246| 0.0000kb| 0.0000kb added| ERROR| Timeout while waiting for replay system to get game metadata from the cloud 000032.312| 0.0000kb| 0.0000kb added| ERROR| Failed to connect to 192.64.174.163 (192.64.174.163). Timeout duration (ms): 10000 000032.312| 0.0000kb| 0.0000kb added| ERROR| ReplayNetClient GetServerVersion error. Could not send HTTP request. Error: -2147467259 000032.313| 0.0000kb| 0.0000kb added| ERROR| Spectator server version retrieve Failure!!