Nabla

nabla.com

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.

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.

NamePurposeLocationListed 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.

Advertising (1): Google CloudCookie compliance (1): EnzuzoCDN (1): jsDelivrOther (3): JavaScript libraries: Webflow; usually detected as JavaScript libraries: bunny.net; Page builders: Finsweet

6 third parties by category: Advertising 1Cookie compliance 1CDN 1Other 3

Third parties 6 · 78 requests
Webflow Webflow 1.6.0 jQuery 3.5.1 55% of the page's requests 47
Google Cloudsubprocessor DoubleClick Floodlight Google Analytics Google Tag Manager YouTube 19% of the page's requests 16
jsDelivr jsDelivr 12% of the page's requests 10
Enzuzo Enzuzo 2% of the page's requests 2
bunny.net b-cdn.net 2% of the page's requests 2
Finsweet Finsweet 1% of the page's requests 1
Unknown 2 · 3 requests

hubspotonwebflow.comandreatuysuzian.com

First party 1 · 4 requests
Nabla Cloudflare GSAP 3.15.0 HTTP/3 Open Graph Swiper Webpack 5% of the page's requests 4

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

Aug 24: no incident reportedAug 25: no incident reportedAug 26: no incident reportedAug 27: no incident reportedAug 28: no incident reportedAug 29: no incident reportedAug 30: no incident reportedAug 31: no incident reportedSep 1: 1 incident (1 minor)Sep 2: no incident reportedSep 3: no incident reportedSep 4: no incident reportedSep 5: no incident reportedSep 6: no incident reportedSep 7: no incident reportedSep 8: no incident reportedSep 9: no incident reportedSep 10: no incident reportedSep 11: no incident reportedSep 12: no incident reportedSep 13: no incident reportedSep 14: no incident reportedSep 15: no incident reportedSep 16: no incident reportedSep 17: no incident reportedSep 18: no incident reportedSep 19: no incident reportedSep 20: no incident reportedSep 21: no incident reportedSep 22: no incident reportedSep 23: no incident reportedSep 24: no incident reportedSep 25: no incident reportedSep 26: no incident reportedSep 27: no incident reportedSep 28: no incident reportedSep 29: no incident reportedSep 30: no incident reportedOct 1: 1 incident (1 minor)Oct 2: no incident reportedOct 3: no incident reportedOct 4: no incident reportedOct 5: no incident reportedOct 6: no incident reportedOct 7: no incident reportedOct 8: no incident reportedOct 9: no incident reportedOct 10: no incident reportedOct 11: no incident reportedOct 12: no incident reportedOct 13: no incident reportedOct 14: no incident reportedOct 15: 24 incidents (5 critical, 5 major, 3 minor, 11 no impact stated)Oct 16: no incident reportedOct 17: no incident reportedOct 18: no incident reportedOct 19: no incident reportedOct 20: no incident reportedOct 21: no incident reportedOct 22: no incident reportedOct 23: no incident reportedOct 24: no incident reportedOct 25: no incident reportedOct 26: no incident reportedOct 27: no incident reportedOct 28: no incident reportedOct 29: no incident reportedOct 30: no incident reportedOct 31: no incident reportedNov 1: no incident reportedNov 2: no incident reportedNov 3: no incident reportedNov 4: no incident reportedNov 5: no incident reportedNov 6: no incident reportedNov 7: no incident reportedNov 8: no incident reportedNov 9: no incident reportedNov 10: no incident reportedNov 11: no incident reportedNov 12: 2 incidents (2 minor)Nov 13: no incident reportedNov 14: no incident reportedNov 15: no incident reportedNov 16: no incident reportedNov 17: no incident reportedNov 18: no incident reportedNov 19: no incident reportedNov 20: no incident reportedNov 21: no incident reported

90 days agotoday

  • 28 incidents in 90 days
  • 10 major or critical
  • 53 min typical time to resolve
BeganIncidentImpactLasted
Degraded service performanceminor—
Degraded service performanceminor53 min
Increased rate of websocket closures on transcribe APIno impact stated—
Slower transcription in US regionminor—
Encounter API failuresno impact stated—
Increased note generation errors in US regionno impact stated—
Increased rate of transcription errors in US regionno impact stated—
EHR launch failureno impact stated—

Incidents per month

0 15 30 Dec 2025: 0 incidents Jan 2026: 1 incident (1 critical) · typical time to resolve 3 h 28 min Feb 2026: 1 incident (1 major) · typical time to resolve 38 min Mar 2026: 0 incidents Apr 2026: 1 incident (1 minor) · typical time to resolve 1 min May 2026: 1 incident (1 minor) · typical time to resolve 24 h 12 min Jun 2026: 1 incident (1 major) · typical time to resolve 3 h 50 min Jul 2026: 0 incidents Aug 2026: 1 incident (1 critical) · typical time to resolve 16 min Sep 2026: 1 incident (1 minor) · typical time to resolve 46 min Oct 2026: 25 incidents (5 critical, 5 major, 4 minor, 11 no impact stated) Nov 2026: 2 incidents (2 minor) · typical time to resolve 53 min Dec 2025Jan 2026Feb Mar Apr May Jun Jul Aug Sep Oct Nov

critical major minor no impact stated

Components affected

ComponentIncidentsBar
API2
App2

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.

DateCompanyIncidentImpactLasted
Front[gmail] Delays on calendar events synchronizing minor1 h 1 min
Front[by_company_00015] Delays on channel imports for a subset of us-west-1 customers minor5 h 9 min
FrontFront mobile SSO login degraded major4 h 21 min
Front[us-west-1] High API latency currently causing delays minor1 h 25 min

Who is around them.

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.

Rating badge for Nabla's site

Nabla transparency rating

It updates with the rating.

<a href="https://thirdpartyindex.com/vendors/nabla"><img src="https://thirdpartyindex.com/badge/nabla.svg" alt="Nabla transparency rating on Third Party Index" height="20"></a>
[![Nabla transparency rating on Third Party Index](https://thirdpartyindex.com/badge/nabla.svg)](https://thirdpartyindex.com/vendors/nabla)