Dropping 40%+ internet packets, Spartansburg PA. Not losing packets beyond gateway.

[TheXev1]

To start, this is not an isolated issue.  Others in Spartansburg PA are experiencing this issue after investigating, plus my friend in Spring Creak PA (a completely different service station) is experiencing this issue.  This is NOT an issue with my line due to ANY reason.

I am losing over 40% of my internet packets when pinging google.com for over ten mins!  I also tried yahoo.com, facebook.com... this isn't just one url I am loosing packets too!

To make sure this wasn't a line issue, I pinged my gateway address at the same time I was pinging those urls.. 0% packet lose!

My success rate for completing a Speakeasy speed test is also not 100% (It'd be one thing if the line was slow, its winter after all, but it’s another thing to loose packets entirely!)

I would like someone from Verizon to investigate this by running their own test.  This has been going on for over a week and it is a serious hindrance.  I have never had a Quality of Service issue like this with any other ISP.

Thank you for your time.

[dslr595148]

#1 Visit http://www.giganews.com/line_info.html and post up the Traceroute the page shows, if you wish. Be aware that the final hop (bottom-most line of the trace) will contain a hop with your IP address in it. Remove that line. What I'm looking for is a line that mentions "ERX" in it's name towards the end. If for some reason the trace does not complete (two lines full of Stars), keep the trace route intact.

#2 Can you provide the Transceiver Statistics from your modem?

If you don't know how to get that info:

a) What is the brand and model of your modem?

b) What is the brand and model of your router?

[TheXev1]

I cannot get the trancever status until I am onsite later today (modem is setup as bridge), but I can do the reverse trace routes right now via VNC.  Looks like neither tracert wants to complete.

news.giganews.com

1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms
2 xe-2-3-0.er1.iad10.us.above.net (209.66.64.189) 1 ms 0 ms 0 ms
3 xe-0-0-0.er2.iad10.us.above.net (64.125.26.234) 0 ms 0 ms 0 ms
4 above-uu.iad10.us.above.net (64.125.13.174) 0 ms 22 ms 2 ms
5 0.ae1.RES-BB-RTR2.verizon-gni.net (152.63.32.157) 3 ms 2 ms 1 ms
6 as0-0.PITT2-CORE-RTR1.verizon-gni.net (130.81.20.93) 7 ms 8 ms 6 ms
7 130.81.135.225 (130.81.135.225) 14 ms 15 ms 16 ms
8 * * *
9 * * *
10 * * *

news-europe.giganews.com

1 vl201.gw2.ams.giganews.com (216.196.110.2) 0 ms 0 ms 0 ms
2 208.174.49.145 (208.174.49.145) 0 ms 0 ms 0 ms
3 cr2-tengig-0-5-1-0.frankfurtft3.savvis.net (204.70.207.209) 10 ms 7 ms 7 ms
4 cr2-ten-0-8-0-0.NewYork.savvis.net (204.70.195.22) 88 ms 88 ms 88 ms
5 er2-tengig-3-1.NewYork.savvis.net (204.70.198.18) 94 ms 95 ms 94 ms
6 0.xe-9-2-0.BR2.NYC4.ALTER.NET (204.255.168.89) 81 ms 81 ms 115 ms
7 0.ae2.NY5030-BB-RTR2.verizon-gni.NET (152.63.18.74) 93 ms 82 ms 106 ms
8 as0-0.PITT2-CORE-RTR2.verizon-gni.net (130.81.20.95) 100 ms 93 ms 100 ms
9 130.81.135.227 (130.81.135.227) 98 ms 98 ms 107 ms
10 * * *
11 * * *
12 * * *

I decided to run a tracert on my end to google.com.  Here are the results:

Tracing route to google.com [74.125.113.105]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    31 ms    62 ms    45 ms  L100.ERIEPA-DSL-03.verizon-gni.net [74.106.188.1]
  3    37 ms   153 ms    88 ms  130.81.135.226
  4   126 ms   201 ms    65 ms  so-7-0-0-0.PITT2-CORE-RTR1.verizon-gni.net [130.81.18.254]
  5   179 ms    41 ms    41 ms  as2-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.20.92]
  6   137 ms   157 ms   159 ms  0.so-6-0-3.XL3.IAD8.ALTER.NET [152.63.32.133]
  7   117 ms    78 ms   160 ms  TenGigE0-4-0-1.GW7.IAD8.ALTER.NET [152.63.37.154]
  8   143 ms   101 ms    60 ms  google-gw.customer.alter.net [152.179.50.62]
  9     *        *        *     Request timed out.
 10     *      105 ms     *     209.85.243.114
 11   213 ms     *       53 ms  64.233.174.87
 12     *       58 ms     *     72.14.236.193
 13   140 ms     *        *     google.com [74.125.113.105]
 14   115 ms   145 ms     *     google.com [74.125.113.105]
 15    64 ms    54 ms    88 ms  google.com [74.125.113.105]

