NabuCasa Outage History
13 incidents recorded over the last 365 days, 1 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 NabuCasa Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 23, 2026 | Remote Access ressources upgradeThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Jun 8, 2026 | Subscription service migrationThe migration is now complete for the vast majority of customers, who have full functionality restored in their Home Assistant Cloud account page — including updating billing information, changing subscriptions, and… | 500h 0m | Scheduled |
| Jun 8, 2026 | Account page deployment.The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jun 4, 2026 | Major services updateThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Feb 2, 2026 | Update remote access nodeThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Feb 2, 2026 | Update remote access nodeThe scheduled maintenance has been completed. | 30h 0m | Scheduled |
| Jan 21, 2026 | Updating remote access nodesThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jan 19, 2026 | Updating remote access nodesThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jan 10, 2026 | European remote-access partial outageWe have resolved the issue with remote-access in the European region. | 1h 45m | Resolved |
| Dec 16, 2025 | American and European remote-access nodes updateThe scheduled maintenance has been completed. | 4h 30m | Scheduled |
| Dec 11, 2025 | Asian remote-access nodes updateThe scheduled maintenance has been completed. | 1h 15m | Scheduled |
| Dec 4, 2025 | European remote-access nodes updateThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Dec 2, 2025 | European remote-access nodes updateThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
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 NabuCasa 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 NabuCasa 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 NabuCasa 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 NabuCasa outage in this window ran 20d 20h, against a mean recovery of 1d 18h. If you depend on NabuCasa 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.