Being routed to 5.2 and disallowed to verify my account as a Pro User

[am-will]

What issue are you seeing?

I am frustrated at this point. I am on day 3 of being routed to a model I don't want to use.

When I visit chatgpt.com/cyber, and click the button. Nothing happens. The backend is rejecting verification.

This is unacceptable on many levels.

1. I wasn't using it for anything nefarious
2. I wasn't alerted to the fact, but was silently re-routed
3. I wasn't told how to fix it, I had to find out on X
4. Even that didn't work.
5. I reached out to support, and they said its because I hadn't age verified.
6. Which I ALSO had to find out about after the fact. Why this isn't documented on Cyber is unknown.
7. Support has no other way to help me.

Support:

"If your verification attempt didn’t go through, please try again using a valid government-issued ID and ensure the photos are clear and well-lit. At this time, verification must be completed through the in-product flow, as there are no alternate verification methods available."

Well what am I supposed to do when your own verification method doesnt work? There's no alternatives.

I am not trying to Karen out here. I am one of your most ardent supporters, but I'm also extremely disappointed that you rolled this out in its current state without any recourse for paying customers. I've never been one to sugarcoat anything. All of the good will you're building up evaporates when you do stuff like this.

I understand that you're trying to be responsible with these powerful tools, I totally get that.

But silent rerouting, and no clear documentation or path to remedy is why I'm upset.

I know this is unintentional, and I'm quite sure, regrettable too. I think your team is amazing and I always shout you out on X. But I think I speak for everyone who was affected by this, that you simply cannot do this to your customers/supporters, and I would appreciate it if someone would help me on this.

I have reached out on discord, via support channels, and on X, and so far: not a single person has been able to help me.

VM890:261  POST https://chatgpt.com/backend-api/compliance/cyber_verification/persona/inquiries 403 (Forbidden)
reflect @ VM890:261
fetch @ VM890:481
apply @ VM890:281
reflect @ VM890:760
fetch @ VM890:980
apply @ VM890:780
c @ 2340486e-h114sxj33pi48cph.js:1
s @ 4813494d-il9ahiwx8ss4v3p0.js:2
(anonymous) @ 4813494d-il9ahiwx8ss4v3p0.js:2
t9 @ 4813494d-il9ahiwx8ss4v3p0.js:2
s @ 4813494d-il9ahiwx8ss4v3p0.js:2
(anonymous) @ 4813494d-il9ahiwx8ss4v3p0.js:2
n9 @ 4813494d-il9ahiwx8ss4v3p0.js:2
s @ 4813494d-il9ahiwx8ss4v3p0.js:2
(anonymous) @ 4813494d-il9ahiwx8ss4v3p0.js:2
(anonymous) @ 4813494d-il9ahiwx8ss4v3p0.js:2
fetch @ 4813494d-il9ahiwx8ss4v3p0.js:2
request @ 4813494d-il9ahiwx8ss4v3p0.js:2
safePost @ 4813494d-il9ahiwx8ss4v3p0.js:2
mutationFn @ 5e7688bb-nwj71fu61wq54bli.js:2
fn @ 2340486e-h114sxj33pi48cph.js:1
_ @ 2340486e-h114sxj33pi48cph.js:1
start @ 2340486e-h114sxj33pi48cph.js:1
execute @ 2340486e-h114sxj33pi48cph.js:1
await in execute
mutate @ 2340486e-h114sxj33pi48cph.js:1
mutate @ 4813494d-il9ahiwx8ss4v3p0.js:2
d @ 5e7688bb-nwj71fu61wq54bli.js:2
Mt @ 5e7688bb-nwj71fu61wq54bli.js:2
ue @ 5e7688bb-nwj71fu61wq54bli.js:2
Yu @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
Pr @ 2340486e-h114sxj33pi48cph.js:1
gE @ 2340486e-h114sxj33pi48cph.js:1
fv @ 2340486e-h114sxj33pi48cph.js:1
wd @ 2340486e-h114sxj33pi48cph.js:1
cv @ 2340486e-h114sxj33pi48cph.js:1
IE @ 2340486e-h114sxj33pi48cph.js:1
OE @ 2340486e-h114sxj33pi48cph.js:1
RE @ 2340486e-h114sxj33pi48cph.js:1
FE @ 2340486e-h114sxj33pi48cph.js:1
ec @ 2340486e-h114sxj33pi48cph.js:1

