What's causing FiOS users to get so much lag since 2.1?

This is my traceroute atm. Standing in RT I am seeing zero rubber banding. It will probably change later. Verizon FIOS Quantum. Buffalo NY.
http://img837.imageshack.us/img837/3581/7zd7.jpg

Quote:

---

Originally Posted by Whiz

maybe try switching service providers I hear time warner is decent. I signed a 2 yr with Fios so i'm screwed until next year if this issue isn't resolved.

---

Just ran this between NY and the FFXIV:ARR server using Time Warner:

1 ash1-pr1-xe-0-2-0-0.us.twtelecom.net (66.192.245.98) 36.439 ms 6.476 ms 6.450 ms
2 xe-8-0-0.edge2.Washington4.Level3.net (4.53.114.9) 6.380 ms 6.360 ms 6.380 ms
3 vlan60.csw1.Washington1.Level3.net (4.69.149.62) 31.778 ms vlan80.csw3.Washington1.Level3.net (4.69.149.190) 31.658 ms vlan70.csw2.Washington1.Level3.net (4.69.149.126) 31.762 ms
MPLS Label=1191 CoS=0 TTL=1 S=1
4 ae-72-72.ebr2.Washington1.Level3.net (4.69.134.149) 31.528 ms ae-62-62.ebr2.Washington1.Level3.net (4.69.134.145) 31.502 ms ae-92-92.ebr2.Washington1.Level3.net (4.69.134.157) 31.800 ms
MPLS Label=1756 CoS=0 TTL=1 S=1
5 4.69.201.94 (4.69.201.94) 31.683 ms ae-3-3.ebr1.NewYork2.Level3.net (4.69.132.90) 31.724 ms 4.69.201.86 (4.69.201.86) 44.695 ms
MPLS Label=1172 CoS=0 TTL=1 S=1
6 ae-1-100.ebr2.NewYork2.Level3.net (4.69.135.254) 32.862 ms 31.754 ms 31.767 ms
MPLS Label=1172 CoS=0 TTL=1 S=1
7 ae-45-45.ebr2.NewYork1.Level3.net (4.69.141.21) 31.539 ms 4.69.201.37 (4.69.201.37) 31.693 ms ae-47-47.ebr2.NewYork1.Level3.net (4.69.201.33) 31.365 ms
MPLS Label=1197 CoS=0 TTL=1 S=1
8 ae-5-5.car1.Montreal2.Level3.net (4.69.141.5) 31.546 ms 31.499 ms 31.476 ms
MPLS Label=713 CoS=0 TTL=1 S=1
9 ae-11-11.car2.Montreal2.Level3.net (4.69.141.1) 31.745 ms 31.805 ms 31.650 ms
10 ORMUCO-COMM.car2.Montreal2.Level3.net (4.59.178.74) 31.907 ms 46.733 ms 33.759 ms
11 192.34.76.10 (192.34.76.10) 50.813 ms 23.553 ms 23.541 ms

As you can see, TW is also routing through Level3 and the problematic router.

Quote:

---

Originally Posted by remidi

Everyone keeps pointing the finger at FIOS. I've been on the phone with them a couple times now with higher level support and they are being very insistent that they are not throttling the game at all. They are sending me a new modem that we hope will help as I just upgraded to quantum.

---

Wasn't really pointing the finger at FIOS. Other than this game I really have had no issues and actually love the service. I'm simply saying that there is an obvious connection with this issue and FIOS customers at the moment. As others have stated here, the issue seems to be with a route FIOS uses to get to the SE servers and it is with a router that is not theirs.

Just thought I would add, that I to am having problems. Northern VA area, using FIOS.

In another thread I saw people pointing to the issue starting after the data center ISP maintenance posted here:
http://na.finalfantasyxiv.com/lodest...bfbcaa77e593c1

FIOS user in MA. Also having the lag issues mentioned here. It is beyond frustrating.

FiOs user in CA. Huge issue for me as well.

Girlfriend is here in NJ with the same issue. I'm on comcast a few miles away and no problem.

People in my FC have started paying for a certain program to fix their ping thanks to this new error. It works, but seriously, must we do this? Why am I paying a different company to fix a problem that never needed to exist all of a sudden? Please say something, SE.

When posting tracerts it might be more useful to use a program called WinMTR. it will ping each hop in the route until you stop it. (I usually do 500 times minimum) which will show irregularities much better than a triple ping tracert.

Quote:

---

Originally Posted by Leet

When posting tracerts it might be more useful to use a program called WinMTR. it will ping each hop in the route until you stop it. (I usually do 500 times minimum) which will show irregularities much better than a triple ping tracert.

---

pathping does that. just replace tracert with pathping: pathping x.x.x.x
it reports lost packets from source to node and between nodes.