Community Forums - Re: Ping rates over 600 on long distant connection...

Just_tired · ‎11-24-2012

Hello All,

Here's the trouble, up to about a month ago now my DSL was running fine. Then I started getting pings over 300 on long distant connections only, now it has gone up to pings over 600. This is causing me in some cases to be logged off the sites. Dealing with the so called chat help is worthless, they have run around doing nothing and when I request a supervisor I'am ignored. The tickets they claim to have open on this I cannot even find. This needs to be resolved, I would hate to do it but if it keeps up I will find another provider. I know it's not my equipment, and the router has been reset and re-initilized, by me and by the so called help tech. Their solution from these brain dead people is I run with the ethernet cable going direct to the jack. Which does not fix the problem and removes my landline from service.

The router is a Actiontec GT784wnv. All line test show that on local connections my speed is fine, but on long distant connections the ping rates go up from 300 to over 600. This is consistant no matter what time of day or night, so not due to peck hours. I belive it is something within the local office that has me routed thou the slowest lines on the earth. Any help I can get on this would be much appreciated.

Oh router is working fine and is only a couple of months old, have tested with another and the results were the same. Have three computers hooked up (only use one at a time on line) all have Windows 7 as operating system, 2 are quid cores, 1 is older dual core, so know it is not the computer as results are the same no matter which one I use. I get the same results with the wireless as well.

smith6612 · ‎11-26-2012

Would you be able to supply us with some traceroutes to the hostnames or IPs of the hosts you're having problems with latency? 300ms sounds like a route to Australia and back. 600ms would be a route that is either of very poor quality or something that is going across the world twice.

Just_tired · ‎12-03-2012

Did traces and the results are as before the sites I get the highest pings are San Francisco (Second Life vitr. Reality world, may be classified as game) and sorry to say Microsoft in Redmen Washington state which I need a clean line for.

Trace routes do not get routed around the globe never leave USA.

So far Verizon Tech support seem to miss what I say each time and have caused my line to be down for 2 or 3 days. Each time they do something it does not fix the problem and then need local office to reset before I get my line back.

As it stands now I have been without service for a week, and still the problem is not fixed. Up until now the so called chat tech support kept saying its my phone line. I think I got them to understand this time that I could call Hong Cong and have a clear line, my phone is fine. The internet(DSL) is another matter. Their last fix actually made it worst now I get high ping right from the door and all the time I'm on, but just distant sites. So much for Verizon enhanched DSL line it don't work.

Just_tired · ‎12-04-2012

Well here's a good one told today they do not support the applications I'am using (Second Life, World of Warcraft, etc) so nothing can be done with my line. Keep in mind I asked this question when I signed up for verizon, which is why I selected the "Enhanced DSL". So the 15 mps I should get is now well unsupported, UNLESS ready for this I pay extra for a so called premium expert to work on my line. A line that was working fine for at least six months is now junk, which I must pay for each month and no longer meets my needs as stated by "verizon tech support" due to the applications I use are NOT supported. UNLESS of cause I pay them to fix what they broke, with a premium expert.

So anyone looking into verizon for use as a gaming platform run, do not walk away.... Second Life, Worlds of Warcraft, and many others are as stated to me by tech support "UNSUPPORTED and your line speeds will very" in other words pings well over 700. Which means LAG, LAG, LAG. So DO NOT believe the sales rep. who tells you "OH, Yes no problem you need enhanced DSL or Fios if in your area" there full of it. Your line will be good for 6 months then garbage with tech support telling you to bad we do not support that use of DSL.

UNLESS you are willing to pay for a *Choking on this* verizon premium tech support rep( in all likelihood also from India ) to work on your line at a very high rate.

verizon forgot one thing, they are no longer the only ISP and in some areas we are not stuck with them. So my bill is paid for this month, but I still control what money I take out of my wallet and who I give it to. We will see who gets paid next month, the full of it folk at verizon with poor service and even poorer tech support, or some other ISP that can meet my needs for internet access.

It appears from talking with others the same problem happens with Fios as well, they cannot or will not support your using the internet for full graphics gaming or high bandwidth use ( WHICH YOU ARE PAYING THEM FOR). So they will charge you but don't dare use what you pay for.

smith6612 · ‎12-04-2012

May i see an example traceroute of what is happening with the latency? We need to see where it is breaking down rather than bother phone and live chat all day. Here's some example traces from my own connection which hasn't given me a problem in 7 years for speed (minus occasional hiccups!). I'm in New York to put it on the record and it is currently peak hours.

