Logto

logto.io

Logto declares 7 subprocessors in its subprocessor list, which we last checked on Nov 11, 2026 (evidence). They include Google Cloud, Microsoft and Cloudflare. No published changes since we first read it on Nov 6, 2026. 1 tracked vendor, LandingAI, names Logto as a subprocessor.

Subprocessors CSV of Logto's subprocessors · Atom feed of Logto's subprocessors DORA draft CSV of Logto's subprocessors as declared by Logto what's this? · 

7 third parties.

NamePurposeLocationListed since
Azure Cloud Infrastructure & Platform Services
Cloudflare Network & Edge Security
Google Workspace Business Apps & Productivity
Linear Change & Release Management
Notion Business Apps & Productivity
PostHog Business Apps & Productivity
Slack Business Apps & Productivity

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

Logto's homepage made 87 requests to 2 domains, and 1 service controlled by another company.

Advertising (1): usually detected as Advertising: Google Cloud

1 third party by category: Advertising 1

Third parties 1 · 1 request
Google Cloudsubprocessor fonts.googleapis.com 1% of the page's requests 1
First party 1 · 86 requests
Logto Cloudflare Goober HTTP/3 Open Graph Plausible Prism React React Router 8.3.0 99% of the page's requests 86

Subprocessor of (1)CSV of the companies listing Logto · Atom feed of the companies listing Logto

1 company
  • LandingAI landing.ai Identity and Access Management; Provides customer identity services, including user login, authentication, and user management for the LandingAI platform. - Logto's Subprocessors: [List]( - Products: All (US)

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

Aug 15: before our history of this status pageAug 16: before our history of this status pageAug 17: before our history of this status pageAug 18: before our history of this status pageAug 19: before our history of this status pageAug 20: before our history of this status pageAug 21: before our history of this status pageAug 22: before our history of this status pageAug 23: before our history of this status pageAug 24: before our history of this status pageAug 25: before our history of this status pageAug 26: before our history of this status pageAug 27: before our history of this status pageAug 28: before our history of this status pageAug 29: before our history of this status pageAug 30: before our history of this status pageAug 31: before our history of this status pageSep 1: before our history of this status pageSep 2: before our history of this status pageSep 3: before our history of this status pageSep 4: before our history of this status pageSep 5: before our history of this status pageSep 6: before our history of this status pageSep 7: before our history of this status pageSep 8: before our history of this status pageSep 9: before our history of this status pageSep 10: before our history of this status pageSep 11: before our history of this status pageSep 12: before our history of this status pageSep 13: before our history of this status pageSep 14: before our history of this status pageSep 15: before our history of this status pageSep 16: before our history of this status pageSep 17: before our history of this status pageSep 18: before our history of this status pageSep 19: before our history of this status pageSep 20: before our history of this status pageSep 21: before our history of this status pageSep 22: before our history of this status pageSep 23: before our history of this status pageSep 24: before our history of this status pageSep 25: before our history of this status pageSep 26: before our history of this status pageSep 27: before our history of this status pageSep 28: before our history of this status pageSep 29: before our history of this status pageSep 30: before our history of this status pageOct 1: before our history of this status pageOct 2: before our history of this status pageOct 3: before our history of this status pageOct 4: before our history of this status pageOct 5: before our history of this status pageOct 6: before our history of this status pageOct 7: before our history of this status pageOct 8: before our history of this status pageOct 9: before our history of this status pageOct 10: before our history of this status pageOct 11: before our history of this status pageOct 12: before our history of this status pageOct 13: before our history of this status pageOct 14: before our history of this status pageOct 15: before our history of this status pageOct 16: before our history of this status pageOct 17: before our history of this status pageOct 18: before our history of this status pageOct 19: before our history of this status pageOct 20: before our history of this status pageOct 21: before our history of this status pageOct 22: before our history of this status pageOct 23: before our history of this status pageOct 24: before our history of this status pageOct 25: before our history of this status pageOct 26: before our history of this status pageOct 27: before our history of this status pageOct 28: before our history of this status pageOct 29: before our history of this status pageOct 30: before our history of this status pageOct 31: before our history of this status pageNov 1: before our history of this status pageNov 2: before our history of this status pageNov 3: before our history of this status pageNov 4: before our history of this status pageNov 5: before our history of this status pageNov 6: before our history of this status pageNov 7: before our history of this status pageNov 8: no incident reportedNov 9: no incident reportedNov 10: no incident reportedNov 11: no incident reportedNov 12: no incident reported

90 days agotoday

No incidents reported since Nov 8, 2026

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

Incidents reported by Logto's subprocessorsCSV of incidents reported by vendors Logto lists · Atom feed of incidents reported by vendors Logto lists

14 reported incidents in the last 30 days, by 2 of the vendors Logto lists as subprocessors.

A subprocessor list names a company, not the service an incident touched. This does not show that Logto was involved.

DateCompanyIncidentImpactLasted
LinearSlack integration degraded due to Slack outage minor3 h 9 min
NotionSome Notion Agent sessions may hang or stop updating major2 h 19 min
LinearProject pages failing to load minor3 min
LinearSome Slack integrations have been unexpectedly archived no impact stated56 min
LinearProblems loading application major14 min
NotionUsers unable to access Notion critical3 h 6 min
NotionPHP2Shell (CVE-2026-109618, CVE-2026-109619) no impact stated3 days
NotionNotion MCP query_data_source tool is temporarily unavailable in Claude clients major1 h 19 min
NotionSecurity update: Preventative certificate security measures no impact stated5 days
NotionUnable to install connections created by other workspace members major19 h 57 min
NotionSome Notion Agent requests may stop before completion minor3 h 57 min
NotionCursor-powered Custom Agents unable to load Notion tools no impact stated3 h 39 min
NotionForm submission issues (resolved) no impact stated7 h 48 min
NotionDegraded performance in Notion and the Notion API no impact stated8 days

Who is around them.

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

See the list as we read it on any date: Time machine

None since tracking began.

Rating badge for Logto's site

Logto transparency rating

It updates with the rating.

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