- Service Status
- /
- NovelAI

Is NovelAI Down?
- NovelAI's status page
- Operational · read 5 hours ago, too long ago to count
- FlareWarden checks
- Website reachable · 8 of 8 regions · 211 ms
Right now
The verdict is the worse of these two. How we decide
NovelAI's status page
status.novelai.net · read · too long ago to set the verdict
| Component | Status |
|---|---|
| Cloudflare | Operational |
| Coreweave | Operational |
| Cloudflare | Operational |
| Coreweave | Operational |
| Cloudflare | Operational |
| Coreweave | Operational |
| Cloudflare | Operational |
| Cloudflare | Operational |
| Coreweave | Operational |
| Cloudflare | Operational |
FlareWarden checks
api.novelai.net from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 211 ms
- Checked
By region
- Amsterdam reachable, 136 ms
- Dallas reachable, 129 ms
- Frankfurt reachable, 189 ms
- Newark reachable, 55 ms
- Paris reachable, 184 ms
- Stockholm reachable, 226 ms
- São Paulo reachable, 647 ms
- Toronto reachable, 128 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 18 ms | 2 ms | 9 ms | 133 ms |
| Dallas | 71 ms | 1 ms | 6 ms | 128 ms |
| Frankfurt | 48 ms | 1 ms | 10 ms | 189 ms |
| Newark | 21 ms | 2 ms | 7 ms | 55 ms |
| Paris | 37 ms | 1 ms | 9 ms | 182 ms |
| Stockholm | 87 ms | 1 ms | 6 ms | 223 ms |
| São Paulo | 480 ms | 2 ms | 7 ms | 646 ms |
| Toronto | 80 ms | 1 ms | 7 ms | 128 ms |
History
Incidents NovelAI reported
from status.novelai.net
We don't have NovelAI's incident history yet.
NovelAI website availability
Measured by FlareWarden · api.novelai.net
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 246ms
Last 30 days
29-day clean streakMeasured by FlareWarden's own checks of api.novelai.net from multiple regions every 6 hours. NovelAI's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 29 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What NovelAI does
NovelAI is a subscription service from Anlatan for AI-assisted story writing and anime-style image generation. Writers co-write fiction with its text models, steering them with Memory, Author's Note and Lorebook entries, and artists generate images with NovelAI Diffusion models such as V4.5 and V5. Anlatan runs its own trained models on GPUs provided by CoreWeave, and the site installs as a web app on phones.
What an outage looks like
Failures are usually limited to one part of the service. Image generation can stall or slow down on a single model such as V5 or V4.5 Full while text generation keeps working, or one text model can fail on its own. Login errors have hit only some networks, and payment faults leave generation untouched. Seeds producing different images after a GPU migration is a documented change, not an outage.
What to do about it
Check status.novelai.net, which splits Website, Image Generation, Text Generation, Login, Payments and NovelAI Explore. Do not reset your password to get past a login error: NovelAI warns that a reset deletes your remotely stored stories, which it cannot recover. Download any generated images you want to keep before refreshing, since NovelAI does not save them. Billing and account problems go to support@novelai.net.
Is it down for everyone, or just you?
If this page says NovelAI is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
NovelAI outage FAQ
Will I lose my stories if NovelAI is down?
Should I reset my NovelAI password if I cannot log in?
Are my NovelAI images saved if the page reloads?
Why is NovelAI image generation failing when the site loads?
Is NovelAI down for everyone or just me?
How we measure this
- We request NovelAI's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where NovelAI publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of NovelAI itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.
Get alerted when NovelAI goes down
We check NovelAI every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring