Error 90000 & lag

[Raist]

Traceroutes are a big help... especially if they clearly show a bottleneck happening with someone like Level3, Cogent, TATA, etc. (their routing partner that is taking you from AT&T's network across country and into Montreal to SE's ISP). Seeing dramatic improvement via a VPN is another good clue that there is a routing issue... they will need to trace your specific route so they get a better idea of where you may be bogging down in route (again, having tracert samples can be a big help).

Mileage may vary depending on who you are dealing with. IDK why I was able to get through with less effort than some... I basically just told them I was seeing high packet loss and lag spikes along specific routes and insisted I talk to Tier3 so I can get the data to them and they eventually put me through after I played their game of rebooting things and sending technicians to verify cabling and such was good. I basically forwarded my modems logs along with ping/trace data to my server, as well as some samples for other services like google/youtube and such that would also show issues at times. They've also been catching a lot of flack via their forums and twitter over similar issues as well. We were also dumping data on them through their posted help email address. IDK if I just timed it right to coincide with them eventually getting enough data to prompt them to take action, or if they were just tired of me harassing them each week (sometimes more often). Now I just send them the data when I have issues and they fix it a few days later. Sometimes, they catch it before me and change it automatically (modem will reboot on it's own, as it sometimes calls for it to make some changes). And by fixing it, I mean they change the route I take. A while back, they took me off the gateway for Florence and put me on Hilton Head's gateway. Other than that, they change the routing partner that gets me out of either Atlanta, Charlotte, or Raleigh-Durham and carries me up to Toronto/Montreal area to hit Ormuco. The route changes every couple of weeks amongst Level3, TATA, and Cogent (sometimes I get on PSI-Net, who is part of Cogent and has a strong peering link with Ormuco... but it unfortunately gets congested frequently, which sucks because the response time is amazing when I first get switched there).

Oh, and that's why people ask about rebooting the network devices by the way. Sometimes it is needed to do things like acquire new channel alignments and such. A quick reboot can sometimes wind up putting you on another gateway or a cleaner primary channel, potentially clearing up a lot of issues.

As for the VPN's, some that have decent free options don't work too well with games (will filter out things that aren't typical website traffic and such). Tunnel Bear worked well for me with the game. You get 500MB a month for free, can get extra data if you promote them through social media. To subscribe it can run between $4 and $5 a month depending on how you buy. GhostVPN worked too when I tried it last year. Can get some add pop-ups with their free version, and it's like a 3 hour limit per week or something like that. Hotspotshield was another that worked.. but it was ad supported for the free version as well, which could cause some issues. There are more out there, but those were the ones I tinkered with the most last year. Of those 3, Tunnel Bear seemed to be the more consistent for me on speed/latency when I tested them, so I stuck with their free version in case I needed it again. Still works today... but don't use it for the game (haven't needed VPN tweak for almost a year now). I just use it to secure my line for some other things I do from time to time, and 500MB is plenty for me to do that stuff.

[reliquum]

Hope this comes out ok. I have been doing that and sending it to them, this is a copy of the ones I did last week. Aaaaand, noticing an awful lot of level3's...... I can physically fix computers. build them .tear them apart and rebuild. software and programming and anything not physical and I am lost. My modem is rebooted every few days along with my computer. Aside from the level 3 pings.... anything i can point out to them i need to be routed away from?

And Raist, THANK YOU. so far over the last few weeks, this has been going on for close to 2 months. you've been the only person who has actually pointed me in a direction i have hope for fixing this issue!



C:\Users\USER>tracert 199.91.189.40

Tracing route to 199.91.189.40 over a maximum of 30 hops

1 1 ms 1 ms 1 ms homeportal
2 * * * Request timed out.
3 * * * Request timed out.
4 24 ms 26 ms 23 ms 12.83.80.189
5 26 ms 27 ms 26 ms gar26.dlstx.ip.att.net [12.123.16.85]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 67 ms 68 ms 67 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

10 * * * Request timed out.
11 * * * Request timed out.
12 68 ms 69 ms 69 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

13 82 ms 71 ms 68 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
14 * * * Request timed out.
15 156 ms 141 ms 141 ms 192.34.76.2
16 147 ms 152 ms 145 ms 199.91.189.234
17 144 ms 143 ms 144 ms 199.91.189.40

Trace complete.

C:\Users\USER>tracert 199.91.189.40

Tracing route to 199.91.189.40 over a maximum of 30 hops

