[outages] Congestion between FiOS and ATT & TWCBC around LAX

[james machado]

This is what I am seeing via Cogent and AT&T from San Diego

Tracing the route to 98.119.130.224
VRF info: (vrf in name/id, vrf out name/id)
  1 38.122.146.105 [AS 174] 4 msec 4 msec 4 msec
  2 154.24.21.233 [AS 174] 4 msec 4 msec
    154.24.21.237 [AS 174] 3 msec
  3 154.24.41.177 [AS 174] 3 msec
    154.54.5.229 [AS 174] 4 msec 4 msec
  4 154.54.81.165 [AS 174] 3 msec
    154.54.81.117 [AS 174] 4 msec
    154.54.81.169 [AS 174] 4 msec
  5 154.54.88.9 [AS 174] 6 msec
    154.54.0.238 [AS 174] 4 msec
    154.54.7.185 [AS 174] 4 msec
  6 154.54.41.82 [AS 174] 5 msec
    154.54.41.58 [AS 174] 4 msec 5 msec
  7 154.54.13.86 [AS 174] 4 msec 34 msec 4 msec
  8 130.81.29.127 [AS 701] 10 msec
    130.81.209.255 [AS 701] 6 msec
    130.81.29.127 [AS 701] 10 msec
  9  *  *  *
 10 98.119.130.224 [AS 701] 9 msec 10 msec 9 msec


Tracing the route to 98.119.130.224
VRF info: (vrf in name/id, vrf out name/id)
  1 12.116.189.229 [AS 7018] 46 msec 5 msec 5 msec
  2 12.122.109.114 [AS 7018] [MPLS: Label 17000 Exp 1] 10 msec 12 msec 12 msec
  3 12.122.2.69 [AS 7018] [MPLS: Labels 0/17011 Exp 1] 9 msec 12 msec 8 msec
  4 12.122.129.233 [AS 7018] 9 msec 11 msec 11 msec
  5 192.205.35.162 [AS 7018] 79 msec 99 msec 79 msec
  6  *  *
    130.81.163.249 [AS 701] 75 msec
  7  *  *  *
  8 98.119.130.224 [AS 701] 104 msec 94 msec 78 msec

james


On Tue, Oct 6, 2015 at 5:07 PM, Mark Milhollan via Outages
<outages at outages.org> wrote:
> Anyone seeing congestion in the LAX area reaching Verizon (at least
> FiOS)?  I'm seeing packet loss and large RTT via AT&T (AS 7018) and Time
> Warner Business Class (AS 20001).  I only have pictures of the reverse
> paths but they are showing the same sort of losses and significant jumps
> in hop times as my test results (below).
>
> Sorry, I cannot share the destination used below for others to try.  It
> may be that 98.119.130.224 would also experience the same issue -- it is
> local so I can't quite test it the same way but from outside it usually
> experiences the issue, depending whether the hand-off to Verizon is in
> LAX or elsewhere.
>
> via ATT in LAX:
>
>   [traceroute]
>    4  cr2.la2ca.ip.att.net (12.123.132.210)  8.976 ms  6.307 ms  7.540 ms MPLS Label=17011 CoS=0 TTL=255 S=1
>    5  gar29.la2ca.ip.att.net (12.122.129.233)  8.172 ms  5.926 ms  7.707 ms
>    6  192.205.35.162 (192.205.35.162)  80.756 ms  81.333 ms  101.079 ms
>    7  * * *
>    8  [destination] (elided)  86.391 ms !<10> * *
>
>    [ping results]
>    20 packets transmitted, 15 received, 25% packet loss, time 19165ms
>    rtt min/avg/max/mdev = 83.599/85.562/88.746/1.262 ms, pipe 2
>
> via TWCBC in LAX:
>
>   [traceroute]
>    4  24.43.181.64 (24.43.181.64)  4.064 ms  4.144 ms  4.037 ms MPLS Label=19040 CoS=0 TTL=255 S=1
>    5  agg22.vnnycajz02r.socal.rr.com (72.129.14.168)  3.889 ms  6.123 ms  3.657 ms
>    6  agg29.tustcaft01r.socal.rr.com (72.129.13.2)  4.345 ms  5.874 ms  7.576 ms MPLS Label=16000 CoS=0 TTL=1 S=1
>    7  bu-ether16.tustca4200w-bcr00.tbone.rr.com (66.109.6.64)  5.721 ms  5.978 ms  7.489 ms
>    8  0.ae3.pr0.lax10.tbone.rr.com (66.109.9.26)  4.606 ms 0.ae1.pr0.lax10.tbone.rr.com (66.109.6.131)  5.574 ms 0.ae5.pr0.lax10.tbone.rr.com (107.14.19.121)  4.563 ms
>    9  TE-0-2-0-9.GW5.LAX15.ALTER.NET (152.179.21.133)  94.348 ms  94.830 ms  94.319 ms
>   10  * * *
>   11  [destination] (elided)   89.450 ms !<10>  85.759 ms !<10>  89.075 ms !<10>
>
>    [ping results]
>    20 packets transmitted, 18 received, 10% packet loss, time 19181ms
>    rtt min/avg/max/mdev = 84.401/86.186/89.484/1.313 ms, pipe 2
>
>
> /mark
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages