Dear AT&T,
Hello, my name is Nicholas and I am a resident of Malaysia. Over the past 3 and 1/2 weeks, the Malaysian community of the game, World of Warcraft - Which AT&T is the host provider for; have been experiencing severe lag on your IP range. We, the community are very sure that the IP range starting from 219.xxx.xxx.xxx are having problems. Ranges starting fro 218. and 60. have no problems. Our local ISP (riding on AT&T's internet backbone) say's that this is not their problem, as this is a issue with the AT&T network cloud.
We know we are not blocked as downloads are still alright. However, playing online games and web browsing is extremely slow (and unstable). We are seeing pings to US servers (Such as CNN or Microsoft) at 2000-6000ms on a T1 Broadband connection.
Below are tracert results. Could you please check into it and eMail me back ?
Please note this is my 3rd email to AT&T and my 5th eMail to TMNet (The local ISP on the AT&T Backbone).
Thank you very much.
Regards,
NicholasC.
Tracing route to us.logon.worldofwarcraft.com [12.129.232.115]
over a maximum of 30 hops:
1 14 ms 15 ms 14 ms 219.93.218.177
2 15 ms 15 ms 15 ms 219.93.216.109
3 15 ms 15 ms 15 ms 219.93.155.41
4 15 ms 15 ms 27 ms 210.187.132.83
5 15 ms 15 ms 15 ms 219.93.174.67
6 312 ms 312 ms 312 ms 219.93.153.158
7 1796 ms 1796 ms 1796 ms 12.118.44.5
8 1921 ms 1890 ms 1921 ms 12.123.8.50
9 1828 ms 1843 ms 1843 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
10 1921 ms 1968 ms 1968 ms tbr1-cl2.sffca.ip.att.net [12.122.10.42]
11 1843 ms 1863 ms 1867 ms gbr5-p100.sffca.ip.att.net [12.122.11.74]
12 1913 ms 1937 ms 1941 ms gar3-p360.sffca.ip.att.net [12.123.13.157]
13 1942 ms 1921 ms 1906 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255.254]
14 2030 ms 2031 ms 2031 ms mdf1-bi8k-2-eth-1-3.lax1.attens.net [12.129.192.110]
Tracing route to us.logon.worldofwarcraft.com [12.129.232.114]
over a maximum of 30 hops:
1 15 ms 14 ms 15 ms 219.93.218.177
2 46 ms 119 ms 17 ms 219.93.216.109
3 12 ms 13 ms 12 ms 219.93.155.33
4 14 ms 12 ms 13 ms 210.187.133.83
5 13 ms 12 ms 13 ms 219.93.174.83
6 306 ms 306 ms 307 ms 219.93.153.158
7 1639 ms 1499 ms 1561 ms 12.118.44.5
8 1668 ms 1387 ms 1702 ms 12.123.8.50
9 1781 ms 1375 ms * tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
10 984 ms 870 ms 833 ms tbr1-cl2.sffca.ip.att.net [12.122.10.42]
11 * * * Request timed out.
12 769 ms 770 ms 779 ms gar3-p360.sffca.ip.att.net [12.123.13.157]
13 * * * Request timed out.
14 4157 ms 620 ms 715 ms mdf1-bi8k-1-eth-2-2.lax1.attens.net [12.129.192.
122]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
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.
-----------------------------------
I made a topic report on the LYN's network forum:
Here.This post has been edited by Xeoalpha: Apr 4 2005, 01:24 PM