Fern

buildwithfern.com

We have not found a subprocessor list published by Fern. We monitor 3 of its documents, which we last checked on Nov 21, 2026.

Subprocessors

None extracted.

Web TechnologiesCSV of Fern's web technologies · Atom feed of Fern's web technologies

Fern's homepage made 368 requests to 12 domains, 6 services controlled by another company, and 1 domain not identified.

Analytics (3): posthog, LinkedIn, RampmetricsAdvertising (2): Google Cloud, MicrosoftOther (1): reviewed as Affiliate programs: TUNE, Inc.

6 third parties by category: Analytics 3Advertising 2Other 1

Third parties 6 · 26 requests
Google Cloud DoubleClick Floodlight Google Analytics Google Tag Manager 3% of the page's requests 12
posthog PostHog 2% of the page's requests 6
LinkedIn Linkedin Insight Tag <1% of the page's requests 3
Microsoft Microsoft Advertising <1% of the page's requests 3
Rampmetrics Rampmetrics <1% of the page's requests 1
TUNE, Inc. go2cloud.org <1% of the page's requests 1
Unknown 1 · 1 request

rm-api.com

First party 1 · 341 requests
Fern Amazon CloudFront Amazon Web Services HSTS Lucide Next.js 16.3.5 Next.js App Router Open Graph Priority Hints React Turbopack Vercel Webpack 93% of the page's requests 341

4 tracked companies loaded by the homepage are not in Fern's subprocessor list. A website can use a service without it processing customer data.

Service statusCSV of Fern's status page incidents · Atom feed of Fern's status page incidents

Aug 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: no incident reportedSep 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: 1 incident (1 critical)Sep 24: no incident reportedSep 25: 1 incident (1 minor)Sep 26: no incident reportedSep 27: no incident reportedSep 28: no incident reportedSep 29: no incident reportedSep 30: no incident reportedOct 1: no incident reportedOct 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: 1 incident (1 critical)Oct 13: no incident reportedOct 14: no incident reportedOct 15: no incident reportedOct 16: 24 incidents (10 critical, 3 major, 11 minor)Oct 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: 1 incident (1 critical)Nov 3: 1 incident (1 critical)Nov 4: 1 incident (1 minor)Nov 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: no incident reportedNov 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 reportedNov 22: no incident reported

90 days agotoday

  • 30 incidents in 90 days
  • 17 major or critical
  • 1 h 35 min typical time to resolve
  • 1 h 35 min longest major
BeganIncidentImpactLasted
Docs Performance Slowdownminor1 h 16 min
Publishing Outagecritical—
Publishing Outagecritical1 h 35 min
Intermittent slow page loadsminor—
Docs Previews Slowminor—
Fern Dashboard fails to load organization pagescritical—
Fern Docs 504critical—
Elevated 504 Timeoutcritical—

Incidents per month

0 15 30 Mar 2026: 5 incidents (3 minor, 2 no impact stated) · partial: our history begins Mar 5 · typical time to resolve 2 h 46 min Apr 2026: 3 incidents (1 critical, 1 major, 1 minor) · typical time to resolve 57 min May 2026: 7 incidents (2 critical, 1 major, 3 minor, 1 no impact stated) · typical time to resolve 1 h 33 min Jun 2026: 5 incidents (1 major, 4 minor) · typical time to resolve 3 h 30 min Jul 2026: 2 incidents (1 critical, 1 minor) · typical time to resolve 3 h 18 min Aug 2026: 1 incident (1 major) · typical time to resolve 1 h 13 min Sep 2026: 2 incidents (1 critical, 1 minor) · typical time to resolve 6 h 49 min Oct 2026: 25 incidents (11 critical, 3 major, 11 minor) · typical time to resolve 1 h 6 min Nov 2026: 3 incidents (2 critical, 1 minor) · typical time to resolve 1 h 35 min Mar 2026Apr May Jun Jul Aug Sep Oct Nov

critical major minor no impact stated before or partly before our history

As Fern's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)

ChangesCSV of Fern's changes · Atom feed of Fern's changes

None since tracking began.

Rating badge for Fern's site

Fern transparency rating

It updates with the rating.

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