Trace complete.

Feel free to get as rough and tumble as you need to with me, I am a highly advanced user.  Will update with transever status in a few hours.  I am still lossing packets, but not as badly as when I ran my initial test.

[TheXev1]

Here we go. Took me awhile to get it.

Transceiver Statistics

Transceiver Revision 3.3.6.10.0.1 Vendor ID Code 4D54 Line Mode ADSL_2plus Data Path INTERLEAVED

Transceiver Information Down Stream Path Up Stream Path DSL Speed (Kbits/Sec) 7669 860 Margin (dB) 25.9 14.8 Line Attenuation (dB) 23.5 9.0 Transmit Power (dBm) 17.4 12.2

[TheXev1]

Okay, you can add Corry, PA to your list of sites with issues.  Another friend of mine there is experiancing the dropped packet issue as well.  That is 3 different service stations.  It'd be nice to get some real confirmation on this issue! 

This is outright terriable!  Service appears usable, but it could be perfect if this issue was addressed!

[smith6612]

Well, there's nothing wrong with your statistics or line as you've pointed out. The latency to the Verizon Edge router isn't very consistent, which leads me to believe there is congestion occurring somewhere between the DSLAM and that point but that would be a guess at this point. The routes being taken before the edge  router in the reverse traceroutes do not appear congested as the latency is steady and consistent, but we are also seeing a case of load balancing taking place as well, as each trace appears to go through a different router before reaching the edge router.

