dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
14
share rss forum feed

andyjai

join:2001-09-12
Rowland Heights, CA
reply to andyjai

Re: [Southwest] Problem with Fios

I did some googling and found that a few Los Angeles WoW players are having high ping issue. I don't play WoW, but i ran tracert and pathping to their server, and I think it is the same issue.

Tracing route to 12.129.209.68 over a maximum of 30 hops
 
  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     5 ms     4 ms     4 ms  L100.LSANCA-VFTTP-113.verizon-gni.net [98.119.77.1]
  3     9 ms     7 ms     8 ms  G0-5-1-5.LSANCA-LCR-21.verizon-gni.net [130.81.182.224]
  4     7 ms     7 ms     9 ms  so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
  5    42 ms     *       42 ms  0.xe-9-0-0.BR3.LAX15.ALTER.NET [152.63.114.245]
  6     *        *       38 ms  204.255.168.134
  7    10 ms    34 ms     *     cr1.la2ca.ip.att.net [12.123.132.129]
  8   106 ms    31 ms     *     gar29.la2ca.ip.att.net [12.122.129.241]
  9    41 ms     9 ms     *     12-122-254-234.attens.net [12.122.254.234]
 10     9 ms    10 ms     8 ms  mdf001c7613r0002.lax1.attens.net [206.16.68.54]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 
Tracing route to 12.129.209.68 over a maximum of 30 hops
 
  0  Win7-PC.home [192.168.1.168]
  1  Wireless_Broadband_Router.home [192.168.1.1]
  2  L100.LSANCA-VFTTP-113.verizon-gni.net [98.119.77.1]
  3  G0-5-1-5.LSANCA-LCR-21.verizon-gni.net [130.81.182.224]
  4  so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
  5  0.xe-9-0-0.BR3.LAX15.ALTER.NET [152.63.114.245]
  6     *     204.255.168.134
  7  cr2.la2ca.ip.att.net [12.123.30.134]
  8  gar29.la2ca.ip.att.net [12.122.129.241]
  9     *     12-122-254-234.attens.net [12.122.254.234]
 10  mdf001c7613r0002.lax1.attens.net [206.16.68.54]
 11     *        *        *
Computing statistics for 250 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Win7-PC.home [192.168.1.168]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  Wireless_Broadband_Router.home [192.168.1.1]
                                0/ 100 =  0%   |
  2    5ms     0/ 100 =  0%     0/ 100 =  0%  L100.LSANCA-VFTTP-113.verizon-gni.net [98.119.77.1]
                                0/ 100 =  0%   |
  3    8ms     0/ 100 =  0%     0/ 100 =  0%  G0-5-1-5.LSANCA-LCR-21.verizon-gni.net [130.81.182.224]
                                0/ 100 =  0%   |
  4   10ms     0/ 100 =  0%     0/ 100 =  0%  so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
                               14/ 100 = 14%   |
  5   22ms    14/ 100 = 14%     0/ 100 =  0%  0.xe-9-0-0.BR3.LAX15.ALTER.NET [152.63.114.245]
                               15/ 100 = 15%   |
  6   36ms    29/ 100 = 29%     0/ 100 =  0%  204.255.168.134
                               71/ 100 = 71%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  cr2.la2ca.ip.att.net [12.123.30.134]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%     0/ 100 =  0%  gar29.la2ca.ip.att.net [12.122.129.241]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%     0/ 100 =  0%  12-122-254-234.attens.net [12.122.254.234]
                                0/ 100 =  0%   |
 10  ---     100/ 100 =100%     0/ 100 =  0%  mdf001c7613r0002.lax1.attens.net [206.16.68.54]
 


Lloyd

@verizon.net
@VerizonSupport on Twitter mentioned last night that the ETA for the fix was 10:58 AM this morning. Things look a lot better now and I'm not seeing any significant packet loss on the sites that were having the problem last week.