CCP_Explorer

(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)

Please go and read ...

WOW! Internet customers who are still impacted; can you do an experiment for me and report back if this changes anything, please?

Be default then the EVE Client connects to Tranquility on port 26000 (this is known as the “Quake port”). But we also have backup port on 3724, which can be activated manually (this is known as the “WOW port” where the reference is World of Warcraft and not WOW! Internet…). We normally use this for customers where port 26000 is completely blocked outbound.

Please locate the prefs.ini file. You will normally find it in C:\Users\YOURPCUSERNAME\AppData\Local\CCP\EVE\c_eve_sharedcache_tq_tranquility\settings_Default\ or a similar location on your computer.

• Make a copy of this file for safe keeping.
• Open this file in a text editor, such as Notepad, and edit the last line port=26000 to port=3724
• Don’t change anything else and don’t add empty lines or line breaks.
• Save and close the file.

Start ...

KB3004394 is indeed a known resolution to that problem.

You were all very busy there for a while…

umokka-server805×364 99.5 KB

(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)

Excellent!

Glad to hear that, hope it stays that way!

Added above.

Monday afternoon update:

We are still working with Cloudflare on this and you should be getting replies to your CCP support tickets shortly with a request from Cloudflare for more information.

We are also working with WOW! on this matter and they just said in an email to me:

If your customers haven’t already, could you have them call in to WOW to report their problems and include traceroutes to the affected sites?

That would be a traceroute to 172.65.201.188

Update:

When they call into the Call Center (866 496 9669), please have them reference PRB0043017 in relation to this issue.

@Sumlayen_Chanlin & @Kalindian_Aurgnet: Please update your support tickets with fresh traceroutes (or create new support tickets if the previous ones have already been closed).

And please namedrop me in the support ticket since I want to see the details.

No, we at CCP did not. It is very literally a change that WOW! and Cloudflare made on 13 May at 06:00 UTC. I’ve since heard that fix broke again.

Long-lived TCP connections against a real-time simulation on the one hand and short-lived HTTPS connections to a website on the other hand are two very different things.

EVE is very frugal on network bandwidth but doesn’t tolerate well packet loss, excessive latency or timeouts, since the universe simulation has moved on. Also see my comment above about issues Virgin Media users in the UK have had.

I never said it was your ISP, as I have repeatedly stated there is a verified network routing issue ...

End of day Friday update:

We here at CCP have tirelessly been keeping WOW! and Cloudflare updated on this issue all week and how it is impacting you, EVE Online players at WOW! Internet.

Current status is that we at CCP are in contact with multiple people at WOW! at all levels of the company, have an open support ticket with Cloudflares’ Enterprise Support, and we have been bridging communication between WOW! and Cloudflare. Both WOW! and Cloudflare confirmed this afternoon that they are now in direct contact, diagnosing and trying to resolve this issue, which is a network routing issue between WOW! and Cloudflare.

Please send both us and WOW! a support ticket with details.

EVE’s Customer Support confirmed today that the only pattern to these disconnect issues are customers of WOW! Internet. Some very few other players are also experiencing disconnects and we want to hear about your experience in a support ticket (see ...

My dear Langbard Vafud, this is all completely incorrect as I have repeatedly stated in this thread.

Please do me a favour, read Are you experiencing issues staying connected to EVE Online? and follow the...

If you trace your route to TQ (using the command tracert 172.65.201.188) then you should be able to spot Chicago in there. It might look something like this, this is a confirmed failure route through Telia in Chicago:

chi720×88 3.64 KB

WOW! and Cloudflare set up a new peering connection in Ashburn, VA, early on Tuesday morning (UTC). Cloudflare now has CCP’s support ticket on hold until they can peer with WOW! in Chicago, IL.

Update:

Some WOW! Internet customers are reporting to us that the issue has been resolved for them. They appear to have in common to previously have been routed through Atlanta, GA and are probably now routed through a new peering connection between WOW! and Cloudflare in Ashburn, VA, which was set up yesterday morning.

Other WOW! customers have reported to us that the issue persists and have sent us detailed clients logs (per instructions above). They appear to have in common to be routed through Chicago, IL. The investigation continues.

I would like to emphasize that we are looking for reports of the EVE Client being unable to maintain a connection to the EVE Server.

For the purposes of this investigation then we are not looking for information about lag or chat reconnects (although we always appreciate such reports), but rather focused reports on if the EVE Client gets disconnected from the EVE Server after approx. 1-10 minutes of gameplay.

And then only from players who do not have WOW! Internet as their internet service provider in this thread here, since we are aware of those issues and are actively investigating them.

WOW! Internet customers should rather ple...

It is a database performance issue that has been under investigation this afternoon.