An Accepted Solution is available for this post.
Northern Virginia - FiOS Inconsistent (pathpings with packet loss identified and attached)
whysoserious1
Newbie
‎08-12-2012 11:35 AM

I just moved to a new address yesterday (in Falls Church VA) and FiOS was setup here. I noticed while using it that the internet usage felt inconsistent (I upgraded to the 75/35 plan) and the performance while playing Starcraft 2 was unplayable because there was so much lag. So, I did some troubleshooting.

First, I went to speedtest.net and ran tests on all three local servers. Here are the following results:

Reston Server 1:

image

 Reston Server 2:

 image

Ashburn Server:

image

As you can see, dramatically different results on three local servers. I used to get consistently 30/20 and up on all three at my old place. Definitely some kind of clumsiness going on somewhere locally for that to happen.

My next step was to pathping Starcraft 2's servers. I used the recommended pathping settings from battle.net and ran several tests since last night. Below are pathping reports with trouble spots highlighted in bold: Test 1 was from around 11pm EST Saturday night, Test 2 around 5am Sunday morning, Test 3 around 2pm Sunday.

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

TEST 1

Tracing route to 12.129.202.154 over a maximum of 30 hops

0 Ian-PC.home [192.168.1.2]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.WASHDC-VFTTP-126.verizon-gni.net [173.66.228.1]
3 G0-8-3-5.WASHDC-LCR-21.verizon-gni.net [130.81.49.42]
4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.151.230]
5 0.ae1.BR1.IAD8.ALTER.NET [152.63.32.141]
6 192.205.36.141
7 cr2.wswdc.ip.att.net [12.122.81.250]
8 cr1.cgcil.ip.att.net [12.122.18.21]
9 cr2.dvmco.ip.att.net [12.122.31.85]
10 cr1.slkut.ip.att.net [12.122.30.25]
11 cr2.la2ca.ip.att.net [12.122.30.30]
12 gar29.la2ca.ip.att.net [12.122.129.241]
13 12-122-254-238.attens.net [12.122.254.238]
14 mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
15 * * *
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Ian-PC.home [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% L100.WASHDC-VFTTP-126.verizon-gni.net [173.66.228.1]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% G0-8-3-5.WASHDC-LCR-21.verizon-gni.net [130.81.49.42]
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% so-12-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.151.230]
6/ 100 = 6% |
5 13ms 6/ 100 = 6% 0/ 100 = 0% 0.ae1.BR1.IAD8.ALTER.NET [152.63.32.141]
1/ 100 = 1% |
6 12ms 7/ 100 = 7% 0/ 100 = 0% 192.205.36.141
93/ 100 = 93% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr2.wswdc.ip.att.net [12.122.81.250]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.18.21]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-238.attens.net [12.122.254.238]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]

Trace complete.

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

TEST 2

 

Tracing route to 12.129.202.154 over a maximum of 30 hops

0 Ian-PC.home [192.168.1.2]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.WASHDC-VFTTP-126.verizon-gni.net [173.66.228.1]
3 G0-8-3-5.WASHDC-LCR-21.verizon-gni.net [130.81.49.42]
4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.151.230]
5 0.ae1.BR1.IAD8.ALTER.NET [152.63.32.141]
6 192.205.36.141
7 cr2.wswdc.ip.att.net [12.122.81.250]
8 cr1.cgcil.ip.att.net [12.122.18.21]
9 cr2.dvmco.ip.att.net [12.122.31.85]
10 cr1.slkut.ip.att.net [12.122.30.25]
11 cr2.la2ca.ip.att.net [12.122.30.30]
12 gar29.la2ca.ip.att.net [12.122.129.241]
13 12-122-254-238.attens.net [12.122.254.238]
14 mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
15 * * *
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Ian-PC.home [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 10ms 0/ 100 = 0% 0/ 100 = 0% L100.WASHDC-VFTTP-126.verizon-gni.net [173.66.228.1]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% G0-8-3-5.WASHDC-LCR-21.verizon-gni.net [130.81.49.42]
0/ 100 = 0% |
4 13ms 0/ 100 = 0% 0/ 100 = 0% so-12-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.151.230]
5/ 100 = 5% |
5 12ms 5/ 100 = 5% 0/ 100 = 0% 0.ae1.BR1.IAD8.ALTER.NET [152.63.32.141]
3/ 100 = 3% |
6 12ms 8/ 100 = 8% 0/ 100 = 0% 192.205.36.141
92/ 100 = 92% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr2.wswdc.ip.att.net [12.122.81.250]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.18.21]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-238.attens.net [12.122.254.238]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]

