Bungie Answered
[Weekly Report] PS5 Sign-in Loop Persists - Update [1.0.6] (Still Unresolved)
Status Report: Still unable to sign in.
Current Version: [1.0.6]
Platform: PlayStation 5
ISP: J:COM (Japan)
Timeline:
-Issue started: March 31 (Patch 1.0.5.1)
-Days since last successful login: [16]days
-Status: Unresolved even after multiple maintenance cycles.
Confirmed Facts:
-Mobile tethering works, but standard ISP (J:COM) route is still blocked.
-This is a routing/handshake issue on Bungie's server-side.
I have given up on my season goals and am not currently playing the game due to this persistent error. However, I will continue to report this weekly until a permanent fix is implemented for all affected Runners.
Note: For privacy reasons, I will delete/redact this post and create a new one every week.
1
Комментарии
Hello there,
Thank you for reaching out.
This is a known and tracked situation with PS5, J:COM
We are aware of reports specifically from Japan (including J:COM) plus other regions.
These show persistent failures reaching Steam Datagram (SDR) routing clusters – essentially the game cannot reach any relay, which is why you loop at sign-in
Support has already noticed that switching to a mobile hotspot lets stuck players log in again, just like you’re seeing, which is why this is treated as a routing path issue between certain ISPs (like J:COM) and the relay network, not your PS5 or Bungie account.
We are currently investigating these situations.
The failure is on the path between your ISP and the relay network (SDR), that’s why hotspot (different route) works and home ISP doesn’t.
Using an alternative connection (hotspot / different ISP) when you want to play, or
Working with J:COM and telling them:
Marathon/Steam Datagram traffic cannot reach any SDR relay cluster from your line, but works via mobile data;
This started around March 31, 2026 (Marathon 1.0.5.2) and continues in 1.0.6.
We are looking at improving both error handling and connectivity
Thank you for the update. However, simply telling a user to contact an ISP or use a hotspot for over 16 days is not an acceptable solution.
1. Cross-Platform Issue:
I must clarify that this connection failure is not limited to PS5; it is also occurring on the PC (Steam) version. This proves that the issue lies entirely within the routing between the Steam Datagram (SDR) network and the ISP (J:COM), rather than any local hardware settings.
2. Responsibility for Infrastructure:
Expecting a single customer to negotiate global routing policies with a major ISP is unrealistic. This is a structural failure that must be addressed between Bungie/Valve's network teams and the providers.
3. My Proposal for Cooperation:
I am willing to contact J:COM and push them from my side to help resolve this. However, I will only do this if Bungie provides a firm commitment that your engineering team is also actively engaging with Japanese ISPs to fix this cluster issue.
If you are taking this seriously and working on a structural fix for both PC and Console Runners, I will do my part as a user to provide J:COM with the necessary pressure. Please confirm if there is an ongoing dialogue between Bungie/Valve and the Japanese network infrastructure teams.
4. Request for ETA:
I have already missed over 2 weeks of season goals. I need a clear update on when the "improved connectivity" will be deployed.
I will continue my weekly reports until I can log back in from my home connection.
Best regards,
Aiwever
Войдите в службу, чтобы оставить комментарий.