FatsharkJulia

Sorry about this, I’ve added your report to our database.

I’ve passed this on to our developers. Thank you!

I’ve added your report to our database. Thank you!

Thank you for your report, I’ve added this to our database.

We’re looking in to similar issues, apologies.

Thank you for your report. We’re looking at connectivity issues on a larger scale, and hopefully this will improve for you with time.

Please be sure to include the crash reports produced. Thank you!

I’m merely the communicator, nothing will change if I head to bed. The smart people are still working.

They are also working on the current downtime as we speak.

Much appreciated!

Servers are stabilising after a second downtime within the space of a couple of hours, hang in there.

We’re battling some (new) downtime at the moment - please check back in shortly!

I’ve said something similar in the Backend Error post, but I also want to make it known here that we are aware of how serious and widespread this issue is. Our developers are actively investigating.

I appreciate everybody wants information and as soon as I have it, I’ll share it with you.

We initially suspected this was isolated to those using IPv6 but that doesn’t seem to be the case based on your responses, and there is not much consistency between ISPs either.

Some players have been able to resolve their issues by changing their DNS or using a VPN (similarly to the Backend Error issue) but I appreciate using a VPN is not a viable long-term solution.

Just wanted to emphasise before I clock out for the night that we are very much aware of how critical this issue is (in addition to the internal_error), and it may seem like we’re being quiet on the matter - but the reality is we’re deep in investigation.

As soon as I have more information to share, I will!

I understand some players have been able to work around this by changing their DNS or using a VPN but I appreciate this isn’t ideal.

Bit of a hiccup. The smart people are looking in to it!

D’oh, I’ve now renamed it as darktide_launcher in the FAQ!

It’s odd you would experience this 3h ago, long before we put a patch live! As that’s the only time you should really see this error.

Could you see if it occurs now that we have put a new patch live?

This will likely be the result of some bizarre buffer overflow issue. It sounds wild, but do you have another Ethernet cable you can try?

We’re looking in to this, apologies.