dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
879
Tinger
join:2001-12-13
Red Wing, MN
·T-Mobile

Tinger

Member

[NV] Level3 interconnect issues in LV

I am getting drops and slow performance with Cox in Las Vegas.

Simple traceroute:

C:\Windows\system32>tracert 199.180.75.2

Tracing route to s6.phx.icastcenter.com [199.180.75.2]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms TM-AC1900-7DC8 [192.168.29.1]
2 * * * Request timed out.
3 6 ms 7 ms 8 ms 24-234-16-66.ptp.lvcm.net [24.234.16.66]
4 9 ms 8 ms 8 ms 24-234-6-28.ptp.lvcm.net [24.234.6.28]
5 21 ms 20 ms 20 ms dllsbbrj02-ge020.rd.dl.cox.net [68.1.0.149]
6 13 ms 12 ms 14 ms xe-9-0-2.edge2.LosAngeles9.Level3.net [4.53.230.
225]
7 31 ms 28 ms 28 ms ae-4-90.edge2.SanJose3.Level3.net [4.69.152.209]

8 * * * Request timed out.
9 28 ms 27 ms 30 ms tinet-level3-xe.sanjose3.level3.net [4.68.62.214
]
10 * * 41 ms xe-3-0-0.phx10.ip4.gtt.net [141.136.106.86]
11 39 ms 41 ms 39 ms icastcenter-gw.ip4.gtt.net [199.168.63.42]
12 33 ms * 34 ms 10ge-3-3.phx.as53767.net [162.251.162.38]
13 * 39 ms 39 ms s6.phx.icastcenter.com [199.180.75.2]

Trace complete.

Kind of points the Level3. Can this get looked into?

jon

Hard Harry7
join:2010-10-19
Narragansett, RI

Hard Harry7

Member

If its a issue inside Level3, I doubt there is very much Cox or anyone here can do to fix that. Try giving them a call?

Technical Support Center
Voice: 1-877-4LEVEL3 (1-877-453-8353)
whiteazn
join:2005-02-10
Henderson, NV

whiteazn to Tinger

Member

to Tinger
I was going to say the same thing

example pathping:

Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:
  0  KIMCHIZ [192.168.1.100] 
  1  192.168.1.1 
  2  10.75.128.1 
  3  24-234-8-58.ptp.lvcm.net [24.234.8.58] 
  4  24-234-6-28.ptp.lvcm.net [24.234.6.28] 
  5  dllsdsrc02-pos0901.rd.dl.cox.net [68.1.0.149] 
  6  xe-5-0-0.edge2.LosAngeles9.Level3.net [4.53.230.81] 
  7  ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98] 
  8  ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98] 
  9  192.205.37.145 
 10  cr1.la2ca.ip.att.net [12.122.128.102] 
 11  cr2.phmaz.ip.att.net [12.122.31.190] 
 12  12.123.158.129 
 13     *        *        *     
Computing statistics for 300 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           KIMCHIZ [192.168.1.100] 
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1 
                                0/ 100 =  0%   |
  2    8ms     0/ 100 =  0%     0/ 100 =  0%  10.75.128.1 
                                0/ 100 =  0%   |
  3    9ms     0/ 100 =  0%     0/ 100 =  0%  24-234-8-58.ptp.lvcm.net [24.234.8.58] 
                                0/ 100 =  0%   |
  4   10ms     0/ 100 =  0%     0/ 100 =  0%  24-234-6-28.ptp.lvcm.net [24.234.6.28] 
                                0/ 100 =  0%   |
  5   18ms     0/ 100 =  0%     0/ 100 =  0%  dllsdsrc02-pos0901.rd.dl.cox.net [68.1.0.149] 
                                0/ 100 =  0%   |
  6   23ms     0/ 100 =  0%     0/ 100 =  0%  xe-5-0-0.edge2.LosAngeles9.Level3.net [4.53.230.81] 
                               17/ 100 = 17%   |
  7   18ms    17/ 100 = 17%     0/ 100 =  0%  ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98] 
                                7/ 100 =  7%   |
  8   18ms    26/ 100 = 26%     2/ 100 =  2%  ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98] 
                                0/ 100 =  0%   |
  9   50ms    24/ 100 = 24%     0/ 100 =  0%  192.205.37.145 
                               76/ 100 = 76%   |
 10  ---     100/ 100 =100%     0/ 100 =  0%  cr1.la2ca.ip.att.net [12.122.128.102] 
                                0/ 100 =  0%   |
 11  ---     100/ 100 =100%     0/ 100 =  0%  cr2.phmaz.ip.att.net [12.122.31.190] 
                                0/ 100 =  0%   |
 12  ---     100/ 100 =100%     0/ 100 =  0%  12.123.158.129 
 
Trace complete.
 

And this has been going on for months now. Not sure this is something that Cox can fix though.

Whether it's a tracert, or pathping, I have always seemed to notice that Level3 @ LA has come up. Above example shows big issue at Tustin1 too though.