Rather then clogging up the "So long Orcon" thread I'll post here. For the last couple of days WoW latency's been pretty abysmal with frequent disconnecting. Speedtests to L.A were extremely low, even early hours in the morning. I ran a tracert and a pathping to the Khaz'goroth server so if anyone can interpret it and offer advice would be appreciated *cough, sounddude*.

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>tracert 12.129.225.123

Tracing route to 12-129-225-123.attens.net [12.129.225.123]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    22 ms    21 ms    21 ms  lo1.erx2.nct.orcon.net.nz [60.234.8.18]
  3    19 ms    19 ms    55 ms  121.98.9.21
  4    20 ms    20 ms    19 ms  ae3.bdr2.nct.orcon.net.nz [121.98.9.146]
  5    21 ms    20 ms    19 ms  xe-1-1-0-401.bdr1.nct.orcon.net.nz [203.192.167.34]
  6    21 ms    20 ms    20 ms  Gi10-0-0-401.GW1.AKL1.asianetcom.net [203.192.167.33]
  7    21 ms    20 ms    20 ms  ge-0-0-0-0.gw1.akl2.asianetcom.net [203.192.185.45]
  8   145 ms   145 ms   145 ms  po1-1-0.gw3.lax1.asianetcom.net [203.192.185.62]
  9   146 ms   145 ms   145 ms  12.119.138.33
 10   146 ms   147 ms   147 ms  cr2.la2ca.ip.att.net [12.122.129.74]
 11   146 ms   145 ms   145 ms  gar4.la2ca.ip.att.net [12.122.129.169]
 12   147 ms   146 ms   145 ms  12.122.255.70
 13   146 ms   152 ms   146 ms  mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
 14     *        *        *     Request timed out.
 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.

C:\Documents and Settings\Administrator>pathping 12.129.255.123

Tracing route to 12.129.255.123 over a maximum of 30 hops

  0  ZEROALPHA [192.168.0.2]
  1  www.routerlogin.com [192.168.0.1]
  2  lo1.erx2.nct.orcon.net.nz [60.234.8.18]
  3  121.98.9.21
  4  ae3.bdr2.nct.orcon.net.nz [121.98.9.146]
  5  xe-1-1-0-401.bdr1.nct.orcon.net.nz [203.192.167.34]
  6  Gi10-0-0-401.GW1.AKL1.asianetcom.net [203.192.167.33]
  7  ge-0-0-0-0.gw1.akl2.asianetcom.net [203.192.185.45]
  8  po1-1-0.gw3.lax1.asianetcom.net [203.192.185.62]
  9  12.119.138.33
 10  cr1.la2ca.ip.att.net [12.122.128.78]
 11  gar4.la2ca.ip.att.net [12.122.128.169]
 12  12.122.255.70
 13  mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
 14  mdf1-bi8k-2-ve-70.lax1.attens.net [12.129.209.66]
 15     *     mdf1-bi8k-2-ve-70.lax1.attens.net [12.129.209.66]  reports: Destination host unreachable.

Computing statistics for 375 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           ZEROALPHA [192.168.0.2]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  www.routerlogin.com [192.168.0.1]

                                0/ 100 =  0%   |
  2   23ms     1/ 100 =  1%     1/ 100 =  1%  lo1.erx2.nct.orcon.net.nz [60.234.8.18]
                                0/ 100 =  0%   |
  3   19ms     0/ 100 =  0%     0/ 100 =  0%  121.98.9.21
                                0/ 100 =  0%   |
  4   21ms     0/ 100 =  0%     0/ 100 =  0%  ae3.bdr2.nct.orcon.net.nz [121.98.9.146]
                                0/ 100 =  0%   |
  5   24ms     0/ 100 =  0%     0/ 100 =  0%  xe-1-1-0-401.bdr1.nct.orcon.net.nz [203.192.167.34]
                                0/ 100 =  0%   |
  6   20ms     0/ 100 =  0%     0/ 100 =  0%  Gi10-0-0-401.GW1.AKL1.asianetcom.net [203.192.167.33]
                                0/ 100 =  0%   |
  7   21ms     0/ 100 =  0%     0/ 100 =  0%  ge-0-0-0-0.gw1.akl2.asianetcom.net [203.192.185.45]
                                0/ 100 =  0%   |
  8  145ms     0/ 100 =  0%     0/ 100 =  0%  po1-1-0.gw3.lax1.asianetcom.net [203.192.185.62]
                                0/ 100 =  0%   |
  9  145ms     0/ 100 =  0%     0/ 100 =  0%  12.119.138.33
                                0/ 100 =  0%   |
 10  ---     100/ 100 =100%   100/ 100 =100%  cr1.la2ca.ip.att.net [12.122.128.78]
                                0/ 100 =  0%   |
 11  ---     100/ 100 =100%   100/ 100 =100%  gar4.la2ca.ip.att.net [12.122.128.169]
                                0/ 100 =  0%   |
 12  ---     100/ 100 =100%   100/ 100 =100%  12.122.255.70
                                0/ 100 =  0%   |
 13  152ms     0/ 100 =  0%     0/ 100 =  0%  mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
                                0/ 100 =  0%   |
 14  147ms     0/ 100 =  0%     0/ 100 =  0%  mdf1-bi8k-2-ve-70.lax1.attens.net[12.129.209.66]
                              100/ 100 =100%   |
 15  ---     100/ 100 =100%     0/ 100 =  0%  ZEROALPHA [0.0.0.0]

Trace complete.

Pretty much any online game I play that has its servers located in California (which is probably all of them) I end up with terrible internet performance with warping, freezing and disconnections so its not really just with WoW.