To run a traceroute, open up a command prompt window and type in tracert , put in a space, and then fill in an IP address or a domain name as I've done. Then press Enter. The system will trace the path your data has to go to in order to send to the server. To copy/paste, right click on the Window, do Select All, and then press Enter to copy. Paste it into a post and remove any private info (mainly your username).

You can also a take a screenshot of the command prompt with the command in it after it has been run, and then attach it as a picture to your post.

First off...

Altair of Storms Realm, World of Warcraft, East Coast Battle.net server in New York City

Tracing route to 199.107.6.248 over a maximum of 30 hops

1    <1 ms    <1 ms    <1 ms 192.168.3.1
2     7 ms     6 ms     7 ms 10.41.15.1
3     7 ms     6 ms     6 ms P2-0.BFLONY-LCR-01.verizon-gni.net [130.81.44.232]
4    19 ms    19 ms    19 ms P11-0-0.BFLONY-LCR-02.verizon-gni.net [130.81.27.63]
5    19 ms    19 ms    19 ms so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.28.136]
6    19 ms    18 ms    18 ms so-2-3-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.19.86]
7    20 ms    19 ms    19 ms 0.ae1.BR2.NYC4.ALTER.NET [152.63.18.37]
8    19 ms    18 ms    19 ms 192.205.36.57
9    23 ms    23 ms    24 ms cr1.n54ny.ip.att.net [12.122.86.6]
10    58 ms    49 ms   109 ms gar1.nw2nj.ip.att.net [12.122.131.81]
11    21 ms    23 ms    22 ms 12.122.251.10
12    23 ms    22 ms    23 ms mdf001c7613r0004-gig-10-1.nyc3.attens.net [63.240.65.18]
13     *        *        *     Request timed out.
14 ^C

Aman'Thul Realm, World of Warcraft, West Coast Battle.net server in Los Angeles

Tracing route to 12.129.254.200 over a maximum of 30 hops

1    <1 ms    <1 ms    <1 ms 192.168.3.1
2     7 ms     6 ms     7 ms 10.41.15.1
3     7 ms     6 ms     6 ms P2-0.BFLONY-LCR-01.verizon-gni.net [130.81.44.22]
4    19 ms    19 ms    19 ms P11-0-0.BFLONY-LCR-02.verizon-gni.net [130.81.2.63]
5    19 ms    18 ms    19 ms so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.8.28.136]
6    18 ms    18 ms    18 ms so-2-3-0-0.NY325-BB-RTR1.verizon-gni.net [130.8.19.86]
7    19 ms    19 ms    19 ms 0.ae1.BR2.NYC4.ALTER.NET [152.63.18.37]
8    19 ms    19 ms    19 ms 192.205.36.57
9    90 ms    90 ms    90 ms cr1.n54ny.ip.att.net [12.122.86.6]
10   136 ms   134 ms   134 ms cr2.cgcil.ip.att.net [12.122.1.2]
11    90 ms    91 ms    91 ms cr1.cgcil.ip.att.net [12.122.2.53]
12    88 ms    92 ms    89 ms cr2.dvmco.ip.att.net [12.122.31.85]
13    91 ms    92 ms    91 ms cr1.slkut.ip.att.net [12.122.30.25]
14   136 ms   131 ms   136 ms cr2.la2ca.ip.att.net [12.122.30.30]
15   132 ms   130 ms   131 ms gar29.la2ca.ip.att.net [12.122.129.241]
16    90 ms    89 ms    89 ms 12.122.251.190
17   137 ms   110 ms    87 ms 206.16.68.46
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
20     *     ^C

To Los Angeles, California

Tracing route to lg.dreamhost.com [208.97.141.21]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.3.1
2     7 ms     6 ms     7 ms 10.41.15.1
3     6 ms     6 ms     7 ms P2-0.BFLONY-LCR-02.verizon-gni.net [130.81.44.234]
4    18 ms    18 ms    18 ms so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.28.136]
5    55 ms    29 ms    29 ms 0.xe-2-0-8.XT2.NYC4.ALTER.NET [152.63.6.253]
6    91 ms    92 ms    91 ms 0.xe-6-1-3.XL4.LAX15.ALTER.NET [152.63.10.162]
7    92 ms    94 ms    92 ms POS7-0-0.GW3.LAX15.ALTER.NET [152.63.112.109]
8    95 ms    95 ms    91 ms internapGIGE-gw.customer.alter.net [157.130.236.110]
9    88 ms    89 ms    89 ms border3.po1-20g-bbnet1.lax010.pnap.net [216.52.255.10]
10    93 ms    92 ms    91 ms dreamhost-1.border3.lax010.pnap.net [64.7.192.250]
11   128 ms    89 ms    88 ms gar-border-1.dreamhost.com [66.33.203.4]
12    89 ms    88 ms    88 ms gameserver.houkouonchi.jp [208.97.141.21]

