20220225 - Connection Issues (UK)

Normal traceroute as of 20:04

1 Like

Still no DC… don’t tell me they put in some kind of fix :open_mouth:

1 Like

Our test server network is in a different geographical location to the production network and is not behind Cloudflare’s systems. If you trace the route, then you will get very different paths.

% nslookup tranquility.servers.eveonline.com
Name: d638e439e07f413c97200d057e5ebd05.pacloudflare.com
Address: 172.65.201.188
Aliases: tranquility.servers.eveonline.com
tranquility.servers.eveonline.com.cdn.cloudflare.net

% nslookup singularity.servers.eveonline.com
Name: singularity.servers.eveonline.com
Address: 87.237.38.2

(And this IP address above for TQ is not its ā€œcorrectā€ destination IP address; only Cloudflare can access that one.)

1 Like

We will know when either they tell us or the disconnects stop happening… There was a disconnect spike at 19:00 this time and nothing at 19:55. But then again, there were minor spikes hourly even there were larger spikes every 4 hours.

Yeah, far too early to tell but here’s hoping :slight_smile:

1 Like

Disconnect 20:13

Is it a count-down?!? :grimacing:

Still no DC here

1 Like

Still no DC for me too.

1 Like

I disconnected at 18:59 exactly …
so still not fixed :frowning:

still connected,

1 Like

Good point, we did all have that early DC so maybe it just got bumped an hour earlier.

1 Like

Forwarded to Cloudflare; they were quick to point out they only got half of the data in our first reply. :smiley:

Does this mean we should looking at 22:55 ish or 22: 49?

1 Like

I guess there could be one around either 22.55ish, or then 23.55ish

I haven’t had connection issues in a long time but past few hours I’ve been disconnected twice. One disconnect happened just a few minutes ago.

I’m not from the UK though, but from the Netherlands. No idea if it’s related to these issues, thought I’d share.

worth posting your trace route (the needed ip’s) to see if you hit any of the same maybe because Netherlands routing seems to be a possible main cause.

Just DC.

I just had a DC at 20:51

Same. Ran a traceroute straight after it happened but was just the normal routing.