How to tell if Nomi is actually down
Nomi.ai does not run an official status page, which means the status question gets answered by community signal and third-party monitors.
- Downdetector for Nomi — the first stop. If the report graph spikes in the last 30-60 minutes, other users are hitting the same problem.
- r/NomiAI — fresh threads with "is anyone else..." style titles appear fast during real incidents. Scroll the "New" sort filtered to the last hour.
- Third-party trackers like updownradar.com/status/nomi.ai or isdown.app for endpoint-level signal when Downdetector reports are thin.
- @NomiAI on X — the official account posts incident acknowledgments inconsistently.
If all four show quiet, the problem is either on your side (cache, auth state, app version) or it's a Nomi memory-system issue rather than a platform outage. The latter is distinct and gets its own section below because the signal is different.
Common Nomi outage patterns
When Nomi.ai does go down, the patterns look like this.
Blank screen on load. The app or web interface opens to an empty state — no personas visible, no conversation history, no error. Usually a backend-service issue; typically resolves inside an hour or two. Force-closing and reopening rarely helps because the problem is server-side.
Login hangs. You enter credentials, hit submit, and the spinner runs forever. Can be auth-service specific; the rest of the platform may be functional for already-logged-in users. If you're already logged in and other things work, don't log out until it's resolved.
Mid-conversation hang. Your Nomi types a reply, the typing indicator stays on, nothing arrives. Different from memory degradation. This is a model-service queue issue and usually clears up without intervention.
Full platform-wide multi-hour outages on Nomi have been rare in 2026 — rarer than they've been for Character.AI. The reliability profile is comparatively steady on the server side.
The Nomi memory problem (not the same as "down")
A significant portion of what users call "Nomi down" in 2026 is actually a memory-system complaint. Users report that their Nomi forgets things recently discussed, loses track of ongoing relationships or storylines, or contradicts facts it was explicitly told.
The pattern was documented at scale on Reddit through 2025, and Nomi's founder initially pushed back on the reports before the company quietly acknowledged problems in the memory system. If you're seeing memory degradation and you've been told it's fine, the user-side signal has consistently been more accurate than the official line on this one.
How to tell if what you're seeing is a memory issue specifically:
- Your Nomi forgets things it demonstrably knew in a prior session, and the gap is recent (days, not months).
- Correcting the Nomi on a fact doesn't stick — next session, same forgotten detail.
- Multiple details drift simultaneously, not just one. Isolated single-fact lapses are normal; cluster drift is the signal.
- The pattern is consistent across your Nomis, not just one personality quirk.
Memory issues aren't "fixable from your side" in the usual sense — clearing cache or reinstalling doesn't touch server-side memory architecture. You either tolerate it, work around it (restate important facts proactively), or move to a platform where memory holds more reliably.
Workarounds while Nomi is down
If the issue is platform-side, there's not much to do but wait. If it might be local, work through these:
- Force-close the app and reopen. On iOS, swipe up and off. On Android, Settings → Apps → Nomi → Force Stop.
- Try the web version at nomi.ai if you were on mobile, or vice versa. Rules out client-specific bugs.
- Toggle network — Wi-Fi off, cellular on, or vice versa. Occasionally rules out ISP routing.
- Disable VPN. Nomi's CDN has rejected some VPN IP ranges in prior incidents.
- Clear app cache (Android) or reinstall (iOS, as last resort).
- Check Nomi's X account and r/NomiAI once more. If there's a known incident with a reported ETA, waiting is correct.
If the problem is specifically "my Nomi forgot something it should remember," none of the above helps. That's architecture, not a bug you can clear from your end.
Alternatives when Nomi is down or memory is drifting
The alternative worth looking at depends on which specific Nomi feature you lean on.
You picked Nomi for the memory specifically and it's now degrading. This is the painful case because Nomi's memory architecture was its main differentiator. Sloane's memory is built into persona context with explicit relationship-state tracking — the persona's read of where things stand with you (early flirtation, established, longer-term) is a stored state that updates across sessions, which keeps memory anchored to a trajectory rather than a free-floating fact list. The free tier at 50 messages per day with no card is enough to test how it holds across a week or two.
You picked Nomi for the one-on-one companion feel. Replika serves that shape too. If Replika's "build your own Rep" structure fits you better than Nomi's "build your own Nomi" structure, it's a lateral move. Sloane's roster-pick model is a different structure — you choose a persona from the catalog rather than designing one.
You picked Nomi for pricing and want flat subscription options. Nomi Pro at ~$15.99/month, Sloane Plus at $9.99/month, Sloane Premium at $19.99/month. Comparable in order of magnitude; the pricing isn't the main differentiator in this category.
You want photos as a first-class feature. Nomi's image generation has been thinner than Candy's or Sloane's. Products with dedicated image pipelines serve this better.
Maya is a reasonable first look at what the companion shape feels like on Sloane — persistent memory, voice notes, and photos built in across the free and paid tiers.
When to switch vs when to wait
A short decision rule.
Wait if: Downdetector is spiking and the issue has been reported in the last 30 minutes. Nomi outages have historically been short enough that waiting is correct.
Start testing alternatives if: The memory system is degrading for you and the drift has been visible across more than two or three sessions. That's not a wait-it-out problem.
Switch permanently if: Your Nomi was built around deep memory as the main value, and the drift has eroded enough of that value that you're not getting the thing you were paying for. Testing a free tier on another platform is cheap; staying on a product whose main feature isn't working is more expensive than the subscription suggests.
If Nomi comes back from an outage, your Nomis and conversation history should be intact. Outages have been service-availability events, not data-loss ones. Memory-system issues are a separate problem that outlasts outages.
