90ks, 10105, 2002, and lag...

90k = old router.

Quote:

---

Originally Posted by Train88

90k = old router.

---

lol... you know we are gonna fan the flames of the "no it can't be anything on my end because my internetz is good" crowd.... but there has been another round of botched firmware updates out there again. Not the Belkin Router thing again, but rather an ISP's modem update this time. There is a thread about it for Virgin Media customers. Might be something else for some people to investigate:

About 90002 / Disconnects (Virgin Media Customers)

uggh... their forums are loading like a dog atm...was trying to see if I could find the model number in play. Want to say it was a SuperHub Modem/Router combo or something like that. So, it could be affecting other ISP's as well--and since those updates get pushed with lease renewals it may have taken a while for them to kick in en-masse.

Googling for more info on any recent SuperHub problems, got some hits on an update that clamped down some firewall rules in March that wreaked havoc also. So, there may be something to this with other brands and not just the SuperHub's--if you have a modem/router combo you may want to double check your firewall options to see if something is going on there. If you have the option, disable the modem's router and try setting up a separate router, or if you are already using a split modem/router setup it might be worth trying a different "known good" router to see if things improve.

Traza a 199.91.189.38 sobre caminos de 30 saltos como máximo.

1 * * * Tiempo de espera agotado para esta solicitud.
2 * * * Tiempo de espera agotado para esta solicitud.
3 * * * Tiempo de espera agotado para esta solicitud.
4 * * * Tiempo de espera agotado para esta solicitud.
5 16 ms 15 ms 16 ms 141-166-89-200.fibertel.com.ar [200.89.166.141]

6 16 ms 15 ms 15 ms 130-165-89-200.fibertel.com.ar [200.89.165.130]

7 14 ms 15 ms 15 ms 222-165-89-200.fibertel.com.ar [200.89.165.222]

8 11 ms 11 ms 12 ms xe-7-1-2.ar3.eze1.gblx.net [159.63.53.213]
9 141 ms 143 ms 143 ms po3-20G.ar3.MIA2.gblx.net [67.17.75.66]
10 142 ms 143 ms 140 ms ae5.edge2.miami2.level3.net [4.68.111.121]
11 190 ms 190 ms 191 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

12 191 ms 195 ms 189 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

13 178 ms 179 ms 178 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
14 184 ms 178 ms 182 ms 192.34.76.10
15 190 ms 191 ms 191 ms 199.91.189.242
16 187 ms 191 ms 185 ms 199.91.189.38

Traza completa.


Just did this tracert 5 minutes ago, don't mind the 180 average ping, I can't help it by living in South America but still, is there something wrong with that? are the first 4 hops causing the problem? I called my ISP and they told me a higher tier of support will contact me soon, but still any help would be great.

yep this game has been unplayable between the hrs of 7pm-12amest after 12 there is never no lag.Ever since that patch after the 1st savage patch this shit has been happening and its annoying as hell cause thats the time my raid team normally raids and everytime its me and 2 other guys thats lag.This game has just gotten worse for me fun wise but after the hr of 12am this game is sooo smooth.

Ya started happening to me as soon as The Rising Event started i tried everything i know to fix it but to no luck

Quote:

---

Originally Posted by Raist

199.91.189.57 hasn't been a valid IP since late March when they changed up the IP assignments. Open Resource Monitor (resmon.exe from search/run box) once you are fully logged into the game. Expand the network sections and you will see the ffxiv.exe process (or ffxiv_dx11.exe if running in DX11 mode) listed with an IP address. That is the one your client is actually using.

Otherwise, it looks like there is heavy congestion within the segments manage by Level 3, your assigned peering partner (those gblx.net hops are actually Level3's). This is the result of the routing decisions made in order to get you from your ISP's network to Ormuco (SE's ISP). Those peering arrangements are made by your ISP, not SE. Your ISP will need to address that on your behalf.

Looks like half of Cablevision's routes peer with Level3 in Argentina, so they may have to work something out with Level3 about clearing the congestion. If they could flip you to their other main peer (TiSparkle, aka Telecom Italia), then it may get you paired with one of the other peers whom Ormuco also peers with (Cogent, TATA, or TiNet...forget if one of the others listed for them is also tied into Verizon as well).

The point is they don't HAVE to use Level3 exclusively to get you to Ormuco in Montreal. If they can't get things cleaned up on Level3 they SHOULD be able to route you through their alternate peer. The trick, as always, is getting someone working on it that can actually escalate things to a higher tier of support.

Try their online contact options. Hopefully you have an email contact or some other means of submitting your tracert reports. Get a sample trace to the correct IP address, as well as maybe some other services that are getting better results. If you can get a good report to something in North America, that might help draw a stark contrast for them and drive home the point that they need to take action. Here is a link to a Blizzard post about tracert testing that provides server addresses for their services...maybe you can use a trace to one of their games to provide a contrast against your FFXIV traces:

https://us.battle.net/support/en/art...g-a-traceroute

---

well I just talked to my ISP and they said that is not possible for them to mannually change the peer I'm connected to, this basically means I'm screwed, right?

Quote:

---

Originally Posted by Raist

How is it SE's responsibility to fix issues that are falling within the scope of our ISP's or even our own local networks? Vanicent's issue apparently involved local hardware....clearly not SE's responsibility to address.

---

I have to admit, that was something I'd considered from the start as a second-to-last resort. I was surprised that it worked, and it wasn't a fluke as I've used both Steam and Final Fantasy XIV at least twice each since, but glad as I know I can try it again if necessary.
Also, just for information, my router is one of the original Virgin Media "SuperHubs", which I'd never had a major problem with until this firmware update, but to be fair, it was solvable.

Accidently loaded the game without WTFast, did my duty roulette? People were rubber banding like crazy. Game was unplayable. Girlfriend has been complaining about it in the last couple of days.


Loaded wtfast immediately after the dungeon, no lag whatsoever.

Quote:

---

Originally Posted by DkDerek

Accidently loaded the game without WTFast, did my duty roulette? People were rubber banding like crazy. Game was unplayable. Girlfriend has been complaining about it in the last couple of days.


Loaded wtfast immediately after the dungeon, no lag whatsoever.

---

May I ask which server are you using in WTfast? I've tried most of them and it's still unplayable. Also your isp would be great.

I fixed my problem ended up being my firewall which got an update and decided to interfere with my ports so i turned off netguard on it and aloud it to use all ports and it was fixed and i'm aware many of you people have tired this just posting this here for other people to try. this was with Mcafee