Trace complete.

To Tampines, Singapore (routing through West Coast)

Tracing route to singtel.com.sg [203.127.23.18]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.3.1
2     7 ms     7 ms     6 ms 10.41.15.1
3     6 ms     6 ms     7 ms P1-0.BFLONY-LCR-01.verizon-gni.net [130.81.195.144]
4    16 ms    16 ms    16 ms so-6-3-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.28.138]
5    18 ms    17 ms    18 ms 0.xe-8-1-0.XL3.NYC1.ALTER.NET [152.63.5.213]
6     *        *       62 ms 0.xe-2-1-0.XT1.NYC4.ALTER.NET [152.63.18.58]
7    68 ms    61 ms    65 ms TenGigE0-6-2-0.GW8.NYC4.ALTER.NET [152.63.21.117]
8    59 ms    62 ms    84 ms tinet-gw.customer.alter.net [152.179.72.122]
9   101 ms   101 ms   101 ms xe-5-1-0.sjc10.ip4.tinet.net [89.149.185.161]
10    89 ms    88 ms    88 ms singtel-gw.ip4.tinet.net [216.221.157.158]
11   116 ms    88 ms    88 ms 203.208.152.109
12    99 ms   289 ms   271 ms 203.208.171.185
13   282 ms   269 ms   266 ms 203.208.153.125
14   284 ms   274 ms   282 ms 203.208.171.209
15   277 ms   284 ms   277 ms GE-0-3-0.tampines.singnet.com.sg [165.21.12.6]
16   298 ms   270 ms   291 ms 165.21.49.126
17   282 ms   294 ms   278 ms GE-0-3-0.tampines.singnet.com.sg [165.21.12.6]
18   292 ms   284 ms   281 ms 203.127.23.18

Trace complete.

To Dallas, Texas

Tracing route to softlayer.com [66.228.118.53]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.3.1
2     7 ms     6 ms     7 ms 10.41.15.1
3     7 ms     6 ms     7 ms P2-0.BFLONY-LCR-02.verizon-gni.net [130.81.44.23
4    18 ms    18 ms    18 ms so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.28.136]
5    31 ms    21 ms    89 ms 0.xe-2-0-8.XT2.NYC4.ALTER.NET [152.63.6.253]
6    21 ms    21 ms    20 ms 0.ae4.BR3.NYC4.ALTER.NET [152.63.16.185]
7    19 ms    18 ms    43 ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
8    19 ms    19 ms    19 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
9    20 ms    19 ms    19 ms ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
10    20 ms    21 ms    24 ms ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78]
11    19 ms    19 ms    18 ms ae-4-90.edge3.NewYork1.Level3.net [4.69.155.209]
12     *       63 ms    62 ms te2-5.bbr01.tl01.nyc01.networklayer.com [4.26.34.22]
13    45 ms    45 ms    45 ms ae1.bbr01.eq01.chi01.networklayer.com [173.192.18.132]
14    63 ms    63 ms    63 ms ae20.bbr01.eq01.dal03.networklayer.com [173.192.18.136]
15    64 ms    63 ms    64 ms ae0.dar01.sr01.dal01.networklayer.com [173.192.18.211]
16    66 ms    66 ms    66 ms po1.slr01.sr01.dal01.networklayer.com [66.228.118.138]
17    64 ms    63 ms    63 ms www.softlayer.com [66.228.118.53]

Trace complete.

To New York City, New York

Tracing route to b.resolvers.Level3.net [4.2.2.2]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.3.1
2     7 ms     7 ms     6 ms 10.41.15.1
3     6 ms     6 ms     6 ms P1-0.BFLONY-LCR-01.verizon-gni.net [130.81.195.144]
4    19 ms    19 ms    18 ms P11-0-0.BFLONY-LCR-02.verizon-gni.net [130.81.27.63]
5    19 ms    18 ms    19 ms so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.28.136]
6    19 ms    18 ms    18 ms so-2-3-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.19.86]
7     *       62 ms     *     0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41]
8    19 ms    18 ms    19 ms 0.ae3.BR3.NYC4.ALTER.NET [152.63.16.181]
9    19 ms    18 ms    18 ms 204.255.173.54
10    20 ms    21 ms    24 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
11    20 ms    19 ms    19 ms ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
12    20 ms    20 ms    20 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
13    21 ms    21 ms    21 ms ae-4-90.edge2.NewYork1.Level3.net [4.69.155.208]
14    21 ms    21 ms    21 ms b.resolvers.Level3.net [4.2.2.2]