Trace complete.

  

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

TEST 3

Tracing route to 12.129.202.154 over a maximum of 30 hops

0 Ian-PC [192.168.1.2]
1 192.168.1.1
2 L100.WASHDC-VFTTP-126.verizon-gni.net [173.66.228.1]
3 G0-8-4-5.WASHDC-LCR-21.verizon-gni.net [130.81.105.14]
4 so-7-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.199.30]
5 0.ae1.BR1.IAD8.ALTER.NET [152.63.32.141]
6 192.205.36.141
7 cr2.wswdc.ip.att.net [12.122.81.250]
8 cr1.cgcil.ip.att.net [12.122.18.21]
9 cr2.dvmco.ip.att.net [12.122.31.85]
10 cr1.slkut.ip.att.net [12.122.30.25]
11 cr2.la2ca.ip.att.net [12.122.30.30]
12 * gar29.la2ca.ip.att.net [12.122.129.241]
13 12-122-254-234.attens.net [12.122.254.234]
14 mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
15 * * *
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Ian-PC [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% L100.WASHDC-VFTTP-126.verizon-gni.net [173.66.228.1]
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% G0-8-4-5.WASHDC-LCR-21.verizon-gni.net [130.81.105.14]
0/ 100 = 0% |
4 12ms 0/ 100 = 0% 0/ 100 = 0% so-7-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.199.30]
0/ 100 = 0% |
5 11ms 5/ 100 = 5% 5/ 100 = 5% 0.ae1.BR1.IAD8.ALTER.NET [152.63.32.141]
0/ 100 = 0% |
6 12ms 0/ 100 = 0% 0/ 100 = 0% 192.205.36.141
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr2.wswdc.ip.att.net [12.122.81.250]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.18.21]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-234.attens.net [12.122.254.234]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]

Trace complete.

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

The packet loss identified around some of the local Verizon servers (verizon-gni.net and alter.net are Verizon properties) is extreme. I believe that there is nothing I can do on my end to fix this, as everything locally seems to be behaving as it should, and the people who I have talked to on tech support are relatively clueless. 

I am paying a great deal of money for Verizon FiOS and should expect to be able to play a simple online game without absurd latency and be able to enjoy most of the internet without my download speeds being crippled.

0 Likes
Reply
12 Replies
An Accepted Solution is available for this post.
Re: Northern Virginia - FiOS Inconsistent (pathpings with packet loss identified and attached)
Hubrisnxs
Legend
‎08-12-2012 11:45 AM

you should probably do a smart who is look up and email the NOC that handles those routers. 

0 Likes
Reply
An Accepted Solution is available for this post.
Re: Northern Virginia - FiOS Inconsistent (pathpings with packet loss identified and attached)
whysoserious1
Newbie
‎08-12-2012 11:55 AM

Thank you, I'm looking up the NOC emails for all of them and sending the reports.

They are all Verizon owned, so hopefully this post will garner some attention somewhere as well.

0 Likes
Reply
An Accepted Solution is available for this post.
Re: Northern Virginia - FiOS Inconsistent (pathpings with packet loss identified and attached)
prisaz
Legend
‎08-12-2012 12:15 PM

Based on WinMTR the issues seem to be on att starting at LAX1, perhaps they are filtering ICMP, or there is a router issue at that point. Not at Verizon's side of the network. Issues start at ATT and their managed services. http://www0.attens.com/

