the irony is that you will eventually accumulate more than a month's worth of free internet through reinbursement due to filing complaints and downtime.

welcome to Maxis btw.

Tracing route to 202.9.67.59 over a maximum of 30 hops

1 3 ms 3 ms 3 ms 192.168.1.254
2 15 ms 7 ms 8 ms 58.71.244.113
3 7 ms 5 ms 5 ms 58.71.244.114
4 7 ms 8 ms 7 ms 58.71.243.53
5 6 ms 8 ms 8 ms 58.71.243.49
6 8 ms 9 ms 7 ms 58.71.244.246
7 8 ms 9 ms 10 ms 58.71.241.21
8 * * * Request timed out.
9 25 ms 208 ms 207 ms 172.22.144.82
10 8 ms 7 ms 8 ms xe-0-1-0.r02.kslrml01.my.bb.gin.ntt.net [203.78.193.17]
11 110 ms 109 ms 110 ms ae-9.r23.osakjp02.jp.bb.gin.ntt.net [129.250.6.94]
12 154 ms 155 ms 156 ms ae-5.r31.tokyjp05.jp.bb.gin.ntt.net [129.250.7.80]
13 237 ms * 233 ms ae-10.r26.tokyjp05.jp.bb.gin.ntt.net [129.250.2.152]
14 154 ms * 146 ms p16-5-0-2.r26.tokyjp05.jp.ce.gin.ntt.net [61.120.145.146]
15 146 ms 142 ms 147 ms 203.118.15.186
16 140 ms 139 ms 141 ms an-ats-int11.starhub.net.sg [203.118.15.110]
17 147 ms 148 ms 153 ms 203.117.163.142
18 154 ms 152 ms 151 ms xe-1-1-0.gw401.sg1.ap.equinix.com [27.111.222.104]
19 151 ms 154 ms 170 ms xe-1-1-1.gw401.sg2.ap.equinix.com [27.111.222.107]
20 111 ms 114 ms 110 ms 202.79.216.154
21 108 ms 105 ms 107 ms 10.100.64.134
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

traceroute on my reply above, I would love to see if your maxis connection goes to Japan or not

thanks

and btw, maxis fibre still higher ping than streamy-x 512kbps



This post has been edited by h@ksam: Dec 21 2015, 01:47 PM

1. how long does the high ping persist? is it a daily affair?

2. what is the server IP?

nothing that I can see right now having the issues you mentioned.

maxis problems can be a more permanent feature and mostly happens at night during peak, definitely more than 10 minute sessions.

it might be the game server issue.

battlelog is my fav subject since the bulk of complaints initiated from here.

the average optimal ping for b-log SG server should be between 15-20+ give and take.

I'd say if you're getting 100+ms right now at 6pm it's time to fire up that customer hotline and open case ID for a rebate.

here's a traceroute on one of the battlefield servers as at 6:20pm

Tracing route to a4.d0.0cd8.ip4.static.sl-reverse.com [216.12.208.164]
over a maximum of 30 hops:

1 3 ms 3 ms 3 ms 192.168.1.254
2 16 ms 8 ms 6 ms 58.71.244.89
3 6 ms 6 ms 4 ms 58.71.244.114
4 19 ms 7 ms 6 ms 58.71.243.53
5 8 ms 6 ms 7 ms 58.71.243.49
6 9 ms * 8 ms 58.71.244.246
7 9 ms 8 ms 7 ms 58.71.241.21
8 * * * Request timed out.
9 21 ms 19 ms 19 ms se1-0-0.kchp-pe201.maxis.net.my [202.122.151.186]
10 18 ms 18 ms 16 ms 36351.sgw.equinix.com [202.79.197.69]
11 18 ms 18 ms 16 ms ae5.dar01.sr03.sng01.networklayer.com [50.97.18.197]
12 * * * Request timed out.
13 18 ms 17 ms 18 ms a4.d0.0cd8.ip4.static.sl-reverse.com [216.12.208.164]

Trace complete.

This post has been edited by h@ksam: Dec 23 2015, 06:24 PM