What’s Changed: Character AI has been hitting users with login loops, Cloudflare verification cycles, and white loading screens since the April 28 PipSqueak 2 forced rollout. The site has had at least 11 acknowledged or third-party-tracked outages between April 16 and May 6, with a 41-minute unacknowledged login outage on May 5 alone. The cause is not officially confirmed but the timing tracks with the model and infrastructure changes that landed in the same window.
If you tried to log into Character AI yesterday or this morning and got stuck on the Cloudflare “I am not a robot” check that just keeps repeating, or signed in only to get a white loading screen that never resolves, you are not the only one.
The issue cluster has been hitting different users at different times since April 28, and Character AI’s official status page is not catching most of it.
The same week that PipSqueak 2 became the forced default model also brought the worst run of login and access issues the platform has had this quarter. Users on r/CharacterAI have been posting “is the site down for anyone else?” almost daily.
The official status page acknowledges some of it, third-party trackers catch more, and a meaningful slice of the issues never get logged anywhere except the Reddit threads.
What Is Happening to Character AI Right Now
Users are hitting three failure modes since the PipSqueak 2 rollout: a Cloudflare verification loop that keeps asking “I am not a robot” without granting access, a white loading screen after login that never finishes loading, and chats that fail to load or send messages even when login works.
All three landed within the same 8-day window that PipSqueak 2 became the default.
The most concrete data comes from third-party trackers. Per Character AI’s official status history, the platform has logged 77 incidents across the last 90 days with a median duration of 23 minutes.
Several major user-reported outages, including the 41-minute login issue on May 5 starting at 8:06 PM PDT, never made the official status page at all. The third-party services like StatusGator and IsDown caught those.
The pattern in the last 30 days specifically:
| Date | Length | What broke | Acknowledged? |
|---|---|---|---|
| May 6, 12:06 AM UTC | 18-41 min | Login issues | No |
| May 5, 8:06 PM PDT | 41 min | Persistent login failures | No |
| May 5, 5:00-5:15 PM PDT | 10-15 min | “Investigating an issue” | Yes |
| May 2 | 25-26 min | “Investigating an issue” | Partially |
| May 1 | Multiple, 5-20 min each | Brief down periods | Some |
| April 29 | 14-25 min | “Investigating an issue” | Yes |
| April 28 | Two windows, 8-31 min total | Service issues (PipSqueak 2 rollout day) | Yes |
| April 26 | 40-60 min | Service down | Yes (5 min after IsDown caught it) |
The pattern that jumps out is that the official acknowledgement consistently lags third-party detection by 5 to 15 minutes, and login-specific outages frequently never get acknowledged at all.
The platform appears to track core API availability more aggressively than the auth and Cloudflare layer that most users hit first.
Why This Is Hitting Users Right After PipSqueak 2
The new model rollout, the Roar removal, the lorebook upgrade, and the memory architecture change all shipped in the same window. That is a lot of infrastructure churn for a platform that was already running close to capacity at 20 million monthly active users.
The auth and Cloudflare layer is the soft spot under that load.
Character AI does not officially confirm what causes each individual outage, but the timing pattern is hard to miss. Per Business of Apps platform data, Character AI sits at roughly 20 million monthly active users as of early 2026. Pushing a new core LLM, retiring four legacy models, and upgrading memory and lorebook to that user base in a single week is exactly the kind of move that strains every layer of the stack.
The way I read the outage cluster is that the user-visible failures are mostly auth and Cloudflare issues, not the model itself. PipSqueak 2 responses arrive fine when you can get past the login screen. The problem is the increased traffic from frustrated users repeatedly retrying their login, combined with the new safety verification flows that landed alongside the model change.
There is also the broader pattern from earlier in 2026. The platform had similar login chaos around the face scan age verification rollout when the new ID flow first landed. Big-bang infrastructure changes consistently produce a multi-week tail of auth issues. PipSqueak 2 is now in that tail.
What to Do When Character AI Login Loops on You
The fix order most users on the May 5 threads converged on: clear cookies for character.ai, retry in a private browser window, switch to mobile data if you are on home wifi, and as a last resort wait 30 to 60 minutes before retrying.
None of these is guaranteed but the combination clears the issue for most users within 15 minutes.
The five-step recovery checklist that consistently works:
- Clear cookies and site data for character.ai specifically. In Chrome: Settings → Privacy → Cookies → See all → search “character.ai” → delete. In Firefox: Settings → Privacy → Cookies → Manage Data → search character.ai → delete.
- Open a private or incognito window and retry. This bypasses cached Cloudflare verification tokens that may be the actual cause of the loop.
- Switch networks. If you are on home wifi, switch to mobile data. If you are on mobile, switch to wifi. Cloudflare’s reputation scoring sometimes flags certain IP ranges differently and a network switch resets the score.
- Disable any VPN or browser extensions that modify network requests. Privacy extensions and VPNs are the most common cause of repeated Cloudflare challenges.
- If none of the above work, wait 30 to 60 minutes. Most user-reported login outages in the May 5 cluster cleared within an hour. Continued retrying often makes the issue worse because Cloudflare flags the repeated attempts.
| Symptom | Likely cause | Fix |
|---|---|---|
| “I am not a robot” loop | Stale Cloudflare verification token | Clear cookies, open private window |
| White loading screen after login | App stuck mid-handshake | Hard refresh (Ctrl+Shift+R), clear cache |
| Logged out repeatedly | Session token expired during outage | Clear cookies, log back in once |
| “Sorry, something went wrong” on chat | API timeout, unrelated to login | Wait 5 min, refresh chat page |
| Cannot send messages but login works | Backend API throttled | Wait 10-15 min, do not refresh repeatedly |
Example scenario: Imagine logging in this morning and getting stuck on the Cloudflare check that keeps re-appearing.
Before: You retry the verification 6 times, each one fails. You start refreshing the page, which triggers more Cloudflare scrutiny, which makes the loop tighter. Twenty minutes in, you are still locked out and increasingly convinced your account is broken.
After: You stop retrying after the second failure. You clear cookies for character.ai, open an incognito window, and log in once. The Cloudflare check accepts the first verification, and you are in. Total time to resolution: 90 seconds.
The way I read the user threads is that the people who get stuck longest are the ones who keep refreshing and retrying. The Cloudflare reputation score punishes that pattern. Stopping, clearing cookies, and trying once from a clean state is the fastest path back in.
When the Fixes Are Not Enough
If clearing cookies, switching networks, and waiting an hour all fail, the issue is on Character AI’s side and you cannot fix it from your end. Switch to an alternative platform for the session and check back in a few hours.
The May 5 cluster lasted 41 minutes for some users and 10 minutes for others. Patterns of multi-hour lockouts have been rarer.
The honest assessment is that Character AI’s reliability has gotten worse through April and into early May. Per the official status page, 77 incidents in 90 days works out to almost one incident every 28 hours on average. For users who rely on Character AI as their primary roleplay platform, that frequency now justifies having a backup.
The closest matches for users who get locked out mid-session:
- Crushon AI has a similar character library style and rarely has the Cloudflare-specific issues. The free tier has daily message caps that get tight if you use it as your main platform, but it works fine as a fallback.
- Candy AI has tighter memory and longer character cards, with no recent major outage history. Better for users who want their backup to feel different from Character AI rather than identical.
- Janitor AI has its own outage history (the May 1-2 incidents were Janitor too), but the login layer is more reliable than Character AI’s right now.
A specific recommendation: Candy AI is the alternative I would point users to specifically because the platform stability has been steady through this same window when Character AI has been struggling. It is paid past the limited free tier, but the lack of forced model rollouts and the better memory consistency is the right tradeoff for users who want a backup that does not break the same way.
For deeper context on the Character AI options when login is working but the model is not behaving, the PipSqueak 2 fix breakdown covers the prompt-style hints that tame the most common rough edges, and the broader Character AI alternatives roundup covers the platforms users have been migrating to since the April rollout.
What Comes Next for Character AI Reliability
The honest answer is that the next 4 to 6 weeks are likely to keep producing intermittent outages while the PipSqueak 2 rollout stabilises. Big-bang model and infrastructure changes consistently produce a multi-week tail. After that, the official status page should catch up with reality and the auth-specific issues should fade.
Until then, expect at least one short outage per day on average.
What I would watch in the next two weeks:
- Whether the official status page starts acknowledging more of the user-reported outages. If yes, that signals improving observability and a more honest read on platform health. If no, third-party trackers remain the better source.
- Whether the Cloudflare verification loop frequency drops as the new auth flow settles. The pattern from the face-scan age verification rollout suggests this fades after about 3 to 4 weeks.
- Whether Character AI revisits the legacy model menu retirement on May 8. If user pressure forces them to keep Soft Launch or Goro available, that signals the platform is willing to walk back unpopular decisions and reduces churn.
- Whether c.ai+ subscribers see meaningfully better uptime than free users. Right now there is no clear pattern, but if subscriber outages drop while free-tier outages persist, that signals an intentional tier split.
Frequently Asked Questions
Why does Character AI keep showing the Cloudflare verification check?
The Cloudflare layer is repeating its verification because the platform’s auth flow is failing to complete the handshake on the first pass, often due to stale tokens, VPN traffic, or repeated rapid retries. Clearing cookies for character.ai and retrying once in a private window is the fastest fix.
Is Character AI down right now?
Check both the official status page and a third-party tracker like StatusGator. The official page misses many user-reported outages, particularly auth and login issues. If multiple users on r/CharacterAI are posting “is the site down” threads in the last 30 minutes and your retry attempts fail, it is almost certainly an outage even if not officially acknowledged.
How long do Character AI outages usually last?
The median outage in the last 90 days is 23 minutes, per the official status page. Some user-reported login issues lasted up to 41 minutes in the May 5 cluster. Multi-hour lockouts are rare. If you have been locked out for over 60 minutes, the issue is more likely on your end than Character AI’s.
Will the PipSqueak 2 rollout chaos calm down?
Probably yes within 4 to 6 weeks. The pattern from earlier 2026 rollouts (face scan verification, the Roar removal) suggests the platform takes 3 to 4 weeks to stabilise after a major change before the outage frequency returns to baseline. May should be rougher than April, June should be smoother than May.
Should I cancel my c.ai+ subscription if outages keep happening?
The current data does not show a clear gap between c.ai+ and free user outage rates, so cancelling does not improve your experience materially. If you are already paying and the platform is unusable, the better move is to keep the subscription paused and use an alternative platform during the rollout window. You can resume c.ai+ when stability returns.
Are these outages affecting all users or just some?
Both. Some incidents are platform-wide (the official acknowledged ones). Some are regional or auth-layer issues that hit a subset of users hard while others see no problem. If you can log in but a friend cannot, you may be seeing a Cloudflare reputation score difference rather than a true outage.
