users.tpg.com.au is down again for the past 5 days and tpg isnt in a hurry to fix it. this resolves to 188.8.131.52. not pinging at all. all my js, css, php files for ebay store gone with it ...
anyone experiencing this ? tried it from my work same problm, thx
I found the same thing on the 19th May and reported the problem including the ping test and a tracert results:
Pinging users.tpg.com.au [184.108.40.206] with 32 bytes of data:
Request timed out.
Tracing route to users.tpg.com.au [220.127.116.11]
over a maximum of 30 hops:
1 1 ms 12 ms 14 ms 192-168-1-1.tpgi.com.au [192.168.1.1]
2 14 ms 13 ms 13 ms 10.20.22-139.tpgi.com.au [10.20.22.139]
3 29 ms 29 ms 28 ms 203-219-155-130.tpgi.com.au [18.104.22.168]
4 26 ms 29 ms 30 ms syd-gls-har-crt2-be-10.tpgi.com.au [22.214.171.124]
5 35 ms 23 ms 28 ms syd-sot-ken-crt2-he-0-3-0-0.tpgi.com.au [126.96.36.199]
6 23 ms 24 ms 21 ms syd-sot-ken2-bras22-Te-0-1-0.tpgi.com.au [188.8.131.52]
7 * * * Request timed out.
8 * * * Request timed out.
To me it is a failure to connect to the next link after 184.108.40.206. (Simple?)
On Sunday and Monday I repeated the same information and even provided the above output.
Monday evening I received the following
Thank you for your email.
We understand that you're having an issue with your web mail. We will assist you accordingly regarding this issue.
Please be inform that there is an ongoing maintenance for our web servers.
Our Webmaster are already doing the repair. We will keep you posted once we have an update.
This, to me has NOTHING to do with the MAIL Server, its the system used for the users.tpg.com.au,
which happens to be [220.127.116.11]
Oh please get some engineers who listen to the complaint!
actually it works now .... thanks for all the replies ...
TPG - can you find the culprit once and for all pls.... cheers
Now that it works - the trace is this
2 10 ms 3 ms 11 ms 10.20.25.118 ---> 10-20-25-118.tpgi.com.au
3 1 ms 2 ms 2 ms 18.104.22.168 ---> 203.29.134-15.tpgi.com.au
4 2 ms 2 ms 2 ms 22.214.171.124 ---> users.tpgi.com.au
Welcome to TPG Community!
Thanks for confirming that this concern has now been sorted.
Based on the reports from our webmasters, the issue was attributed to a server hardware failure. Server data has been restored and is back in production.
Should you need further assistance, please let us know.