Latitude.sh

latitude.sh

Latitude.sh declares 1 subprocessor in its subprocessor list, which we last checked on Nov 11, 2026 (evidence). It is Wasabi. No published changes since we first read it on Sep 23, 2026. 7 tracked vendors name Latitude.sh as a subprocessor, including Baseten, Mistral and Algolia.

Subprocessors CSV · Atom DORA draft CSV what's this? · 

1 third party.

NamePurposeLocationListed since
Wasabi Storage ServicesLocations: USA, Canada, United Kingdom, Netherlands, Germany, Italy, France, Australia, Japan, Singapore (as configured by the Customer)

Web TechnologiesCSV · Atom

Latitude.sh's homepage made 110 requests to 3 domains, and 2 services controlled by another company.

CDN (1): usually detected as CDN: UNPKGOther (1): reviewed as Digital asset management: Cloudinary

2 third parties by category: CDN 1Other 1

Third parties 2 · 3 requests
Cloudinary cloudinary.com 2% of the page's requests 2
UNPKG unpkg.com <1% of the page's requests 1
First party 1 · 107 requests
Latitude.sh Contentful HSTS Lucide Next.js 15.5.28 Next.js App Router Open Graph PWA Priority Hints Radix UI React Segment 5.2.0 Sentry Vercel Vercel Analytics Vercel Speed Insights 1.3.1 Webpack 97% of the page's requests 107

1 tracked company loaded by the homepage is not in Latitude.sh's subprocessor list. A website can use a service without it processing customer data.

Subprocessor of (7)CSV · Atom

7 companies
  • Algolia algolia.com
  • Baseten baseten.co Cloud Compute
  • ConnectWise connectwise.com Data Center Provider; Japan, US
  • Daytona daytona.io Cloud Infrastructure
  • Mistral mistral.ai Cloud infrastructure (Latitude.sh); Product: Vibe Code Web
  • Replicated replicated.com Various IaaS
  • Ubicloud ubicloud.com Infrastructure (server) and data hosting

ComplianceCSV · Atom

Certified
Says it complies with

Certifications as Latitude.sh's trust center lists them; reports are usually shared on request (evidence)

Service statusCSV · Atom

Aug 14: no incident reportedAug 15: no incident reportedAug 16: no incident reportedAug 17: no incident reportedAug 18: no incident reportedAug 19: no incident reportedAug 20: no incident reportedAug 21: no incident reportedAug 22: no incident reportedAug 23: no incident reportedAug 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: 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: 1 incident (1 major)Sep 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: 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: 1 incident (1 minor)Oct 10: no incident reportedOct 11: no incident reportedOct 12: no incident reportedOct 13: no incident reportedOct 14: no incident reportedOct 15: no incident reportedOct 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 reported

90 days agotoday

  • 2 incidents in 90 days
  • 1 major or critical
  • 3 h 55 min typical time to resolve
  • 2 h longest major
BeganIncidentImpactLasted
Network Connectivity Issues - São Paulominor3 h 55 min
Network issue affecting services in Sao Paulo locationmajor2 h
Power Issue - LON2major23 h 37 min
Network Connectivity Issues - New Yorkminor1 h 17 min
Increased error rate for Reinstalling and Deployingcritical12 h 9 min
Network Connectivity Incident - Miamino impact stated11 h 6 min
Increased error rate for deployments in Dallasminor38 min
IPMI Access Errors Increasing - Dallasminor2 h 47 min

Incidents per month

0 4 8 Dec 2025: 7 incidents (2 major, 2 minor, 3 no impact stated) · typical time to resolve 4 h 12 min Jan 2026: 0 incidents Feb 2026: 3 incidents (3 minor) · typical time to resolve 6 h 42 min Mar 2026: 5 incidents (3 major, 2 minor) · typical time to resolve 2 h 47 min Apr 2026: 0 incidents May 2026: 2 incidents (1 critical, 1 no impact stated) · typical time to resolve 1 h 7 min Jun 2026: 5 incidents (1 critical, 3 minor, 1 no impact stated) · typical time to resolve 2 h 47 min Jul 2026: 0 incidents Aug 2026: 1 incident (1 major) · typical time to resolve 23 h 37 min Sep 2026: 1 incident (1 major) · typical time to resolve 2 h Oct 2026: 1 incident (1 minor) · typical time to resolve 3 h 55 min Nov 2026: 0 incidents Dec 2025Jan 2026Feb Mar Apr May Jun Jul Aug Sep Oct Nov

critical major minor no impact stated

Components affected

ComponentIncidents
SAO2

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

Incidents reported by Latitude.sh's subprocessorsCSV · Atom

1 reported incident in the last 30 days, by 1 of the vendors Latitude.sh lists as a subprocessor.

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

DateCompanyIncidentImpactLasted
WasabiSystem errors in CA-CENTRAL-1 minor3 h

Who is around them.

ChangesCSV · Atom

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

None since tracking began.

Rating badge for Latitude.sh's site

Latitude.sh transparency rating

It updates with the rating.

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