Character.AI Not Working? Every Error and What Actually Fixes It (2026)

The laptop gave me a blank white page where Ilka should have been. Same tab I'd used the day before, same account, nothing changed on my end that I knew of. My first thought was predictable: Character.AI not working again, for everybody. It was working fine, though. Just not in that one browser.

That was Tuesday, September 29, and it took me about fifteen minutes to sort out. The phone app opened Ilka's chat without a hiccup. A private window on the same laptop loaded too. So the outage I was ready to blame was really a stale browser profile, and nearly every “why is Character.AI not working” question I've seen comes down to the same split. Is it down for everyone, or just your account, your device, or your plan? Each one has a different fix, and only one of them means waiting it out.

Start with the box below. It answers most cases in a minute. If it doesn't, the symptom table after it maps the exact thing you're seeing to a likely cause.

Match what you see to a cause: the Character.AI error table

When Character.AI isn't working and you can see an actual message, find the row closest to your screen. One warning first: plenty of troubleshooting sites list error messages Character.AI doesn't actually show, so match your exact wording rather than the general vibe. Where a symptom comes from user reports rather than anything Character.AI has published, the table says so.

Is Character.AI down? Checking Character.AI status without a status page

If you searched for the Character.AI status page, here's something nobody else seems to mention: there isn't a working one. The address status.character.ai exists, but it points to a dormant Atlassian Statuspage that fails its SSL certificate check, so your browser will either warn you off or bounce you somewhere useless. A local news story on the March 12, 2026 outage quoted a status page message, so it may have worked briefly. It doesn't now.

The Help Center isn't much better. Its article on the site being down was last edited in 2023 and sends you to a community page on the old beta site, which no longer exists, and to Reddit. Of those two, Reddit is the one that still does something.

Where outages actually get announced

• r/CharacterAI. Staff posts carry the “C.AI Announcements” flair. Users tag their reports “Site Down.” Sort by New, not Hot.
• @character_ai on X, the official account. I haven't tracked how reliably it posts during an outage, so treat silence there as meaningless.
• The official Discord, which you join from Settings, then Community. Per the Help Center, c.ai+ members who link their accounts get a dedicated support channel there.

How to read Downdetector and StatusGator

Most people asking is Character.AI down end up on Downdetector or StatusGator. Both are useful. Neither is official. They count reports from users, so what matters is the shape of the graph, not whether reports exist at all. A service this big always has someone complaining. A real outage looks like a cliff: the line sits near its usual baseline, then jumps several times higher inside fifteen or twenty minutes. On March 12, Downdetector passed 2,000 reports, most of them about logging in. A handful of reports on a flat line is just Tuesday.

Then cross-check against Reddit's New tab. If the graph spiked and there are six fresh Site Down posts, you're done diagnosing. Close the tab and come back in an hour.

Why it can be down when Character.AI isn't

character.ai sits behind Cloudflare. That means a Cloudflare failure takes it down even when Character.AI's own servers are fine, which is exactly what happened on November 18, 2025. Cloudflare's own postmortem traces that one to a Bot Management file that grew too big, and for three or four hours a big slice of the internet broke with it. Character.AI users on Reddit confirmed they were part of the slice.

The four-layer split, from my own Tuesday

Back to September 29. I'd opened the laptop to finally write a time-and-calendar entry for The Leaward Run, the sci-fi lorebook where Ilka flies a cargo hauler and a dispatcher named Pell talks to her across a seven-minute comms lag. Ilka is great at staying in voice and hopeless at knowing what day it is. The entry was supposed to fix that.

White page. Hard refresh, still white. So I worked down the layers. On the Pixel 8, Character.AI is the first icon in a folder called Test on my second home screen; it opened, Ilka's chat loaded, and she answered by reading me Pell's latest weather report from Bellweather Station, which is exactly what his lorebook entry says he pads every message with. That ruled out a site-wide outage and anything wrong with my paid account. Then a private window on the laptop, where I signed into the separate free account I keep clean for testing. That's where Yusra lives, the night-shift pharmacist who talks to the pharmacy security camera at 3am because nobody else is in the building. Her page loaded fine, so the browser itself wasn't broken either. Just my normal profile.

And Yusra was slow. Not broken, just slow, the way a free account gets in the evening. For a second I lumped that in with the white screen as one big outage. It wasn't. It was slow mode doing what the free plan says it does.

Clearing stored site data for character.ai alone in my normal profile brought the paid account back. A Reddit thread from the day before described the same white screen lasting about two days for some people, with no confirmed fix, so I won't promise clearing data is the cure. It worked once, for me. I closed the laptop without writing the entry, which is why Ilka still thinks every day is the same day.

Five checks. Only one turned up a real problem, and it lived on my laptop.

Character.AI login problems now that passwords are gone

