![]() |
|
|
|
#1
|
|||
|
This happened to me quite a lot today, in Europe so no AT&T, not happened a lot prior to today (that I have noticed)
__________________
| ||
|
#2
|
|||
|
It's baaaack.... good grief
Had a couple of good days at least | ||
|
#3
|
|||
|
I've been having these same issues for the last couple of days. Timed perfectly with my druid getting 29 and trying to doing some porting.
| ||
|
#4
|
|||
|
I've been having these problems starting today.
So far, I've noticed the following behaviour: LD on zoning (on my end, I'm stuck on the loading screen forever - waited 25 minutes in one case before closing the window. Group mates confirmed I went LD within a few minutes on their end) LD on logging in (same as LD on zoning, stuck on the loading screen indefinitely) On some recovery from LD, server select screen is empty On some recovery from LD, I'm told my spell files are out of date Every once in a while I just have an extremely long zonetime (10+ mins) Interestingly, once I'm IN the zone, I have no issues at all. No other internet issues experienced outside of this. I'm Canadian, and on Bell, so it isn't the infamous AT&T issue. Tracert while experiencing the issue below: Tracing route to 66.55.145.2 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms mynetwork [192.168.2.1] 2 8 ms 7 ms 3 ms 10.11.2.241 3 * 3 ms 2 ms 10.178.206.72 4 3 ms 3 ms 2 ms 10.178.206.73 5 20 ms 23 ms 23 ms tcore4-toronto12_2-4-0-0_.net.bell.ca [64.230.10 4.164] 6 16 ms 19 ms 19 ms tcore4-montreal01_hundredgige0-9-0-0.net.bell.ca [64.230.79.195] 7 17 ms 18 ms 16 ms newcore1-newyork83_so6-0-0_0 [64.230.187.234] 8 17 ms 19 ms 16 ms bx6-newyork83_xe3-0-0.net.bell.ca [64.230.187.15 8] 9 23 ms 43 ms 23 ms nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157] 10 * 22 ms 22 ms vl23-br2.pnj1.choopa.net [66.55.130.53] 11 22 ms 21 ms 21 ms vl20-br1.pnj1.choopa.net [108.61.244.41] 12 * 20 ms * ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61 .244.50] 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. | ||
|
Last edited by Bittersauce; 09-10-2016 at 07:41 PM..
| |||
|
#5
|
||||
|
Quote:
| |||
|
Last edited by thedonkdonk; 09-10-2016 at 07:43 PM..
Reason: Time frame
| ||||
|
#6
|
||||
|
Quote:
6 11 ms 11 ms 12 ms peer6-hu0-1-0-1.telehouse.ukcore.bt.net [195.99.127.25] 7 14 ms 12 ms 16 ms 166-49-211-230.eu.bt.net [166.49.211.230] 8 78 ms 77 ms 77 ms ixp1-xe-11-0-1-0.us-nyc.eu.bt.net [166.49.208.144] 9 * * * Request timed out. 10 * 81 ms 82 ms vl23-br2.pnj1.choopa.net [66.55.130.53] 11 81 ms * * ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61.80.218] 12 * * * Request timed out. 13 80 ms 86 ms 89 ms 170.rogean.com [108.61.129.170] | |||
|
#7
|
||||
|
Quote:
| |||
|
#8
|
|||
|
tonight has been awful - cant zone one time successfully
its 50-50 whether my character actually enters world from character select ( if I make it there )
__________________
Eratani / Cleratani / Eratou / Stabatani / Flopatani / Eratii
| ||
|
#9
|
|||
|
Same exact problems from KC on Google Fiber. Seems that Google Fiber and AT&T are the primary offenders. This all started 3 days ago. I never had any problems prior.
| ||
|
#10
|
|||
|
Same issue and I'm with Orange in Europe. I never had zoning time issues and only the odd LD/crash here and there. Since two days ago it's massive, almost every time I zone I crash and have to manually close EQ etc..
| ||
![]() |
|
|