http://whois.arin.net/rest/net/NET-12-129-202-128-1/pft

You may wish to see if you can adjust your number of connections with the software. It could be with your higher speeds, you are saturating there servers or router.

Or your router can not handle the number of connections at the newer speeds. What model and revision of Verizon router are you using?

But I did see a number of connection inconsistencies during my tests to that server location.

 |------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                        Edited for privacy

| 

|so-3-1-0-0.RES-BB-RTR2.verizon-gni.net -    0 |  246 |  246 |    2 |   15 |  221 |    4 |
|                0.ae2.BR1.IAD8.ALTER.NET -    0 |  246 |  246 |    7 |   14 |  111 |    9 |
|                          192.205.36.141 -    0 |  246 |  246 |    5 |   10 |   81 |    5 |
|                    cr2.wswdc.ip.att.net -    0 |  246 |  246 |   80 |   82 |  123 |   82 |
|                    cr1.cgcil.ip.att.net -    0 |  246 |  246 |   80 |   83 |  132 |   81 |
|                    cr2.dvmco.ip.att.net -    0 |  246 |  246 |   79 |   82 |  117 |   80 |
|                    cr1.slkut.ip.att.net -    0 |  246 |  246 |   80 |   83 |  154 |   81 |
|                    cr2.la2ca.ip.att.net -    0 |  246 |  246 |   80 |   82 |  115 |   82 |
|                  gar29.la2ca.ip.att.net -    0 |  246 |  246 |   77 |   95 |  344 |   79 |
|               12-122-254-238.attens.net -    0 |  246 |  246 |   77 |   84 |  264 |   78 |
|mdf001c7613r0003-gig-12-1.lax1.attens.net -    0 |  246 |  246 |   77 |   82 |  205 |   80 |
|                   No response from host -  100 |   49 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   49 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   49 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   49 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   49 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   49 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   49 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   49 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   49 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   49 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   49 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   49 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   49 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   49 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   49 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   49 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Looks to be a hosting issue with ATT and Attens.com or .net. All my test yielded intermittent results at ATT. At one of these two places. Mostly the second where pack loss occurred.

image

0 Likes
Reply
An Accepted Solution is available for this post.
Re: Northern Virginia - FiOS Inconsistent (pathpings with packet loss identified and attached)
whysoserious1
Newbie
‎08-12-2012 01:19 PM

I have the Actiontec MI424-WR Revision D. The computer running all the tests is hard wired to it. 

How would I go about liminting connections via software?

0 Likes
Reply
An Accepted Solution is available for this post.
Re: Northern Virginia - FiOS Inconsistent (pathpings with packet loss identified and attached)
prisaz
Legend
‎08-12-2012 01:45 PM
@whysoserious wrote:

I have the Actiontec MI424-WR Revision D. The computer running all the tests is hard wired to it. 

How would I go about liminting connections via software?

I would call tech support and tell them you are running into connection issues and your router keeps dropping out. I have a rev. D and they told me to dispose of it. I saved it as a back up, and it is sitting collecting dust.

If you tell them it is intermittant and keeps dropping your connection, based of the Revision they will most likely send a new one at no cost.

#1 the NAT table is limited to the number of connections due to memory and possibly other issues.

The answer is to get the Rev D. replaced. It will not perform well, and at the higher speeds you will most likely have bigger issues.

Setting or limiting the connections is a bandaid. If it is possible in your software.

Pier to Pier software such as games and file sharing ran into issues with Rev. D and below.

They sent a MI424-WR Revision E to replace my Revision D. Not the latest by today's standards, but better. It has been at least a year or more since mine was replaced. Probably two. You would probably receive even a newer router.

0 Likes
Reply
An Accepted Solution is available for this post.
Re: Northern Virginia - FiOS Inconsistent (pathpings with packet loss identified and attached)
cdubz
Newbie
‎08-14-2012 10:55 AM

I am having a very similar issue in Falls Church, VA. 

Check out my thread with no responses 😞