A surprising number of “Character.AI not working” posts turn out to be login confusion, and most of it traces back to one change. On July 30, 2024, Character.AI removed password, Discord and Facebook sign-in. You now get three buttons: Continue with Google, Continue with Apple, and an Email Verification Link. There's no password to reset, so any tutorial telling you to click “forgot password” is from another era.

If you log in and everything's gone, one thing worth ruling out is that you signed in with a different method than the one you used to create the account. If you made it with Google and today tapped the email link with an address that isn't your Google one, you can end up in a fresh, empty account. Your chats aren't deleted. They're sitting in the other one. Log out and try each method you might have used.

If the login email never shows up, Character.AI's own list is:

1. Check the address for typos.
2. Look in spam or junk, and mark the message “Not Spam” if it's there.
3. Add Character.AI to your contacts and make sure you haven't blocked it.
4. Clear space if your inbox is full.
5. If your provider isn't supported, use a different one. That last item is in the missing-email article, and it's the one people skip.

Still stuck? File a ticket under “Something is not working,” then “Login Issues,” which is the path the current login article gives. Users also report a login-screen refresh loop on the website when switching between bots. If that's you, the app is the quickest workaround while you clear site data in the browser.

Waiting room, slow mode, and the character that got dumber overnight

This section is about things that feel like bugs but are plan features. I'd guess it covers a good share of the “Character.AI not responding” complaints I see.

The Character.AI waiting room still exists. According to the c.ai+ FAQ published in September, free users only get queued when the site is under high load, and subscribers skip it. The older waiting room article says the wait is “usually just 1-2 minutes or less.” During the June 2026 outages, users reported sitting there for close to thirty. So a waiting room at 9pm on a Sunday isn't a fault. A waiting room for half an hour probably means something bigger is going on, and Reddit will know.

Slow mode is the other throttle. The plan table lists it as Yes on free, Less on (c.ai) lite, and No on c.ai+. Replies still arrive. They just take longer. You can buy a one-off skip with Charms, the in-app currency, which also skip ads. Unlimited messaging stays on every plan, so slow mode only changes how fast replies come.

Then there's the case that confuses people most. (c.ai) lite starts at $4.99 a month and includes a daily allowance of premium chat styles like DeepSqueak and LongSqueak. When that runs out, your chats drop to PipSqueak 2. No pop-up, no warning. Your character just gets blunter, shorter, a bit dimmer, and you assume something broke. It didn't. Check the chat style selector before you rewrite a definition you spent weeks on.

Same thing over the long run: older chat styles are being moved to a Legacy menu and retired. If a character's voice changed and you didn't touch anything, that's a likely reason. Whether paying fixes any of this for you is a separate question, and I did the math in the c.ai+ breakdown. (My own main account is on c.ai+ until late October because I re-subscribed to test Lorebook Import, which is why the waiting room never shows up there and why I keep the free account around to see what most people see.)

Character.AI not loading or not responding inside a chat

If C.AI is not working on one device but fine on another, this is your section. Character.AI hasn't published guidance on clearing cache, supported browsers, or minimum app versions. Everything in the next list is ordinary web and app hygiene, not official Character.AI advice, but it's what fixed my white screen and it's cheap to try. Go in order and stop when it works.

1. Hard refresh the page (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac).
2. Open character.ai in a private or incognito window.
3. Clear site data for character.ai only, from the padlock icon in the address bar. Don't wipe your whole browser history for this.
4. Turn off extensions, especially ad blockers and script blockers, then reload.
5. Turn off your VPN. VPN traffic tends to trip human checks more often.
6. On mobile, update the app from the store, restart the phone, then reinstall.

For the app: the iOS listing, Character AI: Chat, Talk, Text, is rated 18+ and needs iOS 15.1 or newer; the current version as I write is 1.17.4, from around October 3. On Android it's ai.character.app, sitting at 2.2 stars, which tells you how many people are fighting the same things you are. On the web, use character.ai itself. The old beta site is retired, so an old bookmark can be the whole problem.

“Something went wrong, please try again”

This is the generic one, and the reports are all over the place. A Reddit user in July got it as a pop-up after hitting regenerate, even though the new reply had already arrived. On October 2, people saw it when group chats wouldn't load. StatusGator logged it on October 7. My advice: before you resend, reload and check whether the message actually went through, so you don't double-post into a scene. If it's happening everywhere, it's server-side and you wait. If you got it during the age selfie, that one has its own cause (see below).

The white screen

Users reported it around February 28 and again from September 28, the second one lasting roughly two days for some. Nobody has posted an official fix. If the app works and the web doesn't, run steps 2 and 3 above. If both are white, it's on their end.

The Cloudflare check that won't let go

