avatar
dmitry
REGULAR
1Issues
0Score
  • dmitryon [DZG-470]

    Yes. Problem solved

  • dmitryon [DZG-470]

    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:

    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:

    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:

    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:

    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:

    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.