The same issue on ps5.

Title: [PS5] Cannot connect to any server — CONNECTING FAILED (0x00010001), started after sudden power loss

Platform: PlayStation 5

Game: DayZ (console)

Error code: 0x00010001 — "Could not connect to the server because it is unreachable."

Description:

I am unable to connect to any DayZ server. The error appears instantly on every connection attempt.

The issue started immediately after a brief power outage (a few seconds) that shut down both my console and my router without a proper shutdown. The game worked normally earlier the same day.

Scope of the issue:

- Affects official servers AND community servers

- Affects EU servers (EUROPE - DE) and US servers (LA) alike

- The server browser loads correctly and shows populated servers with active player counts, so the master service is clearly reachable

- Only the actual connection handshake fails

Troubleshooting already performed (none of it helped):

- Verified the game is fully updated

- Full power cycle of the console (not Rest Mode) and the router

- PS5 Safe Mode: Clear Cache and Rebuild Database

- Deleted local DayZ saved data

- Restored licenses

- Uninstalled and reinstalled the game

- Router rebooted and reset to factory settings

- Tested on a completely separate network via mobile phone hotspot — same error

- Changed DNS servers (Cloudflare and Google)

- Tried connecting from a different PSN account on the same console

- Waited several hours between attempts to allow for server restarts

- Accepted a game invite from a friend who was already in a server (this reportedly resolved an identical case on Xbox Series X) — did not work for me

Additional notes:

Other online games on the same console connect without any problem, and PSN itself is working normally.

A moderator response in an earlier forum thread about this same error code indicated the cause was a character failing to disconnect properly from the server. Given that my issue began with an abrupt power loss mid-session, I suspect my character may be stuck in a similar state on the hive and is blocking all further login attempts.

Last server played on: [server name, e.g. 4016 | EUROPE - DE | 1st Person Only]

Any help checking my character state on the backend would be greatly appreciated. Thank you.

Hello.
>Could you please check whether there is an issue with my Xbox/DayZ account connection to the Official servers

Unfortunately this is not something we can do.

Did the game work on the mobile hotspot? and is your hotspot by the same provider as your main network? So far what you are describing points towards a network issue

The problem was not resolved when I tried using a mobile hotspot. The hotspot was from a different provider than my main internet connection.

Can you please send the hashed ID shown in the main menu bottom left corner and your name tag + when was the last session you tried to connect and a server ID

9D60235481C248434463B4F61E81CF04FF0BB732

Nuxell9515

I xan play only on

Last session was today, every server gives me the same error except 2823 server ID

Hello.
Considering you are able to connect to one server it is likely possible there is some issue on your network.
Could you try to contact your ISP and describe the situation? That a specific IP/Server can be reached while others not?

So, if I understand you correctly, after paying $55 for your game, I am now expected to contact my ISP and troubleshoot your server connectivity issue by going through individual IP addresses?

Is that seriously your solution?

Your game is unable to connect to multiple official servers, while at least one server is reachable. I have already reinstalled the game, restarted the Xbox, restarted the router, tried different servers, changed the Xbox region, and even tested the connection through a completely different mobile network. The problem still persists.

And instead of investigating whether there is an issue on your side – with your servers, routing, or whatever is causing this – your support is simply telling me that it is “likely a problem with my network” and sending me to my ISP.

What exactly do you expect my ISP to do? Troubleshoot your server infrastructure for you? Identify why your game can reach one specific server but cannot reach others? Go through every IP address used by your servers?

I paid for a working game, not for the privilege of diagnosing your networking infrastructure.

If you genuinely believe this is an ISP-side issue, then please provide me with something technically useful: the specific IP addresses/ports that are failing, the expected connection behavior, and any relevant error or network logs that would allow my ISP to actually investigate the problem.

Otherwise, please escalate this to someone who can properly investigate server connectivity and routing issues instead of repeatedly telling customers to contact their ISP.

At the very least, acknowledge that this may be a problem affecting multiple players and not simply dismiss it as an issue on my end without any actual investigation.

I am asking for technical support, not a generic “contact your ISP” response

And honestly, this is even more frustrating considering how long DayZ has been on the market. This is not a newly released game where occasional networking issues could be understandable. After all these years, players should not have to troubleshoot individual server IP addresses with their ISP just to determine why they cannot connect to official servers.

At this point, it genuinely feels like basic server connectivity is still being treated as the player’s problem rather than something your support team is expected to investigate.

One more thing I want to make absolutely clear:

This is not some minor inconvenience or a small technical issue. This is a critical bug that prevents me from playing the game I paid $55 for.

I cannot connect to the majority of official servers, which means I effectively cannot use a major part of the game. And when I finally contact your support looking for help, I am simply told to “contact my ISP” and figure it out myself.

