Nulab Outage History
12 incidents recorded over the last 365 days, 12 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 Nulab Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 4, 2026 | 【Nulab Apps / Backlog / Cacoo】Organization data sync operations, such as adding and removing users or teams, are currently failing to process. | 8h 10m | Resolved |
| Oct 28, 2026 | Scheduled Maintenance (Database engine upgrade) | 2h 3m | Resolved |
| Oct 22, 2026 | Scheduled Maintenance (Database engine upgrade) | 2h 1m | Resolved |
| Oct 20, 2026 | Scheduled Maintenance (Database engine upgrade) | 2h 4m | Resolved |
| Oct 20, 2026 | System maintenance and end of support for direct access from Microsoft Office | 41 min | Resolved |
| Oct 14, 2026 | Scheduled Maintenance (Database engine upgrade) | 2h 1m | Resolved |
| Oct 8, 2026 | System maintenance and end of support for direct access from Microsoft Office | 33 min | Resolved |
| Oct 5, 2026 | 【Backlog】【Cacoo】【Nulab Flowbase】Change your plan or start a new trial are currently unavailable. | 3h 9m | Resolved |
| Oct 5, 2026 | 【Backlog】Webhook are currently unavailable. | 9h 55m | Resolved |
| Sep 15, 2026 | System maintenance and end of support for direct access from Microsoft Office | 32 min | Resolved |
| Sep 5, 2026 | Maintenance notice | 1h 0m | Resolved |
| Aug 25, 2026 | System maintenance and end of support for direct access from Microsoft Office | 37 min | 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 Nulab 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 Nulab 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 Nulab 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 Nulab outage in this window ran 9h 55m, against a mean recovery of 2h 44m. If you depend on Nulab 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.