Reply
New Contributor
jltaser
Posts: 2

Re: Latency from southern California to anything north


TWC-KevinT wrote:

This issue has been escalated to our Network Operations Center for further review. Updates will be posted here as they are made available to us. We apologize for the inconvence. 


Thank you for the notice. I'll be looking forward to the updates and (hopefully) the resolution of this issue.

Please use plain text.
New Contributor
yujin
Posts: 2

Re: Excessive Latency - Tata Communications (Southern California)

has there been an update?  This throttling in paloalto was found several weeks ago; however, I was incredibly lucky and was not effected for some reason.  Starting about two weeks ago, I have been experiencing packet losses that sometimes last more than 10 seconds.  If I wait until maybe 2 am, the problem ceases and everything is back to normal.  When these packet losses occur, other programs (streaming, VOIP, digital phone, messenger programs, IE/FF/Chrome, everything imagineable) is ok.  Square Enix has admitted some companies are treating the game as P2P transmissions...

are different network providers pressuring/clarifying the activity?  I really rather use money to pay for faster time warner speeds than VPN/Tunneling services to get my connection to a practical point.

Please use plain text.
New Contributor
gbauchat
Posts: 4

Re: Excessive Latency - Tata Communications (Southern California)

Look at this tracer test and if look at line 13 this is unacceptable. I am paying for your best internet and I know for a fact that 1000's of people are experiencing the same issue. If this isn't fixed soon I will take my business somewhere else. This is effecting my work every night from 6pm-11pm I will go to fios or anyone else before I am unable to do my work because your servers are sending me to some crap ass node that has extremely high congestion. This needs to be fixed and I mean ASAP. I am reading thousands of complaints about this. I love this internet I get from you but if I can't do my job then I will find a internet company that can supply me with what I need.


Tracing route to 12.129.209.68 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 46 ms 28 ms 26 ms cpe-75-82-152-1.socal.res.rr.com [75.82.152.1]
3 11 ms 8 ms 9 ms tge7-1.hemtcazd01h.socal.rr.com [76.166.9.217]
4 15 ms 15 ms 15 ms tge0-12-0-0.ontrcacp01r.socal.rr.com [72.129.5.192]
5 16 ms 15 ms 15 ms agg21.lsancarc01r.socal.rr.com [72.129.5.0]
6 17 ms 23 ms 16 ms 107.14.19.32
7 13 ms 15 ms 15 ms 107.14.19.138
8 * 31 ms 28 ms ix-5-0-0-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.153]
9 31 ms 31 ms 32 ms if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1]
10 45 ms 44 ms 42 ms 66.110.59.42
11 42 ms 42 ms 47 ms cr1.la2ca.ip.att.net [12.122.82.246]
12 54 ms 44 ms 45 ms gar20.la2ca.ip.att.net [12.122.128.181]
13 187 ms 203 ms 394 ms 12-122-254-238.attens.net [12.122.254.238]
14 43 ms 43 ms 41 ms 206.16.68.46
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.

Please use plain text.
New Contributor
yujin
Posts: 2

Re: Excessive Latency - Tata Communications (Southern California)

ISPs need to get together and start pressuring or some kind of coalition needs to be formed for a better internet in the US.  People make fun of the internet infrastructure in the US...

Please use plain text.
New Contributor
gbauchat
Posts: 4

Re: Excessive Latency - Tata Communications (Southern California)

Went to my neighbors house that has Fios did same test he had zero issues so if its not fixed within the week I am going to just cancel my service. There going to loose thousands of customers from this crap.

Please use plain text.
New Contributor
gbauchat
Posts: 4

Re: Excessive Latency - Tata Communications (Southern California)

[ Edited ]

Was monitoring my ms last night went from 50-2160 over and over I got fed up and called FIOS and got 75/35 for 64.99 a month the exact price I am paying for 50mb here. I called a Tier 3 tech they admitted its congestion on peak times well FIOS you don't get that so I recommend every customer with this issue to leave maybe TWC will learn that taking your customers money means you have to offer a reliable service. Wife tried to watch a simple video last night on how to frost a specific cookie couldn't even stream the video. 

 

