20220225 - Connection Issues (UK)

Unfortunately, the issue you are experiencing happens outside of CCP’s (extended) network. So there is very little CCP can do except gather information and alert the network providers involved so they can investigate and resolve the situation (In this thread’s case, Virgin Media and their parent Liberty Global).

It might seem pointless, but running the traceroutes as explained by the CCP Explorer and reporting with that information is really helpful, as it allows CCP to see what physical route your traffic takes, what network providers are involved in that route, and help pinpoint at which point things go wrong.

2 Likes

Today from approx 07:45 GMT I had 2 straight disconnects without even getting into the game. Then had a 3rd within an hour of this time.
Here is my traceroute today

Tracing route to d638e439e07f413c97200d057e5ebd05.pacloudflare.COM [172.65.201.188]
over a maximum of 30 hops:

1 2 ms 1 ms 2 ms 192.168.0.1
2 11 ms 10 ms 9 ms 10.53.32.217
3 9 ms 8 ms 8 ms leed-core-2a-ae40-0.network.virginmedia.net [80.0.55.189]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 19 ms 21 ms 18 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
8 21 ms 20 ms 20 ms 213.46.182.162
9 23 ms 27 ms 23 ms adm-bb4-link.ip.twelve99.net [62.115.137.64]
10 22 ms 31 ms 23 ms brx-b4-link.ip.twelve99.net [62.115.116.231]
11 * * * Request timed out.
12 23 ms 30 ms 21 ms 172.65.201.188

Trace complete.

09:56 disconnect

Also 09:56

Disconnected 09:56

Tried running a trace but got timed out by hop 4 and did not complete

Hopefully this will help someone (Windows users):

Open a blank text file.

Copy the following into your file:

:START
@echo Started: %date% %time%
tracert tranquility.servers.eveonline.com
@echo Completed: %date% %time%
timeout 60
GOTO START

save your file (ie filename.bat) to your desired folder. MUST be .bat
Open a Command prompt window
Drag your saved file into the command prompt window (it will show the location when dragged) and hit enter/return to run it.

Voila - you are now trace routing every 60 seconds and the output will run every 60 seconds.

Simply change tiimeout 60 to your own desired time if needed :slightly_smiling_face:

2 Likes

10:14 Disconnect

Yeah, I logged in just in time to catch the 9.56.
So it seems the routing has changed which I guess means they are at least trying different things, although from the overnight posts it sounds like it may be worse.
Instead of
8 22 ms 22 ms 22 ms adm-bb4-link.ip.twelve99.net [62.115.137.64]
9 24 ms 21 ms 21 ms adm-b10-link.ip.twelve99.net [62.115.120.229]
10 * * 18 ms cloudflare-ic342028-adm-b10.ip.twelve99-cust.net [62.115.172.231]
11 20 ms 19 ms 25 ms 172.65.201.188

I now also get

8 23 ms 22 ms 26 ms adm-bb4-link.ip.twelve99.net [62.115.137.64]
9 23 ms 22 ms 20 ms brx-b4-link.ip.twelve99.net [62.115.116.231]
10 * * 211 ms cloudflare-svc079354-ic369103.c.telia.net [213.248.67.9]
11 21 ms 23 ms 22 ms 172.65.201.188

So we are now going amsterdam then stockholm. Are VM actually aware the servers are in London?

Just out of curiosity, why does the final IP address show as being located in the US?

10:14 DC here too

most recent trace
7 21 ms 22 ms 23 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
8 23 ms 22 ms 30 ms 213.46.182.162
9 25 ms 33 ms 32 ms adm-bb4-link.ip.twelve99.net [62.115.137.64]
10 23 ms 24 ms 23 ms brx-b4-link.ip.twelve99.net [62.115.116.231]
11 * 25 ms * cloudflare-svc079354-ic369103.c.telia.net [213.248.67.9]
12 26 ms 25 ms 22 ms 172.65.201.188

Trace complete.

