N
Outage recap · Nabla

Nabla outage — February 18, 2026

On February 18, 2026, Nabla had a reported incident on Nabla's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Nabla frontends broken when loading/displaying encounters.

major
Started
Feb 18, 9:21 AM EST
Resolved
Feb 18, 10:00 AM EST
Duration
39 min

Nabla's updates (4)

  1. identified · Feb 18, 9:21 AM EST

    We have accidentally deployed a non-backwards compatible change, which causes old frontend clients to break. We are in the process of deploying a hotfix to address this. In the meantime: - On web => reloading the page should immediately fix the issue. - On mobile apps => closing and restarting the app should trigger an update, immediately resolving the issue. - On chrome extension: no good workaround, will be resolved with our hotfix.

  2. identified · Feb 18, 9:21 AM EST

    We are continuing to work on a fix for this issue.

  3. monitoring · Feb 18, 9:53 AM EST

    Hotfix is deployed. All apps should be functional again. We are monitoring to ensure there are no more errors (even for old frontend clients) before closing this incident.

  4. resolved · Feb 18, 10:00 AM EST

    No more errors, closing this incident. Our apologies for the service disruption.

Updates are Nabla's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

AIDownCheck is not affiliated with Nabla. This recap summarizes incidents published on Nabla's official status page.