Trace complete.

To Falkenstein, Germany

Tracing route to hetzner.de [213.133.107.227]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.3.1
2     6 ms     6 ms     6 ms 10.41.15.1
3     6 ms     7 ms     6 ms P1-0.BFLONY-LCR-02.verizon-gni.net [130.81.195.222]
4    19 ms    18 ms    18 ms so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.28.136]
5    19 ms    18 ms    18 ms 0.so-4-0-1.XT2.NYC4.ALTER.NET [152.63.10.29]
6    19 ms    19 ms    19 ms 0.xe-11-1-1.XL4.NYC1.ALTER.NET [152.63.10.101]
7    19 ms    19 ms    19 ms 0.xe-11-0-1.GW14.NYC1.ALTER.NET [152.63.20.181]
8    19 ms    19 ms    19 ms kpn-gw.customer.alter.net [157.130.249.230]
9   120 ms   117 ms   116 ms asd2-rou-1022.NL.eurorings.net [134.222.231.229]
10   112 ms   112 ms   112 ms dssd-s2-rou-1102.DE.eurorings.net [134.222.228.138]
11   112 ms   112 ms   112 ms ffm-s1-rou-1102.DE.eurorings.net [134.222.232.153]
12   114 ms   114 ms   114 ms nbg-s1-rou-1001.DE.eurorings.net [134.222.227.118]
13   116 ms   133 ms   116 ms kpn-gw.hetzner.de [134.222.107.21]
14   145 ms   126 ms   127 ms hos-bb2.juniper3.rz1.hetzner.de [213.239.240.145]
15   121 ms   121 ms   119 ms hos-tr2.ms-ex3k2.rz1.hetzner.de [213.239.192.83]
16   119 ms   118 ms   118 ms www.hetzner.de [213.133.107.227]

Trace complete.

To Chicago, Illinois

Tracing route to singlehop.com [184.154.60.210]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.3.1
2     7 ms     6 ms     7 ms 10.41.15.1
3     7 ms     6 ms     6 ms P1-0.BFLONY-LCR-01.verizon-gni.net [130.81.195.144]
4    19 ms    18 ms    19 ms P11-0-0.BFLONY-LCR-02.verizon-gni.net [130.81.27.63]
5    18 ms    19 ms    18 ms so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.28.136]
6    20 ms    24 ms    18 ms so-2-3-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.19.86]
7    20 ms    19 ms    19 ms 0.ae1.BR2.NYC4.ALTER.NET [152.63.18.37]
8    19 ms    18 ms    19 ms 204.255.168.26
9    19 ms    19 ms    19 ms xe-1-1-0.cr1.lga5.us.above.net [64.125.26.161]
10    43 ms    43 ms    52 ms xe-4-1-0.cr1.ord2.us.above.net [64.125.31.237]
11    43 ms    43 ms    75 ms xe-0-1-0.mpr1.ord6.us.above.net [64.125.22.125]
12    44 ms    82 ms    43 ms xe-0-1-0.mpr1.ord5.us.above.net [64.125.28.41]
13    51 ms    44 ms    44 ms 209.66.114.50.t00815-03.above.net [209.66.114.50]
14    43 ms    43 ms    44 ms asw-ds116.ord03.singlehop.net [173.236.77.98]
15    43 ms    43 ms    44 ms web05.singlehop.net [184.154.60.210]

Trace complete.

So like I said. Let's work this issue out here, rather than deal with the phone and chat support until we figure out what is broke and why. If it's specific sites, run some traces to those and to sites that are in the same general location that are not seeing issues. Maybe you're going across a bad circuit or hitting a peer that is having problems on a constant basis. We need to see the traces before we can help here for free. Verizon's service is great for playing games (avid PC gamer here, build my own machines when I'm not building servers) when it works. There's reasons why me along with a lot of co-workers swear by Verizon's FiOS service (and with me being the outcast DSL user 😛 ) rather than the cable company's DOCSIS service.

I also pay for only the Basic service (up to 1Mbps/384k) but I get the Enhanced speeds (5M/768k) for a few reasons. Basically, my line itself is running on some very unsupported modes on very old remote gear Verizon doesn't even support beyond 3M with a highly unsupported router configuration which I'm testing out. Basically, support will look at it funny and wonder what happened to it, and probably not bother supporting it. Here's my bandwidth usage for last month

So, with that in mind just tell us if you do need help or not. That's what the forum is here for! 🙂

Just_tired · ‎12-05-2012

Ok, here are the trace's: Note I stared out IP Numbers, will not post mine or anyone else as it is not needed, but starting IP was mine and trace IP was one of the problem sites.

First Trace to Problem site:

Tracing route to ****.****.com [***********]]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ***.***.*.*

