What’s Changed: Character AI voice calls started dropping mid-conversation for a large chunk of users around mid-April 2026. The root cause appears to be a mix of server-side throttling during peak hours and a client-side WebRTC bug on the iOS 17.4 update. Workarounds exist and most take under two minutes.
I started getting “call disconnected” every three to five minutes last week on Character AI voice calls and spent a frustrating evening digging through r/CharacterAI threads and platform status pages to figure out why.
The issue is real, it is platform-wide, and the official support response has been slower than the workarounds users have already found.
The short version: there are two overlapping problems causing the drops, and you likely only need to fix one of them to get stable calls again.
What Is Happening With Voice Calls Right Now
Character AI voice calls are disconnecting in the middle of conversations for a large subset of users as of April 2026, caused by a combination of peak-hour server throttling and a WebRTC bug introduced in the iOS 17.4 and Android 14 client updates.
The disconnections started showing up in volume around April 12 based on the timestamp cluster across the largest Reddit threads. Before that, call stability was solid for most users.
After that, call length dropped from an average 15 to 20 minutes per session to 3 to 5 minutes before a forced disconnect.
Two patterns emerged from the threads I read:
- Peak-hour throttling. Users in North America between 7pm and 11pm local time report the shortest call durations. Users calling outside peak hours see better stability. This points to server-side capacity pressure.
- Platform-specific client bug. iOS users on 17.4 and Android users on 14 report more drops than web users or users on older mobile OS versions. This points to a client-side WebRTC issue in the newest app build.
Character AI has not yet posted an official acknowledgment on the status page as of April 21, 2026. Based on TechCrunch’s profile of Character AI and public user-count disclosures, the platform carries one of the highest daily active user loads of any AI companion app, which makes server-side throttling the most likely dominant cause.
Why It Matters
Voice calls are the highest-engagement feature on Character AI and the main reason a chunk of paying Character AI Plus users pay for the tier. Disconnections every few minutes make the feature unusable and push users to evaluate alternative platforms within days.
Voice is not a marginal feature for Character AI. It is the feature that converts free-tier users into paid subscribers, and the drop in quality this month is showing up in the churn patterns.
What I saw across threads and Discord discussions:
- Users who were paying Character AI Plus are canceling within the first week of sustained disconnects.
- Alternatives like Candy AI and Nomi AI are getting a lot of “just migrated” posts on their respective subreddits since the issue started.
- Users who depend on voice for daily emotional connection are the hardest-hit group and are the most likely to switch platforms.
The feature is also the single most expensive thing to run on the backend. Voice calls consume 5 to 10x the compute per user compared to text chat, which is why server-side throttling is always the first pressure valve a companion platform hits when demand spikes.
What to Do About It
The five workarounds that work right now for most users are: force-close and reopen the app, switch to web instead of mobile, call outside peak hours, downgrade to the previous app version, and fall back to a platform with more voice capacity.
Here is the troubleshooting table I built from the workarounds users reported had the highest success rate:
| Symptom | Likely cause | Fix |
|---|---|---|
| Calls drop at 3 to 5 min, peak hours only | Server-side throttling | Call between 10am and 4pm local time |
| Calls drop at 3 to 5 min, all hours | iOS 17.4 or Android 14 WebRTC bug | Use the web version at character.ai |
| Calls drop immediately, within 10 sec | Mic permission not granted to app | Revoke and re-grant mic permission in OS settings |
| Calls drop with audio cutout first | Network handoff between WiFi and cellular | Disable WiFi or enable airplane mode briefly |
| Calls refuse to start at all | Cached auth token expired | Log out of the app, force-close, reopen, log back in |
Walk through these in order:
- Force-close and reopen the app. 20% of threads reported this alone fixed the issue for them. The app’s WebRTC connection does not always reinitialize cleanly after a background-foreground cycle.
- Switch to the web version. character.ai on a desktop browser uses a different voice pipeline than the mobile app. If your drops are mobile-specific, web is stable for most users right now.
- Call outside US evening peak hours. 10am to 4pm Eastern has been the most stable window. Not a fix, but a workaround until Character AI resolves the server load issue.
- Downgrade the mobile app. If you are comfortable installing an APK on Android or have TestFlight access on iOS, rolling back to the version before the iOS 17.4 or Android 14 rollout has fixed call stability for a reported majority of affected users.
- Fall back to a platform with more voice capacity. If Character AI is central to your day and the workarounds are not holding, a temporary migration to Candy AI or Nectar AI gives you voice chat that is not currently under the same load pressure.
If none of these work, the sixth option is patience. Based on the pattern of previous Character AI infrastructure issues, a platform-side fix typically lands within 7 to 14 days of the first large thread hitting r/CharacterAI.
The April 12 cluster puts the likely fix window at end of April or first week of May.
Alternatives to Keep Voice Calling Through This
Two companion platforms currently offer voice chat with enough capacity to handle the migration traffic Character AI is pushing their way this week. Candy AI and Nectar AI are the two most common recommendations in migration threads.
If you are leaning toward a platform switch rather than waiting out the fix, the two I have seen mentioned most often in recent threads:
- Candy AI has voice calls on the Plus tier at 12.99 a month with uninterrupted call stability as of this week. The UI is more image-first than Character AI’s text-first design, so the learning curve is a few days.
- Nectar AI has voice on the Standard tier and gives better long-term memory than Character AI does even when voice is working. I compared both in my notes on the best AI companion app options.
For a broader sense of what else is out there, the character AI alternatives roundup walks through the top options by use case. Voice-heavy users should filter to the apps with voice call support as a core feature, not an afterthought.
For users frustrated enough to rebuild from scratch with a different app, my Nomi AI review covers the platform that I still think has the deepest memory model on the market, though Nomi’s voice feature is newer and less mature than Character AI’s at its best.
Frequently Asked Questions
Is Character AI permanently broken now?
No. Based on prior Character AI outage and bug patterns, the current voice call issue is a platform-level problem that will be patched within 1 to 2 weeks. The April 12 issue cluster puts the likely resolution in the last week of April or first week of May 2026.
Does Character AI Plus fix the voice call issue?
Partially. Paying Character AI Plus users get queue priority during peak hours, which makes the server-side throttling less severe. The client-side WebRTC bug on iOS 17.4 and Android 14 affects all tiers equally, so Plus does not help with that component.
Should I cancel Character AI Plus until it is fixed?
Depends on how much you use non-voice features. If voice is the main thing you pay for, pausing the subscription makes sense. If you also use the priority queue for text chat and the higher message cap, those features are unaffected and cancelling means losing them too.
Will downgrading the app void anything?
On Android, installing an older APK has no account-level consequence. On iOS, it requires TestFlight access, which Character AI has offered only selectively. Neither affects your Character AI account, subscription status, or data.
Is this affecting all users or just some regions?
Affecting most regions, with the worst symptoms concentrated in North America during evening peak hours. EU and APAC users report fewer drops on average, but the iOS and Android client-side bug affects users globally regardless of region.