Imagine buying a game and then being told by its support team: “We don’t know why you can’t connect to our servers, so go troubleshoot it with your ISP.”

That is not a solution. That is shifting responsibility to the customer.

If this is actually a known issue affecting multiple players, it should be investigated and acknowledged as such. And if you genuinely believe the problem is on my side, then I expect an actual technical explanation and specific diagnostics – not just a generic recommendation to contact my ISP.

I am not asking for anything unreasonable. I just want to be able to play the game I paid for.

I completely agree with Sir's statements. I paid for this game, but I've been experiencing this error for 7 days!!! Guys, this is not serious on your part. They're telling me to reboot the console after three complaints I've made with a list of the steps I've taken. I called my ISP, I bought a new router. It didn't help, you understand? Where is your help? Where is customer support? You're not a small indie company, guys.

Unfortunately we do not have any other data besides the error you have described - CONNECTING FAILED (0x00010001) which as it states - the connecting failed.
This is not something we are able to reproduce on our end nor affects majority of the playerbase. It is likely network specific problem and hence why you are being directed to your ISP as there is nothing we can do on our end right now.

Can you provide an IP example of the server that works and a server that does not?

All servers are down... official, community, different regions, and so on. I logged in from four accounts and three networks (including tethering). I called providers, tried different connection types, manually entered DNS data, and so on. I tried a ton of methods over the course of a week, and nothing worked. What did I pay money for? If a bug affects only a small number of players, can't it be fixed? Great, guys, very great (no).

I've been playing for years, and there are tons of bugs and errors, both for me and for my friends around the world.

Are you saying this is a feature of our network? Does everyone in every country have the same provider?

HEEEELLLOOOOO?????? 4 DAYS GUYS???? This issue has been reproducible for me for

almost two weeks. I have already provided all requested information and tried every suggested troubleshooting step, including different networks. I am still completely unable to connect to any DayZ server on PS5. Support has not provided a solution or meaningful update. Please escalate this to the team responsible for the PS5 backend/ server connection issue and investigate my account/character/server-side state.

Hello.
This was further investigated by our programmers. From what we can see, the issue is very likely not backend related. If this were an issue on the backend side it would return a different error. 0x00010001 (“server is unreachable”) error is related purely to the client connecting to the server and that connection works entirely without the backend. The only thing we can suggest at the moment is to have an IT specialist to help you troubleshoot and fix the connection issue.

Hello. I performed additional network diagnostics from a Windows 7 laptop connected to the same Kyivstar home Internet connection/router as my Xbox Series X.

I compared a DayZ EU server that I can successfully connect to with a DayZ EU server that consistently returns 0x00010001 (server is unreachable).

1. Working DayZ server

IP: 31.214.158.208
Port: 11100

• The server is accessible from my Xbox and I can connect to it successfully.

• ICMP ping from the laptop: 4/4 replies, 0% packet loss, ~229 ms RTT.

• tracert 31.214.158.208 reaches the destination successfully.

2. Non-working DayZ server

IP: 195.82.158.114
Port: 11000

• The Xbox consistently fails to connect and returns 0x00010001.

• ICMP ping from the same laptop: 0/4 replies, 100% packet loss.

• tracert 195.82.158.114 reaches a Nitrado node in Frankfurt (80.81.194.168), after which all subsequent hops time out until the end of the trace.

Both tests were performed from the same physical network, same router and same ISP (Kyivstar). The difference is therefore reproducible when comparing an accessible DayZ server against an inaccessible one.

I understand that ICMP filtering can cause ping/traceroute timeouts and that this alone does not prove that traffic is being blocked. However, the combination of:

Xbox → 0x00010001
same Kyivstar connection → 100% ICMP loss to the affected IP
traceroute stopping after a Nitrado/Frankfurt hop
while another DayZ EU server is reachable from the same connection

suggests a possible routing/reachability issue between my ISP and specific DayZ server IP ranges, rather than a general Xbox Network or DayZ backend problem.

Interestingly, both IPs appear to be hosted by marbis GmbH / AS199610, so the issue may be related to the path to a specific destination IP rather than the hosting provider as a whole.

Could the development/network team please check whether 195.82.158.114 is reachable from the relevant infrastructure and whether there are any known routing, filtering, firewall, or connectivity issues affecting connections from Ukrainian ISPs/AS15895 (Kyivstar) to this destination?

I can provide the complete tracert output/screenshots and additional server IP comparisons if required.

Hello,

I would like to add a PS5 case with packet-capture results and a comparison between two ISPs, supporting the connectivity issue reported here by other Kyivstar customers.

Symptoms and setup

