It is not us.
Here is a partial traceroute to your location, leaving out your personal IP address.
1 L300.DLLSTX-VFTTP-58.verizon-gni.net (71.244.19.1) 0.992 ms 1.597 ms 0.868 ms
2 G0-5-0-5.DLLSTX-LCR-21.verizon-gni.net (130.81.58.28) 4.981 ms 2.988 ms 3.894 ms
3 ae3-0.DFW9-BB-RTR1.verizon-gni.net (130.81.199.58) 2.474 ms 2.556 ms 2.528 ms
4 0.so-7-0-0.XL3.LAX15.ALTER.NET (152.63.112.53) 31.974 ms 33.170 ms 33.159 ms
5 POS6-0-0.GW3.LAX15.ALTER.NET (152.63.112.105) 31.500 ms 31.547 ms 31.594 ms
6 internapGIGE-gw.customer.alter.net (157.130.236.110) 33.269 ms 33.326 ms 33.520 ms
7 border1.te3-1-bbnet1.lax012.pnap.net (216.52.255.37) 33.206 ms 33.557 ms 33.450 ms
8 acedc-5.border10.lax.pnap.net (63.251.209.206) 33.158 ms 33.231 ms *
9 cust-uscolo-1.bs01.lsan.acedc.net (69.27.173.10) 33.463 ms 33.121 ms 33.478 ms
10 204.9.202.230.uscolo.com (204.9.202.230) 33.867 ms 33.787 ms 33.687 ms
11 199.36.28.34 (199.36.28.34) 33.442 ms 32.138 ms 32.117 ms
12 120.28.0.77 (120.28.0.77) 166.422 ms 166.213 ms 166.304 ms
Take note of hop #8. There is packet loss occurring there. That is in the PNAP (Public Network Access Point) in Los Angeles. It is not uncommon for them to have problems, from time to time.
As I can only see the data going back to you, if you could post the trace from your location to 71.252.137.149, it would give us a complete picture.
I have already filed a bug report with the PNAP in Los Angeles, but we are not a direct customer, so it will not get priority attention.