Hi.
I play some games on, and near servers in Singapore/Sri Lanka. A few weeks ago, my ping was a stable 140-150ms, which was acceptable. After a computer restart due to windows updates, I've been getting pings of over 230ms.
My other question is, why is my initial ping to my modem so high? It's a wired connections, and If I ping just my modem, it shows the normal >1ms. I tried trace routing to 8.8.8.8 which is a google DNS, and it showed similar ping as the trace route below.
Can anyone help explain why?
tracert 209.58.164.107
Tracing route to 209.58.164.107 over a maximum of 30 hops
1 17 ms 99 ms 99 ms BigPond.BigPond [10.0.0.138]
2 29 ms 29 ms 29 ms 172.18.212.13
3 29 ms 29 ms 29 ms 172.18.69.149
4 29 ms 29 ms 30 ms bundle-ether4.cha-edge901.brisbane.telstra.net [
203.50.44.40]
5 29 ms 29 ms 32 ms bundle-ether6.cha-core4.brisbane.telstra.net [20
3.50.11.140]
6 45 ms 44 ms 44 ms bundle-ether20.ken-core10.sydney.telstra.net [20
3.50.11.178]
7 45 ms 44 ms 42 ms bundle-ether1.oxf-gw10.sydney.telstra.net [203.5
0.6.97]
8 43 ms 43 ms 48 ms bundle-ether1.sydo-core04.sydney.reach.com [203.
50.13.94]
9 44 ms 57 ms 43 ms i-0-1-0-47.sydo-core03.bi.telstraglobal.net [202
.84.222.61]
10 205 ms 202 ms 203 ms unknown.telstraglobal.net [202.84.138.41]
11 236 ms 233 ms 231 ms unknown.telstraglobal.net [202.84.137.214]
12 231 ms 230 ms 231 ms i-0-2-0-8.istt-core02.bi.telstraglobal.net [202.
84.225.214]
13 237 ms 240 ms 235 ms unknown.telstraglobal.net [210.176.138.34]
14 234 ms 240 ms 235 ms te-0-0-2-0.cr02.sin-11.sg.leaseweb.net [103.254.
152.199]
15 231 ms 232 ms 235 ms et-50.ce01.sin-11.sg.leaseweb.net [103.254.152.2
01]
16 260 ms 259 ms 259 ms 209.58.176.65
17 258 ms 257 ms 256 ms 209.58.164.107
Trace complete.
Here's my trace route to that google server I mentioned:
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 53 ms 99 ms 99 ms BigPond.BigPond [10.0.0.138]
2 29 ms 29 ms 29 ms 172.18.212.13
3 29 ms 30 ms 29 ms 172.18.69.149
4 30 ms 29 ms 30 ms bundle-ether4.cha-edge901.brisbane.telstra.net [
203.50.44.40]
5 30 ms 29 ms 32 ms bundle-ether6.cha-core4.brisbane.telstra.net [20
3.50.11.140]
6 44 ms 43 ms 44 ms bundle-ether20.ken-core10.sydney.telstra.net [20
3.50.11.178]
7 42 ms 43 ms 42 ms bundle-ether1.ken-edge903.sydney.telstra.net [20
3.50.11.173]
8 41 ms 42 ms 41 ms 72.14.212.22
9 * * * Request timed out.
10 42 ms 43 ms 42 ms 74.125.37.154
11 43 ms 44 ms 44 ms 66.249.94.237
12 41 ms 42 ms 41 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
Was this helpful?
Thank you for your feedback
Thank you for your feedback
There was another thread a couple days ago with the same issue. Looks like there's a more recent incident here that's likely causing the issue:
http://status.vocus.com.au/view-incident.aspx?IncidentID=428
With direct debit there’s no need to give paying your bill another thought.
Avoid queuing up and never worry about late fees again.
Need a hand or want to share your expertise?
Register for CrowdSupport and get involved