The problem appears to be localized to my eyes (as Corry, PA does not feed out of Pittsburgh but instead, Erie), but if it is more widespread, please share traceroutes from other users (if they haven't provided them elsewhere around here) that you mentioned to see if we can see any correlation to the routes/problems.

Also if you could, can you try pinging sites besides Google? Yahoo.com and Dslreports.com are good sites to try. In the traces to Google, packets seem to be getting lost past the Google/Verizon Border router.

[Casper0082]

I am also having the same issues as mentioned above.   This is coming from the subarbs of Philadelphia.  I noticed it start last Thursday.  Below are a couple ping/packet loss and traceroutes.   I gathered these pings when I noticed extreme lag.  7 second pings for multiple seconds is terrible.

PING google.com (74.125.115.147) 56(84) bytes of data.
64 bytes from google.com (74.125.115.147): icmp_req=3 ttl=53 time=27.8 ms
64 bytes from google.com (74.125.115.147): icmp_req=4 ttl=53 time=28.2 ms
64 bytes from google.com (74.125.115.147): icmp_req=6 ttl=53 time=27.5 ms
64 bytes from google.com (74.125.115.147): icmp_req=8 ttl=53 time=26.7 ms
64 bytes from google.com (74.125.115.147): icmp_req=9 ttl=53 time=28.2 ms
64 bytes from google.com (74.125.115.147): icmp_req=11 ttl=53 time=28.2 ms
64 bytes from google.com (74.125.115.147): icmp_req=12 ttl=53 time=26.7 ms
64 bytes from google.com (74.125.115.147): icmp_req=14 ttl=53 time=27.1 ms
64 bytes from google.com (74.125.115.147): icmp_req=15 ttl=53 time=189 ms
64 bytes from google.com (74.125.115.147): icmp_req=16 ttl=53 time=356 ms
64 bytes from google.com (74.125.115.147): icmp_req=17 ttl=53 time=533 ms
64 bytes from google.com (74.125.115.147): icmp_req=18 ttl=53 time=27.0 ms
64 bytes from google.com (74.125.115.147): icmp_req=20 ttl=53 time=27.6 ms
64 bytes from google.com (74.125.115.147): icmp_req=21 ttl=53 time=27.4 ms
64 bytes from google.com (74.125.115.147): icmp_req=22 ttl=53 time=28.0 ms
64 bytes from google.com (74.125.115.147): icmp_req=23 ttl=53 time=26.1 ms
64 bytes from google.com (74.125.115.147): icmp_req=24 ttl=53 time=27.7 ms
64 bytes from google.com (74.125.115.147): icmp_req=25 ttl=53 time=27.6 ms
64 bytes from google.com (74.125.115.147): icmp_req=26 ttl=53 time=27.4 ms
64 bytes from google.com (74.125.115.147): icmp_req=27 ttl=53 time=29.5 ms
64 bytes from google.com (74.125.115.147): icmp_req=28 ttl=53 time=27.5 ms
64 bytes from google.com (74.125.115.147): icmp_req=29 ttl=53 time=26.4 ms
64 bytes from google.com (74.125.115.147): icmp_req=32 ttl=53 time=28.3 ms
64 bytes from google.com (74.125.115.147): icmp_req=33 ttl=53 time=413 ms
64 bytes from google.com (74.125.115.147): icmp_req=34 ttl=53 time=916 ms
64 bytes from google.com (74.125.115.147): icmp_req=35 ttl=53 time=1395 ms
64 bytes from google.com (74.125.115.147): icmp_req=36 ttl=53 time=1747 ms
64 bytes from google.com (74.125.115.147): icmp_req=37 ttl=53 time=2238 ms
64 bytes from google.com (74.125.115.147): icmp_req=38 ttl=53 time=2751 ms
64 bytes from google.com (74.125.115.147): icmp_req=43 ttl=53 time=4245 ms
64 bytes from google.com (74.125.115.147): icmp_req=46 ttl=53 time=4268 ms
64 bytes from google.com (74.125.115.147): icmp_req=47 ttl=53 time=4429 ms
64 bytes from google.com (74.125.115.147): icmp_req=48 ttl=53 time=4700 ms
64 bytes from google.com (74.125.115.147): icmp_req=51 ttl=53 time=5095 ms
64 bytes from google.com (74.125.115.147): icmp_req=52 ttl=53 time=4896 ms
64 bytes from google.com (74.125.115.147): icmp_req=57 ttl=53 time=1609 ms
64 bytes from google.com (74.125.115.147): icmp_req=58 ttl=53 time=799 ms
64 bytes from google.com (74.125.115.147): icmp_req=59 ttl=53 time=107 ms
64 bytes from google.com (74.125.115.147): icmp_req=60 ttl=53 time=28.1 ms
64 bytes from google.com (74.125.115.147): icmp_req=61 ttl=53 time=26.5 ms
64 bytes from google.com (74.125.115.147): icmp_req=62 ttl=53 time=26.9 ms
64 bytes from google.com (74.125.115.147): icmp_req=63 ttl=53 time=28.4 ms
64 bytes from google.com (74.125.115.147): icmp_req=64 ttl=53 time=27.9 ms
64 bytes from google.com (74.125.115.147): icmp_req=66 ttl=53 time=26.7 ms
64 bytes from google.com (74.125.115.147): icmp_req=67 ttl=53 time=26.7 ms
64 bytes from google.com (74.125.115.147): icmp_req=68 ttl=53 time=26.9 ms
64 bytes from google.com (74.125.115.147): icmp_req=69 ttl=53 time=29.3 ms
^C
--- google.com ping statistics ---
69 packets transmitted, 47 received, 31% packet loss, time 68192ms
rtt min/avg/max/mdev = 26.162/882.890/5095.440/1554.459 ms, pipe 6

ING google.com (74.125.113.103) 56(84) bytes of data.
64 bytes from google.com (74.125.113.103): icmp_req=1 ttl=53 time=7021 ms
64 bytes from google.com (74.125.113.103): icmp_req=2 ttl=53 time=6912 ms
64 bytes from google.com (74.125.113.103): icmp_req=3 ttl=53 time=6896 ms
64 bytes from google.com (74.125.113.103): icmp_req=4 ttl=53 time=7168 ms
64 bytes from google.com (74.125.113.103): icmp_req=5 ttl=53 time=7361 ms
64 bytes from google.com (74.125.113.103): icmp_req=6 ttl=53 time=7417 ms
64 bytes from google.com (74.125.113.103): icmp_req=8 ttl=53 time=7675 ms
64 bytes from google.com (74.125.113.103): icmp_req=9 ttl=53 time=7710 ms
64 bytes from google.com (74.125.113.103): icmp_req=11 ttl=53 time=7770 ms
64 bytes from google.com (74.125.113.103): icmp_req=13 ttl=53 time=7719 ms
64 bytes from google.com (74.125.113.103): icmp_req=14 ttl=53 time=7231 ms
64 bytes from google.com (74.125.113.103): icmp_req=15 ttl=53 time=7125 ms
64 bytes from google.com (74.125.113.103): icmp_req=16 ttl=53 time=7196 ms
64 bytes from google.com (74.125.113.103): icmp_req=17 ttl=53 time=7283 ms
64 bytes from google.com (74.125.113.103): icmp_req=19 ttl=53 time=7354 ms
64 bytes from google.com (74.125.113.103): icmp_req=20 ttl=53 time=7326 ms
64 bytes from google.com (74.125.113.103): icmp_req=21 ttl=53 time=7616 ms
64 bytes from google.com (74.125.113.103): icmp_req=23 ttl=53 time=7763 ms
64 bytes from google.com (74.125.113.103): icmp_req=25 ttl=53 time=7518 ms
64 bytes from google.com (74.125.113.103): icmp_req=26 ttl=53 time=7334 ms
64 bytes from google.com (74.125.113.103): icmp_req=30 ttl=53 time=7050 ms
64 bytes from google.com (74.125.113.103): icmp_req=31 ttl=53 time=6918 ms
64 bytes from google.com (74.125.113.103): icmp_req=32 ttl=53 time=7035 ms
64 bytes from google.com (74.125.113.103): icmp_req=33 ttl=53 time=7126 ms
64 bytes from google.com (74.125.113.103): icmp_req=34 ttl=53 time=6854 ms
64 bytes from google.com (74.125.113.103): icmp_req=37 ttl=53 time=7040 ms
64 bytes from google.com (74.125.113.103): icmp_req=39 ttl=53 time=7181 ms
64 bytes from google.com (74.125.113.103): icmp_req=40 ttl=53 time=7110 ms
64 bytes from google.com (74.125.113.103): icmp_req=42 ttl=53 time=7335 ms
64 bytes from google.com (74.125.113.103): icmp_req=43 ttl=53 time=7245 ms
64 bytes from google.com (74.125.113.103): icmp_req=44 ttl=53 time=7233 ms
64 bytes from google.com (74.125.113.103): icmp_req=45 ttl=53 time=6867 ms
64 bytes from google.com (74.125.113.103): icmp_req=46 ttl=53 time=6568 ms
64 bytes from google.com (74.125.113.103): icmp_req=48 ttl=53 time=6853 ms
64 bytes from google.com (74.125.113.103): icmp_req=49 ttl=53 time=6941 ms
64 bytes from google.com (74.125.113.103): icmp_req=51 ttl=53 time=6217 ms
64 bytes from google.com (74.125.113.103): icmp_req=52 ttl=53 time=5076 ms
64 bytes from google.com (74.125.113.103): icmp_req=53 ttl=53 time=4089 ms
64 bytes from google.com (74.125.113.103): icmp_req=54 ttl=53 time=3090 ms
64 bytes from google.com (74.125.113.103): icmp_req=56 ttl=53 time=1116 ms
64 bytes from google.com (74.125.113.103): icmp_req=57 ttl=53 time=123 ms
64 bytes from google.com (74.125.113.103): icmp_req=58 ttl=53 time=27.2 ms
64 bytes from google.com (74.125.113.103): icmp_req=59 ttl=53 time=27.6 ms
64 bytes from google.com (74.125.113.103): icmp_req=60 ttl=53 time=26.7 ms
64 bytes from google.com (74.125.113.103): icmp_req=61 ttl=53 time=28.1 ms
64 bytes from google.com (74.125.113.103): icmp_req=62 ttl=53 time=27.8 ms
64 bytes from google.com (74.125.113.103): icmp_req=63 ttl=53 time=26.4 ms
64 bytes from google.com (74.125.113.103): icmp_req=64 ttl=53 time=28.7 ms
^C
--- google.com ping statistics ---
64 packets transmitted, 48 received, 25% packet loss, time 63422ms
rtt min/avg/max/mdev = 26.432/5680.762/7770.894/2781.887 ms, pipe 8

traceroute to google.com (74.125.115.147), 30 hops max, 60 byte packets
 1  * * *
 2  10.7.16.1 (10.7.16.1)  9.245 ms  10.587 ms  12.078 ms
 3  at (130.81.11.225)  13.893 ms  15.135 ms  16.356 ms
 4  so (130.81.20.138)  17.821 ms  19.309 ms  20.454 ms
 5  0.xe (152.63.3.69)  29.078 ms 0.xe (152.63.3.249)  30.880 ms 0.xe-3-0-2.XL4.IAD8.ALTER.NET (152.63.3.57)  31.131 ms
 6  TenGigE0 (152.63.32.198)  59.392 ms  50.667 ms TenGigE0 (152.63.37.98)  49.240 ms
 7  google (152.179.50.62)  82.575 ms  82.762 ms  81.635 ms
 8  72.14.238.214 (72.14.238.214)  26.059 ms 72.14.238.212 (72.14.238.212)  28.260 ms 216.239.46.248 (216.239.46.248)  28.090 ms
 9  209.85.243.114 (209.85.243.114)  60.433 ms  52.703 ms  51.837 ms
10  216.239.48.103 (216.239.48.103)  31.146 ms  26.518 ms 64.233.174.117 (64.233.174.117)  27.577 ms
11  209.85.242.177 (209.85.242.177)  36.145 ms * 209.85.242.181 (209.85.242.181)  33.298 ms
12  google.com (74.125.115.147)  30.762 ms  30.036 ms  28.894 ms