Realtime regression in non-English production voice agents: gpt-realtime-mini vs gpt-realtime-mini-2025-10-06

vb:

Hi!

Thank you for raising this.

You are probably already aware that you can still use gpt-realtime-mini-2025-10-06. You do not need to use the undated model slug, which currently points to the December snapshot.

For production systems, dated model versions are usually the better choice because they help keep behavior more consistent.

Since I do not see a deprecation notice for the older snapshot, using it seems reasonable here.

In this case, I would suggest staying on the older snapshot for now and waiting for a possible gpt-realtime-mini-2 release, or reviewing the Realtime model best practices here:

Thank you for the reply.

Just to clarify one important point: gpt-realtime-mini-2025-10-06 does appear to be listed on the official OpenAI deprecations page Deprecations | OpenAI API

On the current deprecations page, under the section for legacy GPT model snapshots, I see the following entry:

Shutdown date: 2026-07-23 Model snapshot: gpt-realtime-mini-2025-10-06 Substitute model: gpt-realtime-mini

So while we can still use the dated snapshot for now, the problem is that it appears to have a scheduled shutdown date, and the listed substitute model does not currently behave equivalently in our non-English/Romanian production voice-agent flows.

That is the core issue we are trying to surface: the dated snapshot is currently production-stable for us, but the documented replacement introduces worse language quality and more hallucination/confabulation against supplied business data.

For that reason, we are looking for either:

1. confirmation of whether this deprecation entry is accurate;

2. a migration path for production users affected by language-specific regressions;

3. or guidance on how to escalate this as a production-impacting model quality regression before the shutdown date.

We are happy to provide side-by-side transcripts showing the behavioral difference.