HE @ 2340486e-h114sxj33pi48cph.js:1
(anonymous) @ 2340486e-h114sxj33pi48cph.js:1

What steps can reproduce the bug?

It is just my account. Everyone else seems to be able to verify

What is the expected behavior?

No response

Additional information

No response

[github-actions]

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• Persona cyber verification precheck failed on Personal Pro account (403) #11883
• Verified Pro subscriber silently routed to GPT-5.2 instead of requested GPT-5.3-codex #11925
• I’m being incorrectly routed to GPT-5.2. I'm pro user and cyber verified #11920
• GPT-5.3-Codex being routed to GPT-5.2 #11842
• Model routing mismatch: requesting gpt-5.3-codex returns gpt-5.2-2025-12-11 (verified via SSE response.created) #11867

Powered by Codex Action

[khaled-wsa]

I verified my ID and it worked for a day or two, then I got silently routed back to gpt-5.2. Their classifier downgrades your whole account, not just the session, and it won't reset on its own. Been stuck like this for around 24 hours. Verification doesn't matter if the classifier just routes you back again. Really disappointing for a Pro ID Verified user.

[am-will]

I verified my ID and it worked for a day or two, then I got silently routed back to gpt-5.2. Their classifier downgrades your whole account, not just the session, and it won't reset on its own. Been stuck like this for around 24 hours. Verification doesn't matter if the classifier just routes you back again. Really disappointing for a Pro ID Verified user.

That's unfortunate 😕

I have no doubt they're working on this as a priority. They are a great team.

But I couldn't just pretend like I'm not really bothered by how this was handled either.

That way hopefully in the future, this doesn't happen again.

[aurindo10]

I’m also being routed to 5.2, and so far OpenAI hasn’t provided any solution that actually fixes the problem. I’m verified and I’m a Pro user. This is really bothering me because all my work is stalled.

[lmee]

I reviewed "Being routed to 5.2 and disallowed to verify my account as a Pro User" and read all comments before proposing a patch path.

Problem I see: I am extremely frustrated at this point. I am on day 3 of being routed to a model I have 0 interest in using, for which I am paying $200 for.
Root-cause hypothesis: an auth/session state mismatch across validation steps.
First patch plan: reproduce the flow with deterministic steps, inspect auth/session state transitions, patch validation around the wrong-code path, and add regression coverage for happy and failure flows.
If this aligns with maintainer expectations, I will post repro evidence first and then open the scoped patch.

[lmee]

I reviewed "Being routed to 5.2 and disallowed to verify my account as a Pro User" and read all comments before proposing a patch path.

Problem I see: I am extremely frustrated at this point. I am on day 3 of being routed to a model I have 0 interest in using, for which I am paying $200 for.
Root-cause hypothesis: an auth/session state mismatch across validation steps.
First patch plan: reproduce the flow with deterministic steps, inspect auth/session state transitions, patch validation around the wrong-code path, and add regression coverage for happy and failure flows.
If this aligns with maintainer expectations, I will post repro evidence first and then open the scoped patch.

[etraut-openai]

Thanks for reporting, and apologies for the inconvenience. We're aware of the issue and are actively working on a mitigation. I'll share updates as they become available.

[am-will]

Thanks for reporting, and apologies for the inconvenience. We're aware of the issue and are actively working on a mitigation. I'll share updates as they become available.

Thanks Mr Traut. I really appreciate everything you do.

[aurindo10]

The whole day waiting and still nothing. PLEASE @etraut-openai

[kcosr]

I'm commenting here since the other issues have been closed as duplicates. I also verified, got unblocked, and was blocked again while doing nothing nefarious or even security related. This was 3 days ago, also. I also contacted support but have not heard back. This is on the POC individual account my company purchased for me to demonstrate before we make a company-wide buying decision.

[bro4all]

Any update on this?