http://forums.verizon.com/t5/FiOS-Internet/DC-Falls-Church-SLOW-Speedtest-net-downloading-files-Veri...

0 Likes
Reply
An Accepted Solution is available for this post.
Re: Northern Virginia - FiOS Inconsistent (pathpings with packet loss identified and attached)
whysoserious1
Newbie
‎08-14-2012 05:02 PM

Okay, I got the MI424WR Rev I. It'll be good for in house wireless networking... once the actual WAN connection is working properly. Here is a winMTR test to the Starcraft2 server with the new upgraded router:

image

Lots of packet loss. I would like to know: can this is any way be a function of wiring in or directly outside my house? I would think no because the packetloss happens down the line AND speed test to Verizon's own speed tests are very high (short hop to them). 

The functional speed of my internet is terrible. Right now I am paying a great deal of money for a great test to Verizon's speed test. 

Thoughts?

0 Likes
Reply
An Accepted Solution is available for this post.
Re: Northern Virginia - FiOS Inconsistent (pathpings with packet loss identified and attached)
whysoserious1
Newbie
‎08-15-2012 01:16 AM

Alright, decided to run a ton of tests off peak hours in order to get some more results.

Tests are broken down into several varieties and will be broken up into three separate posts:

1) Speed tests from several places on the internet

2) Line quality tests from several places on the internet

3) winMTR results from several places 

Section 1: Speed Tests

1a. Speed test available at Verizon's Quantam promtional site: Quantam Test Site

image

1b. Speed test from another Verizon speed test at Verizon.net: Verizon.net/speedtest (Virginia server)

image

1c. Speed test from Speakeasy.net (Washington, DC server selected: http://www.speakeasy.net/speedtest/

image

1d. Speed test from DSL reports (Washington, DC server selected): http://www.dslreports.com/speedtest?flash=1

image

1e. Speed test from Speedtest.net (DC server): http://www.speedtest.net/

image

1f. Speed test from speedtest.net (Reston Server 1 - InfoRelay)

image

1g. Speed test from speedtest.net (Reston Server 2 - DigitalOne AG)

image

1h. Speed test from speedtest.net (Ashburn)

image

1i. Speed test from speedtest.net (Frederick, MD)

image

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

Thoughts:

  • Obviously, these results aren't great. The only "good" test was from Verizon.net. Now, I've had FiOS for about two years and at my previous house (I moved last weekend), I would get great tests across the board from these websites, so I don't think it's as simple as "the speed tests websites aren't reliable" as Verizon techs like to tell us. Furthermore, one of Verizon's own sites, the Quantam advertisting one, shows a ridiculously slow down speed.
  • My thought is that since the Verizon.net site shows an excellent connection (likely on a very short number of hop), the problem probably isn't something that I can fix or can be fixed immediately in/around my house
0 Likes
Reply
An Accepted Solution is available for this post.
Re: Northern Virginia - FiOS Inconsistent (pathpings with packet loss identified and attached)
whysoserious1
Newbie
‎08-15-2012 01:45 AM

Continuing my late night tests, from the previous post...

Section 2: Online Line Quality Tests

2a. Pingtest.net (Washington DC server): http://www.pingtest.net/

image

2b. Pingtest.net (Ashburn)

image

2c. Pingtest.net (Philly)

image

3d. Pingtest.net (Brooklyn NYC)

image

3e. Pingtest (Columbus)

image

3f. Pingtest (L.A.)

image

3f. Pingtest (Austin TX)

image

3g. FreeOokla Line Quality (unkown server(s) location): http://freeola.com/line-test/

image

3h. Linequality Xmissiom (unknown server(s) location): http://speedtest.xmission.com/

image

3i. Linequality Cloudshare (unknown server location): http://speedtest.cloudshare.com/

image

Thoughts:

  • Again, a great deal of inconsistency here. I ran the tests several time on each server to try and rule out really absurd results. 
  • I believe, based on these results, because there are some extroardinarily good ones, that the problem again, is NOT in/around my house. It is something on the greater network somewhere out there.
0 Likes
Reply