Game Disconnections for the day 22 Jan 19

Technical Support
1 
traceroute to 119.74.101.182 (119.74.101.182), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.318 ms  0.275 ms  0.272 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


22/01/2019 15:10:46 UTC
--------------------

TRACEROUTE:
traceroute to 119.74.101.182 (119.74.101.182), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.538 ms  1.079 ms  1.089 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


22/01/2019 15:10:49 UTC
--------------------

MTR:
Start: Tue Jan 22 15:10:48 2019 Blizzard  1.|-- Blizzard    0.0%    10    0.3   0.2   0.2   0.3   0.0
  2.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


22/01/2019 15:10:48 UTC
--------------------

MTR:
Start: Tue Jan 22 15:10:51 2019 Blizzard  1.|-- Blizzard    0.0%    10    0.3   0.2   0.2   0.3   0.0
  2.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


22/01/2019 15:10:51 UTC
--------------------

Data obtained using Looking Glass.
This occurred when I try to play Overwatch.
Takes forever to connect to game, then disconnects within a minute or so.

pathping data:
Tracing route to 24.105.30.129 over a maximum of 30 hops

  0  COLIN-PC [10.0.0.8] 
  1  10.0.0.1 
  2  bb119-74-101-254.singnet.com.sg [119.74.101.254] 
  3  202.166.123.134 
  4  202.166.123.133 
  5  ae8-0.tp-cr03.singnet.com.sg [202.166.122.50] 
  6  ae4-0.tp-er03.singnet.com.sg [202.166.123.70] 
  7  203.208.191.113 
  8  203.208.158.126 
  9     *        *        *     
Computing statistics for 200 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           COLIN-PC [10.0.0.8] 
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  10.0.0.1 
                                0/ 100 =  0%   |
  2    1ms     0/ 100 =  0%     0/ 100 =  0%  bb119-74-101-254.singnet.com.sg [119.74.101.254] 
                                0/ 100 =  0%   |
  3    1ms     0/ 100 =  0%     0/ 100 =  0%  202.166.123.134 
                                0/ 100 =  0%   |
  4    2ms     0/ 100 =  0%     0/ 100 =  0%  202.166.123.133 
                                0/ 100 =  0%   |
  5    2ms     0/ 100 =  0%     0/ 100 =  0%  ae8-0.tp-cr03.singnet.com.sg [202.166.122.50] 
                                0/ 100 =  0%   |
  6    2ms     0/ 100 =  0%     0/ 100 =  0%  ae4-0.tp-er03.singnet.com.sg [202.166.123.70] 
                                0/ 100 =  0%   |
  7    6ms     0/ 100 =  0%     0/ 100 =  0%  203.208.191.113 
                               37/ 100 = 37%   |
  8  204ms    37/ 100 = 37%     0/ 100 =  0%  203.208.158.126 

Trace complete.
2

Looking glass is looking fine. Main concern would be the 37% loss and the jump from 6 ms to 204 ms going through Singtel:

  7    6ms     0/ 100 =  0%     0/ 100 =  0%  203.208.191.113 
                               37/ 100 = 37%   |
  8  204ms    37/ 100 = 37%     0/ 100 =  0%  203.208.158.126

We’ve been seeing some reports of issues in the area, usually with the M1 ISP though this may be related. Based on those results though, we would recommend contacting the ISP.

3

I have the same issue.spike lag please fix