Nabla Outage History
8 incidents recorded over the last 365 days, 8 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 Nabla Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 1, 2026 | Degraded performances for Note GenerationBetween 8:35AM (ET) and 9:35AM (ET) Note generation suffered abnormally high rate of error. The issue was quickly identified as related to a software change that had a higher than expected impact on a database… | -205 min | Resolved |
| Sep 1, 2026 | Nabla service degradedThis incident is resolved | 46 min | Resolved |
| Aug 3, 2026 | Nabla mobile applications brokenThe hotfix is fully rolled out. Service is fully recovered according to our metrics. | 16 min | Resolved |
| Jun 3, 2026 | Nabla service degradedStable for several hours, closing. | 3h 50m | Resolved |
| May 6, 2026 | Increased transcription errorsThis incident has been resolved. | 24h 12m | Resolved |
| Apr 23, 2026 | Slightly degraded Nabla serviceOur service has been slightly degraded today from ~8:40AM EST to ~12:30pm EST. Symptoms: occasional HTTP 408 (timeout) & 500 (internal error) when contacting our API. These would typically result in some perceived… | 0 min | Resolved |
| Feb 18, 2026 | Nabla frontends broken when loading/displaying encounters.No more errors, closing this incident. Our apologies for the service disruption. | 38 min | Resolved |
| Jan 28, 2026 | Generalized service outageAll signals are back to green, making incident as resolved. | 3h 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 Nabla 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 Nabla 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 Nabla 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 Nabla outage in this window ran 1d, against a mean recovery of 4h 44m. If you depend on Nabla 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.