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.

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.

What did Kyivstar actually tell you? They told me it's not their problem and they don't handle that. How can I reach their technical department and someone who will understand what this is about and help me with it?

So, how did it go?

Were you able to find out anything or get anything done with Kyivstar?

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.

Telegram:
@D1z

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 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 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 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 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.