From running the batch file (mentioned at 20220225 - Connection Issues (UK) - #382 by Alaska):

Before -

6 33 ms 23 ms 28 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
7 19 ms 19 ms 17 ms 213.46.182.162
8 28 ms 21 ms 24 ms adm-bb4-link.ip.twelve99.net [62.115.137.64]
9 22 ms 22 ms 20 ms brx-b4-link.ip.twelve99.net [62.115.116.231]
10 27 ms 31 ms * cloudflare-svc079354-ic369103.c.telia.net [213.248.67.9]
11 33 ms 23 ms 25 ms 172.65.201.188

After -
6 23 ms 36 ms 25 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
7 28 ms 19 ms 19 ms 213.46.182.162
8 23 ms 22 ms 30 ms adm-bb4-link.ip.twelve99.net [62.115.137.64]
9 24 ms 21 ms 24 ms brx-b4-link.ip.twelve99.net [62.115.116.231]
10 * * * Request timed out.
11 36 ms 36 ms 26 ms 172.65.201.188

Did not hit the cloudflare on second call

Weird, no DC for me and I am undocked so would have expected to be.

10:14 DC here too, on a VPN connection.

For now many Virgin Media customer have used VPN (from the UK to the UK) to bypass the fault. Long-term then either Virgin Media finds that fault and fixes it (I have a relatively good confidence in that they do) or you should consider looking for another ISP that offers a high-quality, stable internet that is suitable for long-lived TCP connections. Honestly then Virgin Media did appear to offer such services before 22 o’clock on 23 February.

I don’t know if you can get compensated by Virgin Media for having to use VPN to bypass the fault.

We can’t fix internet network routing with a patch, and the server is fine.

We don’t control the internet network routing, in particular we do not control how Virgin Media routes their network. CCP with its external-network partner Cloudflare advertise through DNS and BGP where Tranquility is and where to route network traffic to. But ISPs control the routing within their own networks, what carriers they use, and where they peer with other networks. In particular, they control their egress points to other networks and don’t have to follow the shortest path. The best path from an ISP’s perspective is a combination of hops and cost. But BGP flaps and frequent routing changes are the bane of stable long-lived TCP connections, such as the one the EVE Client has to the EVE Server.

4 Likes

I’ve forwarded this.

10:24 Disconnect

Also forwarded.

1 Like

10.24 DC and we now seem to be back to the original routing from yesterday.

Edited the batch file to include start/end time so you know where to look 20220225 - Connection Issues (UK) - #382 by Alaska

10:24 DC
BEFORE
7 23 ms 22 ms 28 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
8 26 ms 40 ms 22 ms 213.46.182.162
9 29 ms 33 ms 33 ms adm-bb4-link.ip.twelve99.net [62.115.137.64]
10 33 ms 25 ms 33 ms brx-b4-link.ip.twelve99.net [62.115.116.231]
11 30 ms * * cloudflare-svc079354-ic369103.c.telia.net [213.248.67.9]
12 32 ms 29 ms 39 ms 172.65.201.188

AFTER
7 30 ms 31 ms 27 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
8 28 ms 23 ms 22 ms 213.46.182.162
9 30 ms 27 ms 27 ms adm-bb3-link.ip.twelve99.net [62.115.136.194]
10 22 ms 46 ms 31 ms adm-b10-link.ip.twelve99.net [62.115.120.227]
11 33 ms 28 ms 50 ms cloudflare-ic342028-adm-b10.ip.twelve99-cust.net [62.115.172.231]
12 33 ms 21 ms 29 ms 172.65.201.188

DC at 10:24 route has changed back to the one used yesterday
7 23 ms 57 ms 26 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
8 22 ms 23 ms 32 ms 213.46.182.162
9 24 ms 22 ms 30 ms adm-bb4-link.ip.twelve99.net [62.115.137.64]
10 23 ms 31 ms 23 ms adm-b10-link.ip.twelve99.net [62.115.120.229]
11 24 ms 26 ms 35 ms cloudflare-ic342028-adm-b10.ip.twelve99-cust.net [62.115.172.231]
12 20 ms 20 ms 28 ms 172.65.201.188

Trace complete.