Nabla
Nabla declares 3 subprocessors in its subprocessor list, which we last checked on Nov 21, 2026 (evidence). They are Google Cloud, Microsoft and Front. No published changes since we first read it on Oct 1, 2026.
Not listed by any tracked vendor.
Not loaded by any published homepage.
Subprocessors CSV of Nabla's subprocessors · Atom feed of Nabla's subprocessors DORA draft CSV of Nabla's subprocessors as declared by Nabla what's this? ·
3 third parties.
| Name | Purpose | Location | Listed since |
|---|---|---|---|
| Azure | Speech to Text Operations US & EU Regions | ||
| Front | Support Ticketing (No PHI) | ||
| Google Cloud | Data Hosting & Client Analytics Central Region (USA) Belgium (All Non-USA) |
Web TechnologiesCSV of Nabla's web technologies · Atom feed of Nabla's web technologies
Nabla's homepage made 85 requests to 14 domains, 6 services controlled by another company, and 2 domains not identified.
6 third parties by category: Advertising 1Cookie compliance 1CDN 1Other 3
hubspotonwebflow.comandreatuysuzian.com
3 tracked companies loaded by the homepage are not in Nabla's subprocessor list. A website can use a service without it processing customer data.
Service statusCSV of Nabla's status page incidents · Atom feed of Nabla's status page incidents
90 days agotoday
- 28 incidents in 90 days
- 10 major or critical
- 53 min typical time to resolve
| Began | Incident | Impact | Lasted |
|---|---|---|---|
| Degraded service performance | minor | — | |
| Degraded service performance | minor | 53 min | |
| Increased rate of websocket closures on transcribe API | no impact stated | — | |
| Slower transcription in US region | minor | — | |
| Encounter API failures | no impact stated | — | |
| Increased note generation errors in US region | no impact stated | — | |
| Increased rate of transcription errors in US region | no impact stated | — | |
| EHR launch failure | no impact stated | — |
Incidents per month
critical major minor no impact stated
Components affected
| Component | Incidents | Bar |
|---|---|---|
| API | 2 | |
| App | 2 |
As Nabla's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)
Incidents reported by Nabla's subprocessorsCSV of incidents reported by vendors Nabla lists · Atom feed of incidents reported by vendors Nabla lists
4 reported incidents in the last 30 days, by 1 of the vendors Nabla lists as a subprocessor.
A subprocessor list names a company, not the service an incident touched. This does not show that Nabla was involved.
| Date | Company | Incident | Impact | Lasted |
|---|---|---|---|---|
| | [gmail] Delays on calendar events synchronizing | minor | 1 h 1 min | |
| | [by_company_00015] Delays on channel imports for a subset of us-west-1 customers | minor | 5 h 9 min | |
| | Front mobile SSO login degraded | major | 4 h 21 min | |
| | [us-west-1] High API latency currently causing delays | minor | 1 h 25 min |
ChangesCSV of Nabla's changes · Atom feed of Nabla's changes
See the list as we read it on any date: Time machine
None since tracking began.