1 3 ms 1 ms <1 ms homeportal
2 24 ms 24 ms 22 ms 108-207-104-2.lightspeed.rcsntx.sbcglobal.net [1
08.207.104.2]
3 * * * Request timed out.
4 24 ms 26 ms 26 ms 12.83.80.189
5 25 ms 27 ms 27 ms gar26.dlstx.ip.att.net [12.123.16.85]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 72 ms 74 ms 73 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

10 * * 68 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]

11 * * * Request timed out.
12 68 ms 67 ms 67 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

13 68 ms 69 ms 68 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
14 * * * Request timed out.
15 151 ms 149 ms 139 ms 192.34.76.2
16 143 ms 128 ms 123 ms 199.91.189.234
17 137 ms 145 ms 147 ms 199.91.189.40

Trace complete.

Tracing route to 199.91.189.40 over a maximum of 30 hops

1 1 ms 1 ms 1 ms homeportal
2 * * * Request timed out.
3 * * * Request timed out.
4 24 ms 26 ms 23 ms 12.83.80.189
5 26 ms 27 ms 26 ms gar26.dlstx.ip.att.net [12.123.16.85]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 67 ms 68 ms 67 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

10 * * * Request timed out.
11 * * * Request timed out.
12 68 ms 69 ms 69 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

13 82 ms 71 ms 68 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
14 * * * Request timed out.
15 156 ms 141 ms 141 ms 192.34.76.2
16 147 ms 152 ms 145 ms 199.91.189.234
17 144 ms 143 ms 144 ms 199.91.189.40

Trace complete.

============================================
Trace : 199.91.189.40
------------------------------------------------------------------------------------------------------
local -> IP= RESERVED
TTL= 1 IP= 24 ms RESERVED
TTL= 2 TimedOut
TTL= 3 TimedOut
TTL= 4 IP= 12.83.80.189 26 ms UNITED STATES
TTL= 5 IP= 12.123.16.85 29 ms UNITED STATES
TTL= 6 TimedOut
TTL= 7 TimedOut
TTL= 8 TimedOut
ICMP Errors
=============================================


Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\USER>pathping 199.91.189.40

Tracing route to 199.91.189.40 over a maximum of 30 hops


1 homeportal
2 108-207-104-2.lightspeed.rcsntx.sbcglobal.net [108.207.104.2]
3 * * *
Computing statistics for 50 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% homeportal
0/ 100 = 0% |
2 25ms 0/ 100 = 0% 0/ 100 = 0% 108-207-104-2.lightspeed.rcsntx.sb
cglobal.net [108.207.104.2]

Trace complete.

C:\Users\USER>pathping 199.91.189.40

Tracing route to 199.91.189.40 over a maximum of 30 hops


1 homeportal
2 108-207-104-2.lightspeed.rcsntx.sbcglobal.net [108.207.104.2]
3 * * 70.143.193.134
4 12.83.80.189
5 gar26.dlstx.ip.att.net [12.123.16.85]
6 * * *
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% homeportal
0/ 100 = 0% |
2 25ms 0/ 100 = 0% 0/ 100 = 0% 108-207-104-2.lightspeed.rcsntx.sb
cglobal.net [108.207.104.2]
0/ 100 = 0% |
3 25ms 0/ 100 = 0% 0/ 100 = 0% 70.143.193.134
22/ 100 = 22% |
4 28ms 22/ 100 = 22% 0/ 100 = 0% 12.83.80.189
78/ 100 = 78% |
5 --- 100/ 100 =100% 0/ 100 = 0% gar26.dlstx.ip.att.net [12.123.16.
85]

Trace complete.

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\USER>ping 199.91.189.40

Pinging 199.91.189.40 with 32 bytes of data:
Reply from 199.91.189.40: bytes=32 time=136ms TTL=241
Reply from 199.91.189.40: bytes=32 time=141ms TTL=241
Request timed out.
Reply from 199.91.189.40: bytes=32 time=134ms TTL=241

Ping statistics for 199.91.189.40:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 134ms, Maximum = 141ms, Average = 137ms


C:\Users\USER>ping 199.91.189.40

Pinging 199.91.189.40 with 32 bytes of data:
Reply from 199.91.189.40: bytes=32 time=146ms TTL=241
Reply from 199.91.189.40: bytes=32 time=142ms TTL=241
Reply from 199.91.189.40: bytes=32 time=140ms TTL=241
Request timed out.

Ping statistics for 199.91.189.40:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 140ms, Maximum = 146ms, Average = 142ms