Novelai Outage History
8 incidents recorded over the last 365 days, 6 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Novelai Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 2, 2026 | Login issuesWe're aware of issues affecting the servers and are actively looking into the cause. We will keep you updated and thank you for your patience in the meantime. | 2h 9m | Resolved |
| Nov 2, 2026 | V4.5 Full MaintenanceScheduled Maintenance | 3h 0m | Scheduled |
| Sep 18, 2026 | Emergency MaintenanceScheduled Maintenance | 105h 0m | Scheduled |
| Sep 17, 2026 | Errors on loginWe're aware of issues affecting the servers and are actively looking into the cause. We will keep you updated and thank you for your patience in the… | 13h 46m | Resolved |
| Aug 31, 2026 | E-Mail OutageWe are currently experiencing an email outage affecting all outgoing emails, including account registration confirmations, password resets, and account deletion notices. We are working to restore service as quickly as… | 1h 1m | Resolved |
| Aug 24, 2026 | Xialong and GLM instabilityThe team is aware of the generation issues currently affecting the service and is investigating the cause of them. We will keep you updated and thank you for your patience in the… | 7 min | Resolved |
| Aug 21, 2026 | V5 Full outageWe're aware of issues affecting the servers and are actively looking into the cause. We will keep you updated and thank you for your patience in the… | 7h 34m | Resolved |
| Aug 9, 2026 | Image generation instabilityWe're aware of issues affecting the servers and are actively looking into the cause. We will keep you updated and thank you for your patience in the meantime. | 41h 28m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Novelai incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Novelai Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Novelai acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Novelai outage in this window ran 4d 9h, against a mean recovery of 21h 46m. If you depend on Novelai in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.