If you look at line 14 that is unacceptable 230ms meaning the **bleep** connection is being routed to a throttled server or node.

 

 1  75.125.232.57 (75.125.232.57)  0.820 ms  1.076 ms  0.545 ms
 2  te1-4.dsr02.hstntx2.networklayer.com (74.55.252.113)  0.594 ms  0.570 ms  0.581 ms
 3  ae17.bbr01.sr02.hou02.networklayer.com (173.192.18.234)  0.630 ms  0.657 ms  0.419 ms
 4  xe-9-3-0.bar2.Houston1.Level3.net (4.59.126.13)  0.594 ms  0.645 ms xe-9-3-0.bar1.Houston1.Level3.net (4.78.14.49)  0.901 ms
 5  ae-13-13.ebr1.Dallas1.Level3.net (4.69.137.138)  5.601 ms  5.581 ms  7.596 ms
 6  ae-91-91.csw4.Dallas1.Level3.net (4.69.151.161)  5.705 ms ae-81-81.csw3.Dallas1.Level3.net (4.69.151.149)  5.665 ms ae-13-13.ebr1.Dallas1.Level3.net (4.69.137.138)  5.578 ms
 7  ae-71-71.csw2.Dallas1.Level3.net (4.69.151.137)  5.525 ms ae-4-90.edge10.Dallas1.Level3.net (4.69.145.210)  5.431 ms ae-3-80.edge10.Dallas1.Level3.net (4.69.145.146)  5.665 ms
 8  ATT (4.68.62.230)  9.759 ms 4.69.145.82 (4.69.145.82)  5.593 ms ae-4-90.edge10.Dallas1.Level3.net (4.69.145.210)  5.319 ms
 9  ATT (4.68.62.230)  9.601 ms  9.027 ms  7.520 ms
10  cr2.dlstx.ip.att.net (12.123.16.110)  40.040 ms  42.208 ms cr2.la2ca.ip.att.net (12.122.28.178)  41.927 ms
11  gar29.la2ca.ip.att.net (12.122.129.241)  35.011 ms  34.872 ms cr2.la2ca.ip.att.net (12.122.28.178)  38.519 ms
12  12.122.251.190 (12.122.251.190)  35.651 ms  35.621 ms  35.408 ms
13  206.16.68.46 (206.16.68.46)  38.665 ms mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254)  38.610 ms mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250)  39.080 ms
14  * * mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250)  230.822 ms
15  * * *
16  * * *
17  *
Please use plain text.
New Member
jdbla
Posts: 1

Re: Excessive Latency - Tata Communications (Southern California)

I am having the same problem as everyone else.  I am in the Silver Lake area of Los Angeles and trying to download a movie from iTunes.   Here is the traceroute.  Note that the problem is with TATA Communications.  Their Seattle router in my case.  

 

NOTE that whereas the problem is with a TATA Communications.  The real problem is with Time Warner and their insistance on peering with a network that has a history of severe problems.  Time Warner chooses who they share trafffic with and they don't have to peer with TATA.  

 

Also, why has the TWC moderator for this forum failed to keep us updated as promised????

 

Here is the traceroute:

 

Traceroute has started…

 

traceroute to e3191.dscc.akamaiedge.net (2.19.141.15), 64 hops max, 72 byte packets

 1  cpe-172-251-96-1.socal.res.rr.com (172.251.96.1)  43.795 ms  29.586 ms  23.661 ms

 2  tge7-3.lsayca3302h.socal.rr.com (76.166.26.165)  12.952 ms  11.532 ms  50.082 ms

 3  tge0-9-0-3.lamrcadq02r.socal.rr.com (72.129.9.170)  34.018 ms  13.845 ms  17.038 ms

 4  agg28.tustcaft01r.socal.rr.com (72.129.9.2)  16.951 ms  15.596 ms  15.774 ms

 5  ae-5-0.cr0.lax30.tbone.rr.com (66.109.6.64)  15.617 ms  16.480 ms  15.797 ms

 6  107.14.19.67 (107.14.19.67)  31.522 ms  15.418 ms  44.292 ms

 7  ix-9-0-1-0.tcore2.lvw-losangeles.as6453.net (64.86.252.169)  30.167 ms  28.642 ms  34.095 ms

 8  if-2-2.tcore1.lvw-losangeles.as6453.net (66.110.59.1)  63.187 ms  71.837 ms  64.166 ms

 9  if-3-2.tcore1.pdi-paloalto.as6453.net (66.198.127.25)  66.989 ms  64.032 ms  83.796 ms

10  if-14-2.tcore1.00s-seattle.as6453.net (64.86.123.21)  1530.128 ms  1538.183 ms  1533.339 ms

11  64.86.123.66 (64.86.123.66)  66.893 ms *  65.198 ms

12  2.19.141.15 (2.19.141.15)  1475.297 ms  1511.330 ms  1592.099 ms

 

Please use plain text.
New Contributor
jm93065
Posts: 2

Re: Excessive Latency - Tata Communications (Southern California)

From the above posts, I can see that Tata is a problem for for many and has been for some time.  It's absolutely killing a critical vpn tunnel for me...  I am seeing rtt times of up to 1500ms between about 3pm PST and 10 - 11pm PST on hops to:

 

