Forum Discussion

Community Manager

2 years ago

Solved

AT&T network - "Unable to load persistence data" - Season 5

Hi all, Please only post in this thread if you're experiencing the "Unable to load persistence data" error while trying to connect to the Battlefield 2042 servers if you have AT&T as your network...

technical issues

EA_Leeuw
2 years ago
Hi everyone,

Since Season 5 is coming to a close, I'll be locking this thread.

If you continue to experience the AT&T network - "Unable to load persistence data" issue during Season 6 as well, please create a new thread.

Thank you.

*Previous accepted solution.

WhiskyDoc

2 years ago

ATT Fiber customer here. I have tried most nights for over a week now and have only managed to get online once (and that was only after doing a clean install - the very next night it was back to the same error again). Power cycling modem and PS5 don't seem to help. All other games, even online ones, behaving normally.

There's some variation in the error codes that display, but tonight's was the usual one which is the following weirdly long string of numbers:

15: 136006S: 136003S: 136001S: 136002S:-7A

Super annoying - please fix!

EA_Leeuw

Community Manager

2 years ago

Hi all,

Please read the following carefully.

For the players still experiencing this issue - and with AT&T as their ISP -, could you please perform a diagnostics via your AT&T router and DM me a screenshot of the results?

!!WHEN SHARING YOUR DIAGNOSTICS RESULTS, PLEASE ALSO MENTION YOUR OWN PHYSICAL IP ADDRESS (which you can find via whatismyipaddress.com)!!

You can run the diagnostics this way (you need a PC for this that is on the same network as the network you're playing on):

Via your AT&T-provided router admin panel:

Open a web browser and go to http://192.168.1.254/,
Login to the admin panel of your router,
Go to the Diagnostics tab > Troubleshoot,
Where it says "Test Internet Access", enter the following and click on Traceroute:

kingston-prod-wgw-envoy.ops.dice.se

Let it finish all hops & take a screenshot,
Please send me a screenshot of the results via a DM here on AHQ.

Here you can see where you can find the Diagnostics > Troubleshoot tab in the admin panel of your router:

Via your Windows Command Prompt (CMD)

Open your Windows Command Prompt by going to Windows Start Search and typing "cmd",
Enter the following and press enter:

tracert kingston-prod-wgw-envoy.ops.dice.se

Let it finish all 30 hops & take a screenshot,
Please send me a screenshot of the results via a DM here on AHQ.

*While the results indeed show some IPs, this information is only being used as troubleshooting for AT&T.

Thanks in advance.

LigamentousCree
2 years ago
what are we looking for that tells us something isnt right?
Sol4rSp4rk
2 years ago
@EA_Leeuw I've sent you two DMs: one with a traceroute while connected to my AT&T ethernet, and another when connected to my phone's hotspot provided by Verizon. Hope this helps.
nola_ros
2 years ago
I have a screenshot of our AT&T test bu I am unable to send it to you via DM. Please DM me and I can send to you. It has been working for a couple of days but now getting the same persistent data error. My husband and I are on the same network and he can get it in, but I can't. He is playing on PS5 and I am on PS4.
- FireSnake2599
  2 years ago
  @nola_rosI was also not able to PM until I created my first forum post. You should be able to private message him now. Just click on his profile and you should see an envelope next to his name. Click on that and you should be good to go!
  - nola_ros
    2 years ago
    Thanks!
hballard94
2 years ago
Error code attached. Cannot connect as of 12:01AM EST
traceroute to kingston-prod-wgw-envoy.ops.dice.se (52.215.43.89), 30 hops max, 38 byte packets
1 23-115-64-1.lightspeed.knvltn.sbcglobal.net (23.115.64.1) 1.774 ms 0.739 ms 0.821 ms
2 99.17.140.210 (99.17.140.210) 0.892 ms 1.101 ms 0.885 ms
3 * * *
4 * * *
5 * * *
6 32.130.16.203 (32.130.16.203) 13.392 ms 11.572 ms 12.419 ms
7 192.205.33.42 (192.205.33.42) 11.933 ms 11.722 ms 9.796 ms
8 atl-bb2-link.ip.twelve99.net (62.115.143.236) 9.288 ms 10.857 ms 10.894 ms
9 ash-bb2-link.ip.twelve99.net (62.115.137.132) 23.477 ms prs-bb1-link.ip.twelve99.net (62.115.112.243) 103.881 ms rest-bb1-link.ip.twelve99.net (62.115.138.70) 29.394 ms
10 prs-bb1-link.ip.twelve99.net (62.115.112.243) 107.825 ms prs-b3-link.ip.twelve99.net (62.115.118.59) 106.131 ms prs-bb1-link.ip.twelve99.net (62.115.112.243) 106.075 ms
11 * prs-b3-link.ip.twelve99.net (62.115.118.59) 106.066 ms 108.144 ms
12 * amazon-ic-367021.ip.twelve99-cust.net (62.115.42.69) 105.481 ms 105.608 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
- EA_Leeuw
  Community Manager
  2 years ago
  Please do NOT post in this thread if you do NOT have AT&T as your ISP.
  
  If you have a different ISP, please post in this thread.
  
  Thank you.
  - EA_Leeuw
    Community Manager
    2 years ago
    Update Aug. 2, '23:
    
    Big thanks for providing us with all the examples/reports! You're all truly amazing. We'll be sharing these reports with AT&T & AWS in hopes they can pinpoint the root cause of the issue.
    
    For now, we don't require any new diagnostic results. If that changes, rest assured, we'll keep you informed.
    
    And if there are any updates to share with you, we'll make sure to do so promptly!
    
    - EA_Leeuw
    
    Edit:
    
    Just wanted to add that while the Battlefield Comms Twitter channel just released this tweet, this is not related to the AT&T issue that this thread is about.