ChatGPT voice keeps saying "Bad connection" and gets your words wrong: every cause and fix
Last verified: November 14, 2026
ChatGPT Voice is the hands-free mode where you talk to ChatGPT and it talks back in real time. Since around October 9, 2026, a large number of paying users on iPhone, Android, Mac, Windows and the web have described the same pattern: a "Poor connection" or "Bad connection" warning on a network that works fine for everything else, calls that drop and reconnect every few seconds, and transcripts in which ChatGPT answers words nobody said. On November 8, 2026, an OpenAI support agent replying on the official community forum wrote that there is a known Voice connection issue, which confirms that many of these failures start on OpenAI's side and cannot be fixed from your phone or router.
Not every warning comes from that issue, though. ChatGPT Voice streams live audio over a real-time connection, so a VPN, a company firewall, security software that filters traffic or a weak mobile signal can produce the same symptoms, and a wrong language setting can make the transcription look invented when the cause is much simpler. The quickest way to tell the two apart is to run the same call on a different network and, if you can, with a different ChatGPT account on the same device: if the problem follows your account across every network and device, you are most likely affected by the server-side issue, and the useful steps are reporting it with the right details and using a fallback until OpenAI resolves it. The reports come mostly from Plus and Pro subscribers, and several users say a free account on the same phone worked normally.
··········
WHAT THE CHATGPT VOICE CONNECTION WARNINGS LOOK LIKE.
The wording depends on the platform and the app language. Users on the official OpenAI community forum have quoted these messages and behaviors between October and November 2026, while using Live, the default voice mode that runs on GPT-Live-1.1 since mid-October.
........
What you see | Where it was reported | What usually happens next |
"Poor connection" | Web browsers, macOS desktop app, iPhone | ChatGPT keeps listening but replies late or to the wrong words |
"Bad connection" | Chrome and Firefox on Android | Speech is lost or replaced in the transcript |
Reconnecting message every 3-10 seconds | Android app (shown in the app language), Windows | The voice bubble shrinks and grows, context is lost after each reconnect |
Call never connects and times out | Native iPhone app | Same account works in Safari on the same phone |
Animation reacts to your voice, no answer | iPhone | Silence until you end the call |
Transcript shows sentences you never said | All platforms | ChatGPT answers an unrelated question |
........
The last symptom is the one that confuses people most. A transcript is the written record ChatGPT adds to the chat after a voice call, and when parts of the audio never reach OpenAI's servers, the speech recognition works with fragments. One Pro subscriber who measured a live session with Chrome's built-in WebRTC diagnostics reported that 40% to 46% of audio packets were being lost in some intervals while the connection itself stayed open, which matches the pattern of a call that looks connected but hears only pieces of each sentence. WebRTC is the browser technology that carries live audio between your device and the server.
··········
CHATGPT VOICE CONNECTION PROBLEMS: CAUSES, HOW TO CHECK AND FIXES.
The table lists the causes that are either documented by OpenAI, confirmed by OpenAI staff, or reported independently by several users. The step-by-step fixes follow in the next section.
........
Cause | How to check | Fix |
Known server-side Voice connection issue (confirmed by OpenAI support on November 8, 2026) | Problem on every network and device for one account; another account works on the same phone | Report it with app version, OS version, exact message and time; use text or Dictation meanwhile |
A broad ChatGPT or Voice outage | OpenAI status page shows an incident for ChatGPT or Voice mode | Wait for the incident to be resolved, then start a new call |
VPN, proxy or security software filtering traffic | Voice works on a phone hotspot or cellular data but fails on the usual Wi-Fi | Turn off the VPN; ask IT to allow the voice hosts and ports in OpenAI's network recommendations |
Weak or unstable network | Other devices on the same network also struggle with video calls | Move closer to the router, switch to cellular, avoid congested networks |
Native app problem on one platform | Voice works on ChatGPT.com in a browser on the same device | Update or reinstall the app, use the browser version until fixed |
Wrong main language for speech | Transcript is in the wrong language or full of look-alike words | Set your language under Settings, Speech, Main Language |
Microphone permission or input device | Other apps record you normally; ChatGPT shows no input | Allow microphone access for ChatGPT, try the built-in microphone instead of Bluetooth |
........
··········
HOW TO FIX CHATGPT VOICE "BAD CONNECTION" STEP BY STEP.
Work through the checks in this order, because the first two tell you whether anything on your side can help at all.
1. Open the OpenAI status page and look for an active incident affecting ChatGPT or Voice mode. OpenAI's own network troubleshooting article asks users to check it first. If an incident is open, nothing local will fix the call, so wait for the resolution and then start a fresh voice session.
2. Run the same voice call on a different connection. OpenAI recommends testing on a cellular hotspot instead of company or home Wi-Fi to find out whether the network is involved, and checking whether the problem affects only your device or every device on the network. If Voice works on the hotspot, the cause is on the network side and steps 3 and 4 apply.
3. Turn off any VPN, and pause security tools that inspect or proxy traffic. OpenAI's network article names Cisco Umbrella (formerly OpenDNS), Symantec Cloud Secure Web Gateway and PAN-DB Private Cloud from Palo Alto Networks as products that can filter ChatGPT requests, and it says allowlisting may be needed at the VPN or network security level.
4. On a company network, ask the IT team to allow outbound access for voice. OpenAI's network article states that its voice mode uses LiveKit, a real-time audio service, and that LiveKit requires specific hosts and ports to be allowed for outbound traffic; the exact host names and ports are listed in that article for administrators.
5. Test the browser version on the same device. Go to ChatGPT.com in Safari or Chrome, select the Voice icon in the prompt window and allow the microphone. In one long-running community thread, Voice timed out every time in the native iPhone app while working in Safari on the same phone and network, and an OpenAI support agent asked for the app version and iOS version to investigate.
6. Fix the language if the transcript looks invented. OpenAI's help article on wrong language detection says to open Settings, scroll to the Speech section and pick your language in the Main Language dropdown. Automatic detection can mishear accents and mixed-language speech as another language.
7. Check the microphone. On iPhone, open the iOS Settings app, find ChatGPT and make sure Microphone is on; on Android, open the app's permissions in system settings; in a browser, allow the site to use the microphone when asked. If you use a Bluetooth headset, try the device's built-in microphone once to rule out the headset.
8. If the call still drops on every network and device, try the same steps with a second ChatGPT account on the same device. When the second account works and yours does not, you have strong evidence that you are affected by the account-level problem that many subscribers describe, and the next section explains what to send to support.
··········
REPORTING THE CHATGPT VOICE CONNECTION ISSUE TO OPENAI SUPPORT.
When the problem follows your account, a precise report is the only lever you have. In the threads where OpenAI support did reply, agents asked for the same pieces of information, so including them from the start saves a round trip.
........
Detail to include | Where to find it |
ChatGPT app version | iPhone and Android: app settings, About; desktop: app menu |
Operating system version | iOS, Android, macOS or Windows settings |
Exact on-screen message | Screenshot of "Poor connection", "Bad connection" or the reconnecting banner |
Time and time zone of a failed call | Note it while testing |
Whether a call drops or never connects | Describe what the voice bubble does |
What you already ruled out | Other networks, other devices, browser vs app, a second account |
........
Send the report through the in-app help or the OpenAI help center, and remove personal details from screenshots, as the support agent requested in the forum. One reply from OpenAI support on November 8, 2026 asked whether the conversation stays connected or whether the user sees a "reconnecting" message, a sign that the support team distinguishes those two failure modes. Several subscribers say their tickets were first handled by an automated agent and that a new ticket was treated as a duplicate of an unanswered one, so keep follow-ups in the original case.
While you wait, Dictation is a practical fallback for anyone who mostly needs speech input. Dictation records what you say, lets you correct the transcription and sends it as text, so a lost word is visible before ChatGPT answers. Typing into the same chat keeps the conversation going when Voice is unusable.
··········
WHAT OPENAI HAS CONFIRMED AND WHAT ONLY USERS REPORT ABOUT CHATGPT VOICE.
The amount of verified information is small, and it helps to keep it separate from the theories circulating on the forum and on Reddit.
........
Statement | Status |
There is a known Voice connection issue | Confirmed by OpenAI support on the community forum, November 8, 2026 |
Voice mode depends on LiveKit hosts and ports being reachable | Documented in OpenAI's network recommendations article |
VPNs and filtering software can block ChatGPT traffic | Documented in the same article |
Wrong language detection is fixed in the Main Language setting | Documented in OpenAI's help center |
Problems began around October 9, 2026 and worsened after the GPT-Live-1.1 rollout on October 15 | Reported by several users, not confirmed by OpenAI |
The issue is tied to specific paid accounts | Reported by several users who saw free or second accounts work; not confirmed |
Deleting old conversations helps | One temporary improvement reported, problem returned; not recommended |
Downgrading or cancelling the subscription fixes Voice | Anecdotal single reports; not a documented fix |
Switching between Live, Advanced and Standard modes helps | Several users say it made no difference |
........
OpenAI has not published a root cause, an affected-user count or a timeline for a fix as of November 14, 2026, and its public release notes since October 1 contain no voice reliability entry. Users who measured their sessions report heavy audio packet loss with the connection itself staying up, which points to the audio path between the device and OpenAI's real-time servers, but the company has not said where the loss happens. Deleting chat history to try to clear the problem removes data you may want later, and the one user who tried it saw the issue come back.
··········
CHATGPT VOICE AFTER THE DECEMBER 11 SWITCH TO GPT-LIVE.
OpenAI has announced that Advanced and Standard voice will be retired in ChatGPT on December 11, 2026, leaving GPT-Live as the only voice system, as covered in our report on ChatGPT dropping Advanced and Standard voice for GPT-Live. For anyone hit by the connection issue, switching to an older mode was never a reliable workaround according to the forum reports, and after December 11 it will no longer be available at all. The steps above apply to GPT-Live directly.
After each app update, repeat a short test: one call on Wi-Fi, one on cellular, and one in the browser. If the warning disappears on all three, the server-side issue is likely resolved for your account; if it remains only on one network, the cause is local and the network steps apply. Plan limits, daily voice hours and setup on each platform are covered in our guide to ChatGPT Realtime Voice, its limits and fixes. A "Selected model is at capacity" banner shown before or during a call is a different, temporary capacity message, explained in our page on what "Selected model is at capacity" means in ChatGPT.
··········
CHATGPT VOICE "BAD CONNECTION": WHAT TO DO FIRST.
A "Poor connection" or "Bad connection" warning in ChatGPT Voice has two very different origins in November 2026. When it disappears on a phone hotspot, the cause is local, and turning off the VPN, getting the LiveKit voice hosts allowed on a managed network or moving to a stronger signal resolves it. When it follows one account across every network, device and browser while another account works, the cause is the Voice connection issue that OpenAI support acknowledged on November 8, and the effective steps are a detailed support report, keeping text or Dictation as a fallback, and testing again after each update.
Invented transcripts belong to the same picture. When audio packets are lost on the way to the server, the transcript is built from fragments; when the transcript is in the wrong language, the Main Language setting is the fix. Settings changes, reinstalling and switching voice modes have not helped the accounts affected by the server-side issue in any of the reported cases, so the time is better spent on the network test and the support report.
··········
FOLLOW US FOR MORE.
·····
DATA STUDIOS
·····
datastudios.org