2 27 ms 26 ms 26 ms 10.49.21.1

3 42 ms 44 ms 27 ms P0-3-0-7.NWRKNJ-LCR-22.verizon-gni.net [130.81.1

98.66]

4 58 ms 30 ms 29 ms ae0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.209.1

62]

5 33 ms 32 ms 30 ms xe-6-1-3-0.NY325-BB-RTR2.verizon-gni.net [130.81

.23.234]

6 35 ms 33 ms 41 ms 0.xe-9-1-0.BR1.NYC1.ALTER.NET [152.63.4.241]

7 34 ms 37 ms 34 ms pax-brdr-01.inet.qwest.net [63.235.40.53]

8 39 ms 37 ms 37 ms dca2-edge-01.inet.qwest.net [67.14.36.10]

9 45 ms 40 ms 42 ms 65.120.78.82

10 59 ms 40 ms 41 ms 72.21.220.149

11 43 ms 47 ms 45 ms 72.21.222.147

12 * * * Request timed out.

13 * * * Request timed out.

14 * * * Request timed out.

15 41 ms 40 ms 40 ms 216.182.224.81

16 * * * Request timed out.

17 * * * Request timed out.

18 40 ms 42 ms 41 ms ****.****.com [**.***.***.**]

Trace complete.

-----------------------------------------------------------------------------------------------------

Second trace using sign in to base server for In-world use:

Tracing route to sim2942.agni.**********.com [***.**.*.***]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ***.***.*.*

2 25 ms 25 ms 25 ms 10.49.21.1

3 29 ms 28 ms 27 ms P0-3-0-7.NWRKNJ-LCR-22.verizon-gni.net [130.81.1

98.66]

4 27 ms 29 ms 45 ms so-6-1-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.

199.16]

5 30 ms 29 ms 28 ms 130.81.23.228

6 30 ms 31 ms 30 ms 0.ae2.BR2.NYC4.ALTER.NET [152.63.1.205]

7 30 ms 30 ms 30 ms 204.255.168.26

8 51 ms 32 ms 37 ms xe-5-1-0.cr1.lga5.us.above.net [64.125.30.205]

9 35 ms 36 ms 36 ms xe-3-2-0.cr1.dca2.us.above.net [64.125.26.101]

10 96 ms 73 ms 72 ms xe-1-3-0.cr1.iah1.us.above.net [64.125.31.213]

11 72 ms 93 ms 72 ms xe-2-1-0.cr1.dfw2.us.above.net [64.125.30.58]

12 70 ms 78 ms 70 ms xe-0-0-0.cr2.dfw2.us.above.net [64.125.30.74]

13 72 ms 71 ms 72 ms xe-7-2-0.er2.dfw2.us.above.net [64.125.30.93]

14 71 ms 73 ms 72 ms 64.124.146.2.allocated.above.net [64.124.146.2]

15 73 ms 77 ms 73 ms sw-core0-71.dfw.*********.com [***.**.*.***]

16 70 ms 71 ms 72 ms sim2942.agni.********.com [***.**.*.***]

Trace complete.

Please note these traces will not show the problem of high pings which result after signing into a site and continued use. For that you would need to do a full trace of activity while signed on as the commucation routing can and will change during use (IE: normal commucation line switching that occurs during any session as the two computers connected over commucation lines continue to talk to each other).

So these traces are only useful if the problem occurs at time of sign on. These traces are same as a speed test on line they only show a small micro vision of the real world. To see the real trouble with a line one needs to run a full tarce over a period of time to see where and when possible blackbox switching occurs, or even line throtting happens.

Your own trace's shown in your post are not a true reflection of the line status during game play but only a simple trace run from point A to point B. As in any data commucation there are three main parts: (in between and with, maybe others, but only three main)

1. Sending computer

2. Commucation network line(s)

3. Recieving computer

With that said no matter what jerry rigged equipment sits in there as you stated in your post about something being rigged, in my case Number 1 and 3 have been ruled out. Which leaves number 2 verizon and without full trace the results here do not reflect the real problem that occurs. Which is high ping rates after log in and during use, which results in lag and even being signed out by host system. My line for six months ran fine with no troubles, only in the last month has this occured. From the comment made by a verizon tech support person I am lead to belive they are aware of issue and will not correct it unless I pay them a heavy fee. IE his comment to me that games like World of Warcraft and Second Life are not supported by DSL or Fieos with verizon.

Just_tired · ‎12-05-2012