• Platform: PlayStation 5.

• Location: Mykolaiv, Ukraine.

• Affected ISP: Kyivstar, AS15895.

• DayZ displays 0x00010001 (“server is unreachable”) on every official and community server I have tried. The server browser loads normally.

• The same PS5 connects successfully through another ISP, Dykyi Sad / WildPark, AS31272.

Bohemia support advised me to contact my ISP. I understand the explanation above that this error concerns the direct client-to-server connection rather than the DayZ backend. However, identifying which network drops the traffic requires investigation from both ends.

1. Actual PS5 game traffic — 14 September 2026

The PS5 was connected through a Windows PC hotspot to capture its traffic with pktmon. The same local capture setup was used for both providers.

On Kyivstar, 12:33–12:34 UTC, the capture report recorded four outgoing UDP packets and zero replies for each of these game endpoints:

85.190.153.89:11300
128.0.112.98:10500
5.62.99.20:10500
31.214.136.154:10900
46.251.235.7:11200
95.156.224.90:10500

Incoming UDP traffic from unrelated services was recorded during the same capture, but no incoming UDP packets from Nitrado were recorded.

On WildPark, 12:41–12:49 UTC, the same PS5 successfully connected, with bidirectional game traffic:

Server endpoint          Outgoing packets    Incoming packets
31.214.136.144:11100             83                  89
109.230.243.46:11300            971                1160
195.82.158.111:10200           1467                1940
195.82.158.110:10400           1179                1527

These console sessions used different server endpoints. To compare identical destinations across providers, separate PC tests were also performed.

2. Identical destinations tested through both ISPs

In PC diagnostics on 13–14 September, these exact endpoints responded to both ICMP ping and UDP A2S queries through WildPark, but neither responded through Kyivstar:

5.62.99.23:11101
195.82.158.71:10601

These are server-query ports, separate from the PS5 game ports listed above.

3. Follow-up checks — 16 September 2026, approximately 22:09 UTC

The problem remained reproducible through Kyivstar:

Endpoint                  ICMP                  UDP A2S
5.62.99.23:11101           No replies            Timeout
195.82.158.71:10601        No replies            Timeout
95.156.194.221:11701       No replies            Timeout
95.156.194.19:10401        Replies, ~211 ms       Valid challenge + A2S_INFO reply

The successful response from another Nitrado address demonstrates that this is not a blanket failure of UDP or access to all Nitrado servers.

The traceroute to 5.62.99.23 was:

192.168.1.1
176.8.125.253
172.29.104.252
80.81.194.168
80.81.197.21
No further replies through the tested hop limit of 9

A control destination, 85.190.162.196, was reachable by ICMP at approximately 42 ms through the same first five hops.

What these results establish

There is a reproducible, ISP-dependent reachability problem affecting specific Nitrado destinations, supported by actual PS5 UDP traffic observations and separate PC tests.

I am not claiming that traceroute proves where packets are dropped, or that Nitrado is definitely blocking Kyivstar. Filtering, anti-DDoS rules, and forward or return-path routing problems remain possible. Client-side tests cannot distinguish these conclusively.

Could you please escalate this evidence to the team responsible for DayZ hosting connectivity and coordinate with Nitrado?

Specifically, please check:

1. Whether UDP packets from the affected Kyivstar connection reach Nitrado’s edge and the game servers.

2. Whether firewall or anti-DDoS rules discard these packets.

3. Whether replies are sent, and whether the return route to Kyivstar is working.

I can provide the text capture reports, complete diagnostic outputs, and the public source IP privately, and help arrange a timed connection attempt for log correlation.

A network-related error does not by itself establish which side is responsible. These measurements provide concrete endpoints and timestamps for a joint investigation beyond a general recommendation to contact the ISP.

Thank you.

Hello. I have an important update regarding the issue.

The problem has now suddenly resolved itself. Since approximately September 18–19, 2026, I can connect to all European Official DayZ servers again, including the servers that previously consistently returned 0x00010001.

I did not change anything on my side before this happened — no router replacement/reset, no Xbox network changes, no game reinstall, and no change of ISP.

Previously, all/most European Official servers were affected, while a small number of servers were reachable. I also provided the comparison between:

Working: 31.214.158.208:11100

Previously unreachable: 195.82.158.114:11000

From the same Kyivstar connection, the affected IP had 100% ICMP packet loss and the traceroute stopped after a Nitrado/Frankfurt node, while the working IP was reachable.

Now the previously affected European Official servers are reachable again without any action on my side.

This may be useful information for investigating the original issue, as it suggests that whatever was causing the connectivity problem may have been temporary or related to routing/reachability rather than a local Xbox installation issue.

Yes. Problem solved