I vaguely remember an issue of new account autoconfirm not working properly, a year or three ago (but, even more vaguely, also that it was then fixed), which might be related.
There is a friendly Toad who can (in extremis) fix particular cases manually and individually, of course. From experience, though it may have helped that I was not troubled by a widespread issue but just my own (and thus all the effort I put in to verify that I was really me could be considered without getting pleas from all over the place, swamping him).
But, as I always like to say (but don't always personally prepare for!), there's two sides to computer security. One is preventing those who shouldn't have access from getting access. The other is ensuring that those who should have access retain (or, when lost, quickly regain) access. These apply as much to how you handle your own logins, as much as the like of the B12 server handles that side's set of safes-and-safety-nets.
(I probably need to take this as a cue to go to my chosen "fallback" store of important things and see if it needs updating. But I won't say what form this takes as: 1) It's a possibly misguided and unnecessary attempt at "security through obscurity", an awful practise to rely upon; 2) I'd never presume that what works for me would work for anyone else. Just to say that there was an era when I kept active passwords and account details (mixed up and buried in decoy rubbish, in a way only I knew) on a handy scrap of innocuous paper, with the eventual problem of it becoming too scrappy and illegible before I got around to properly making a new 'innocuous scrap'. So I stopped doing that.)