ix-9-0-1-0.tcore2.LVW-LosAngeles.as6453.net,64.86.252.169

 

if-2-2.tcore1.LVW-LosAngeles.as6453.net,66.110.59.1

 

if-3-2.tcore1.PDI-PaloAlto.as6453.net,66.198.127.25

 

Time Warner: What are you doing to work with (or around) Tata to resolve these issues?  Please share?

Please use plain text.
New Contributor
jm93065
Posts: 2

Re: Latency from southern California to anything north

[ Edited ]

Sorry.. thought I was replying to an individual post..not the main thread:  

 

My question was for the TWC Rep who reported on 11/11/13 that the issue had been escaleted to their NOC.  

 

Status please?

 

C:\>ping 66.198.127.25 -n 10

Pinging 66.198.127.25 with 32 bytes of data:

Reply from 66.198.127.25: bytes=32 time=486ms TTL=56
Reply from 66.198.127.25: bytes=32 time=514ms TTL=56
Reply from 66.198.127.25: bytes=32 time=520ms TTL=56
Reply from 66.198.127.25: bytes=32 time=434ms TTL=56
Reply from 66.198.127.25: bytes=32 time=430ms TTL=56
Reply from 66.198.127.25: bytes=32 time=477ms TTL=56
Reply from 66.198.127.25: bytes=32 time=474ms TTL=56
Reply from 66.198.127.25: bytes=32 time=451ms TTL=56
Reply from 66.198.127.25: bytes=32 time=420ms TTL=56
Reply from 66.198.127.25: bytes=32 time=441ms TTL=56

Ping statistics for 66.198.127.25:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 420ms, Maximum = 520ms, Average = 464ms

 

C:\>nslookup 66.198.127.25
Server: ipms-ROC-01-FAIL-02.it-net.carestreamhealth.com
Address: 10.127.252.89

Name: if-3-2.tcore1.PDI-PaloAlto.as6453.net
Address: 66.198.127.25

 

Please use plain text.
New Contributor
kcherdch
Posts: 2

Re: Excessive Latency - Tata Communications (Southern California)

[ Edited ]

Ok, these past 2 days, something is definitely up. I can't play a single game due to high latency.

 

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 2 ms 2 ms 2 ms 192.168.0.1
2 43 ms 12 ms 26 ms cpe-98-154-32-1.socal.res.rr.com [98.154.32.1]
3 16 ms 9 ms 12 ms tge0-7-0-1.breacayb02h.socal.rr.com [76.166.7.77]
4 12 ms 12 ms 15 ms agg11.cyprcabw02r.socal.rr.com [72.129.22.130]
5 15 ms 14 ms 15 ms agg27.tustcaft01r.socal.rr.com [72.129.21.2]
6 15 ms 15 ms 36 ms ae-6-0.cr0.lax30.tbone.rr.com [66.109.6.214]
7 15 ms 95 ms 14 ms 107.14.19.67
8 37 ms 32 ms 37 ms ix-9-2-0-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.173]
9 129 ms 122 ms 112 ms if-22-2.tcore2.PDI-PaloAlto.as6453.net [66.198.144.73]
10 963 ms 963 ms 973 ms if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.144.58]
11 123 ms 127 ms 125 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
12 108 ms 108 ms 108 ms 66.198.96.58
13 147 ms 112 ms 107 ms po22.cr1.mtl.iweb.com [184.107.1.1]
14 108 ms 108 ms 108 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
15 110 ms 107 ms 106 ms 72.55.128.44
16 110 ms 111 ms 107 ms 184.107.107.176

Trace complete.

 

 

Checking 960ms latency's IP address gives me this

 

66.198.144.58

This is a WHOIS cached copy dated: 2013-05-08 19:09:45 | Refresh

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#


#
# Query terms are ambiguous. The query is assumed to be:
# "n 66.198.144.58"
#
# Use "?" to get help.
#

#
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;q=66.198.144.58?showDetails=true&showARIN=false&ext=netref2
#

Tata Communications TATAC-ARIN-4 (NET-66-198-0-0-1) 66.198.0.0 - 66.198.191.255
Tata Communications,Ltd. PALO-PDI-TATAC (NET-66-198-144-0-1) 66.198.144.0 - 66.198.144.255

 

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#

 

I mean, really? 963ms? So Palo Alto at 129 is somewhat acceptable, but 963 at Chicago!? I'm seriously considering changing internet service if this doesn't get fixed with Tata.

 

EDIT: Now the ping to Chicago is at 1350ms.

Please use plain text.