Which address is the correct one ?
- 37.244.33.112 ?
- 37.244.57.10 ?
Whichever it is… it’s broken:
I don’t recall having that either… but I will be paying more attention.
1 Like
IP 37.244.33.32 worked… 3 times 6 times (lvl 88 to 93 incl.) in a row.
Need more keys… will be back.
Need a break… will be back later
That IP was very good to me… good solid connection and saved 6 completed GRifts in a row.
2 Likes
Should be the .112 one 
.10 seems to be another server for some other feature of the .exe
1 Like
Noted… thanks
1 Like
@QuisSeparabi:
IP 37.244.32.66 works… are you building some kind of lists/statistics ?
1 Like
A friend is compiling a little list, we got this so far:
37.244.32.23 OK
37.244.32.35 Not saving
37.244.32.46 Not saving
37.244.32.66 OK
37.244.32.80 Not saving
37.244.32.84 OK
37.244.32.87 Not saving
37.244.32.98: OK
37.244.32.18 Not saving
37.244.32.114 Not saving
37.244.32.143 Not saving
37.244.32.157: OK
37.244.32.158 Not saving
37.244.32.168 Not saving
37.244.32.182 Not saving
37.244.32.183 Not saving
37.244.32.187 Not saving
37.244.32.197 Not saving
37.244.32.229 Not saving
37.244.32.230 Not saving
37.244.32.246 Not saving
37.244.32.247 Not saving
37.244.32.249 OK
37.244.33.16 Not saving
37.244.33.19: OK
37.244.33.32 OK (?)
37.244.33.38: OK
37.244.33.43: OK
37.244.33.46: Not saving
37.244.33.47: OK
37.244.33.77 OK
37.244.33.80: OK
37.244.33.82: OK
37.244.33.94 OK
37.244.33.101: Not saving
37.244.33.102: OK
37.244.33.109: Not saving
37.244.33.111 Not saving
37.244.33.114: OK
37.244.33.119: OK
37.244.33.122: OK
37.244.33.124: OK
37.244.33.135 OK
37.244.33.140: OK
37.244.33.141 Not saving
37.244.33.149: Not saving
37.244.33.151 Not saving
37.244.33.153: OK
37.244.33.158: OK
37.244.33.172 Not saving
37.244.33.174: OK
37.244.33.177: Not saving
37.244.33.183: OK
37.244.33.189: Not saving
37.244.33.205 Not saving
37.244.33.206 Not saving
37.244.33.216 Not saving
37.244.33.220: OK
37.244.33.242: OK
Of course this is totally meh compared to the bug just getting fixed, which is long overdue imho. It’s really important to understand that there are several of the EU servers not working right, and this is probably just one of the things not working right. I would prefer to not find out which other problems could occur on this semi-defective servers. They need another maintenance, and that as soon as possible.
5 Likes
Just did a 107 in around 13.30 on solo Necro on Europe but it doesn’t show up.
Grrrrrrrrrrrrr!
Quite, and for how long?
That’s excellent investigation / feedback.
It’s just a shame that it’s end-users that are doing this instead of Blizzard.
EDIT
Did some 2-man runs this morning…
Me on WW/Rend Barb, Other on Frenzy Barb, GR119, Not recorded
Me on Frenzy Barb, Other on Necro, GR122, Recorded
Me on Frenzy Barb, Other on Necro, GR123, Recorded
Me on Frenzy Barb, Other on Necro, GR124, Recorded
Me on Frenzy Barb, Other on Necro, GR125, Recorded
Neither of us were in a clan, so no clan chat stuff to cloud the issue. The only difference between the first run, which didn’t record, and the subsequent ones that did, was the heroes we were on. I guess it’s possible that when we went back to hero select, that might have changed which server we were hosted on when we went back in.
2 Likes
I don’t know if this is adding value, and the details are “low quality level anecdotal” …based on on my unreliable memory.
When I first noticed that the personal bests were not being updated, ca. three weeks ago, I remember (?) non-recording vs recording of PB GR - within a game - when switching the loadout of my Hardcore Witch doctor ( Ost#2137 - character “Evee” ) between a LoD build and a Helltooth pet build. If I recall correctly - and again, apologies for vagueness, but my memory is botched - I could record new PB using LoD, but not record PB updates with the Helltooth loadout, and reproduce the non-recording switching back and forth between the builds.
I switched the saved builds using Armory. I play mostly solo, and the loadout-switching was definitely soloing. I switched to a third build, pushed and can no longer attempt to reproduce. With my current build I have had both non-recording and recording, between two different sessions on the same day, same loadout.
i can confirm 37.244.33.43.
saved a record for me
1 Like
confirmed, 37.244.33.140 saved record.
I logged in/out until i get one server described above
1 Like
Thanks for the detailed list. Great and useful information until a fix comes along. I can confirmed that testing the following IP range listed in forum the results of my PB records is registered or not registered as stated.
37.244.33.114 good (confirmed)
37.244.33.101 bad (confirmed)
37.244.32.153 good (confirmed)
These were not on the list but in the yellow upgrade test ,my loot appears in clan chat on these IP:
37.244.33.77 good
37.244.32.23 good
37.244.32.230 bad
37.244.32.249 good
1 Like
Yes every time you logout and you start new game, it will change server. So since both of you logged out to switch char and back in game you got another server
2 Likes
Confirmed… even if you don’t change hero, it will change server if you quit the game and start another one.
2 Likes
Not on the list…
37.244.33.32 - OK
That one was weird… The first time I beat my record, I got the notification and bloodshard increase, but not the personal record. The second time, I got it all… notification, bloodshard increase AND personal record. Don’t know… weird !
Playing season solo.
1 Like
37.244.33.141 - Doesn’t work.
1 Like
Are you guys going to fix the Leader boards or not??? Easy answer yes or no?? No use at this stage to even push solo, i stil would have had rank 1 with my sader clear and going for the 140 solo now but doesn’t help i do that before bug is fixed. And its tiresome to keep on waiting, so please just give a response so we know if seasons over or not.
1 Like
37.244.33.94 - OK
2 Likes
37.244.32.229 - Doesn’t work 
37.244.32.35 - Doesn’t work
37.244.33.172 - Doesn’t work
2 Likes