Error 90000 & lag

[VoltaAsura]

[QUOTE=Raist;2539026] [QUOTE]

We perhaps they could do something...years from now. Anything an ISP or *the powers that be* could take a long time to accomplish. I choose to use a GPN because it gives me what I want NOW. If I want a better connection without lag, I will use a GPN for XIV. I do not boot up FFXIV otherwise.

I do not dispute anything you have posted in this thread.

I thought they were in Toronto? Either way, that's the Canadian server that I connect to via WTFast, and it's smooth for me. Close enough?

[Raist]

yeah... the long term solution is to upgrade the exchanges, but in the short term they CAN re-route you through alternate routing partner (or at the very least a different one of their gateways, which may also put you with a different routing partner).

Time Warner has been doing these very things for me for a long time now. Been running through Hilton Head's gateway (about 100 miles away) instead of Florence's gateway for several months. Jacked up the latency for my first few hops, but by changing that one routing point, it shoots me through different corridors and bypassing nearly all the heavy lag spikes from the congested nodes around here (at times up to 3 seconds...even the Rokus would throw up on themselves). It's when I get handed off to their routing partner that is causing the issues now... which we get changed up every couple of weeks as the congestion creeps up.

Was running via TATA the other night... and now I'm running on Cogent again.... OMG, I sooo want to get in game right now. When I first get on Cogent, I get some amazing response times...

Tracing route to 199.91.189.30 over a maximum of 30 hops

  1     2 ms     1 ms    <1 ms  LPTSRV [10.10.100.1]
  2    39 ms    28 ms    27 ms  cpe-066-026-112-001.sc.res.rr.com [66.26.112.1]
  3    24 ms    19 ms    42 ms  cpe-024-031-198-009.sc.res.rr.com [24.31.198.9]
  4    19 ms    19 ms    20 ms  24.31.196.212
  5    31 ms    27 ms    26 ms  be33.chrcnctr01r.southeast.rr.com [24.93.64.182]
  6    35 ms    38 ms    36 ms  bu-ether34.atlngamq46w-bcr00.tbone.rr.com [107.14.19.48]
  7    36 ms    35 ms    37 ms  ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
  8    35 ms    36 ms    39 ms  te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
  9    37 ms    36 ms    38 ms  be2050.ccr41.atl01.atlas.cogentco.com [154.54.0.165]
 10    36 ms    35 ms    38 ms  be2168.ccr21.dca01.atlas.cogentco.com [154.54.31.94]
 11    41 ms    43 ms    44 ms  be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31.118]
 12    46 ms    45 ms    45 ms  be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.50]
 13    49 ms    49 ms    51 ms  be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
 14    72 ms    73 ms    73 ms  38.122.42.34
 15    50 ms    49 ms    49 ms  10.2.2.1
 16    49 ms    49 ms    50 ms  192.34.76.2
 17    52 ms    52 ms    50 ms  199.91.189.234
 18    49 ms    49 ms    49 ms  199.91.189.30

Trace complete.

C:\Windows\System32>ping 199.91.189.30

Pinging 199.91.189.30 with 32 bytes of data:
Reply from 199.91.189.30: bytes=32 time=50ms TTL=239
Reply from 199.91.189.30: bytes=32 time=60ms TTL=239
Reply from 199.91.189.30: bytes=32 time=49ms TTL=239
Reply from 199.91.189.30: bytes=32 time=52ms TTL=239

Ping statistics for 199.91.189.30:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 49ms, Maximum = 60ms, Average = 52ms

So... there is actually something the ISP's can do right now (well, may take a couple days or maybe weeks, depending on the red tape involved each time). It's just getting them to actually do it that is the problem.

[reliquum]

I am still going to refuse to pay twice to play a game i pay for to play on an internet i already pay to use. I give my ISP and SE money to play a game, THEY should fix the issue.


FF14 is not the only game having issues. While I was on WoW there was massive lag for a few hours, in the middle of no where, with no one else around me and this is what I see:

C:\Users\USER>tracert 63.240.161.189

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254]
2 22 ms 21 ms 21 ms 108-207-104-3.lightspeed.rcsntx.sbcglobal.net [1
08.207.104.3]
3 * 23 ms 23 ms 70.143.193.136
4 25 ms 23 ms 22 ms 12.83.80.197
5 49 ms 50 ms 49 ms gar3.cgcil.ip.att.net [12.122.132.213]
6 51 ms 51 ms 51 ms 12.122.251.50
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Users\USER>ping 63.240.161.189

Pinging 63.240.161.189 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 63.240.161.189:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)


Can you honestly tell me *I* should pay MORE money to use the internet when I get this? I am getting the node I connect to, swapped tomorrow. Will see how that works... and go from there.

Plus, when you're physically disabled, cannot work, and on a very...very....very limited income, $5 is a lot of money. =(

[Raist]

Blizzard's firewall is blocking your ping/ICMP at 63.240.161.189. It's nothing new... been that way for a while.

Something that may need to be looked at though is what is going on around 70.143.193.136, where you had a time-out and then two 23ms responses in the same trace. That means the response time went from 2000ms+ down to 23ms in the space of 3 ping requests (that's a swing from 2 seconds or more, down to 0.023 seconds).

That's an AT&T segment... SE can't do much about AT&T's routing and/or maintenance plans. Need to get with their Tier3 guys and have them look into things.

[reliquum]

Tuesday they swapped my node. The line tech said i was plugged into "a very old card" and moved me to a newer one. By newer, I am sure it is still old =_= as this area is not up to date on much of anything.

I haven't been on much as my RA has been flaring up and I can't play..... but when I do play, no lag(well, once, but it lasted about 5 seconds) and I have yet to have a 90k disconnect or a 2002 when trying to log in.

So keep hounding your ISP. So far, no need to pay for a VPN, no need for anything but to enjoy the game as of right now

I will know for sure by next Thursday if this worked! Giving it over a week to make sure it isnt just a fluke

[reliquum]

ffs. soon as i post. i go to play and rubber banding and lagging again.... SO. ....

think im going to take care of this eye twitch....



Edit: it was server lag whole guild was/is lagging all over the world. just got an error 90k, so im unsure if it is my net or the server.