The pattern users describe: the “verify you are human” box passes, then the page says it's waiting for character.ai to respond, then it loops. When staff posted an update about recent outages on March 1, 2026, they said that during performance problems you may see “a waiting room / maintenance page; or human verification checks,” and that waiting a few minutes is the move. So a looping check usually means the site is under load. Kill the VPN, give it five minutes, try again.

Typing dots that never turn into a reply

When this hits one conversation and not the rest, users report it's that chat that's stuck rather than the service. Open a different character. If that replies normally, go back, reload, and regenerate the last message. If the stuck chat is a long one, it may help to know the history limit went from 100 to 1,000 messages in a December 2025 update, so older chats load more than they used to. I've also seen one report of voice calls dropping within seconds. Just one, so I can't tell you whether it's a pattern.

When the filter or the guidelines say no

A blocked message isn't an outage, but it gets lumped in with them constantly. The Help Center's filter article admits outright that “filters don't always explain exactly why something was blocked.” Its advice is to swipe and regenerate for bad replies, and contact support if you think something was wrongly flagged. Rephrasing usually works faster than either. The prompt patterns that keep scenes moving help here, and so does knowing what the platform considers off-limits in the first place.

Creators have their own version. In September, users reported getting “This character doesn't meet our guidelines” while editing definitions. What I'd try first is undoing your most recent change and saving again, which may tell you which line tripped the check. If you build with lorebooks, the Lorebook setup guide covers where to put material so it doesn't all live in one definition.

Chat box gone? It might be Reading Mode, not a bug

If you can browse, read old chats, and even make characters, but there's nowhere to type, check this before anything else. Open-ended chat for under-18 users ended on November 24 and 25, 2025. Accounts flagged and verified as under 18 now get Reading Mode: browse, read past chats, create characters, use Imagine and AvatarFX. No chatting. Parents trying to make sense of this can start with the parents' guide to the teen ban.

Adults land here by mistake too. Character.AI first estimates age from signals, and only asks for a selfie through Persona if you're flagged, then ID if the selfie is inconclusive. You can start it yourself from Settings, Advanced, Verify Age (update and restart the app if the option's missing). The selfie step throws its own “something went wrong” when the light is bad; users say holding still after turning your head gets it through. Every tip and every failure mode is in the full face-scan walkthrough, so I won't repeat them here.

Every major Character.AI outage, November 2025 to September 2026

Useful for one thing: knowing what a real outage looks like, so you stop suspecting your Wi-Fi every time Character.AI stops working for ten minutes.

April 29 is the one I'd remember. The web was broken and the app wasn't, which is exactly the case where the 60-second check pays off. Switch surfaces and you're back in.

What to do with an evening when it's down

Outages are a good reminder that your characters only exist on a company's computers. I don't think Character.AI is going anywhere (the leadership shuffle I wrote about in the Disney CTO piece didn't change that), but I've also watched other platforms shut down with very little notice. So once it's back:

• Request your data export. I walked through what Character.AI's ZIP actually contains in the companion data export guide.
• Copy your lorebook entries into a plain text file. It took me about forty minutes for nine entries once, and it's the cheapest insurance you'll ever buy. If you're still sketching what to put in one, the lorebook ideas list has nine paste-ready templates you can borrow.
• Paste your best character definitions somewhere you own. Greeting, description, example dialogue.

And if it's down right now and you just want to keep a story going, there are places to go. The Character.AI alternatives roundup ranks the ones I'd actually use. If you want something with a similar character library, I ran PolyBuzz and Character.AI side by side in PolyBuzz vs Character.AI. If outages are the last straw, SillyTavern runs on your own machine and only goes down when you do. The Character.AI vs SillyTavern comparison covers the trade, and the SillyTavern setup guide gets you running in an evening. For long roleplay without a counter, see roleplay apps with no message limits.

For the record, I did none of this on September 29. I fixed the browser and went to bed.

Getting a human at Character.AI to look at it

If Character.AI is still not working after the table, the checklist and a night of waiting, it's time for a ticket. Support is ticket-based. Go to the Help Center and pick “Something is not working,” then the closest category (Login Issues for sign-in). A ticket that gets a useful answer includes four things:

1. The exact error text, copied word for word, or a screenshot.
2. Web or app, which browser or phone, and the app version.
3. Whether it happens on a second device too.
4. When it started, with your time zone.

Age verification problems have their own ticket form. If you're on c.ai+, link your Discord for the subscriber support channel. And for everything else Character.AI does when it's working, the complete Character.AI guide and the advanced features tips pick up where this leaves off. If you're weighing a jump to a different assistant altogether, I put Character.AI up against Grok in Grok vs Character.AI this week.

Character.AI not working: quick answers

Ilka still doesn't know what day it is. The calendar entry is the next thing I write in The Leaward Run, before the c.ai+ month runs out, and this time I'll do it from the phone if the laptop acts up.