Lambda Labs

lambdalabs.com

3 tracked vendors name Lambda Labs as a subprocessor, including Fireworks, fal and Nooks. We have not found a subprocessor list published by Lambda Labs. We monitor 5 of its documents, which we last checked on Nov 11, 2026.

Subprocessors

None extracted.

Subprocessor of (3)CSV of the companies listing Lambda Labs · Atom feed of the companies listing Lambda Labs

3 companies
  • fal fal.ai - Contact: privacy@lambdal.com - Address: 2510 Zanker Road San Jose, California 95131 - Description: GPU Hosting and Infrastructure Provider; GPU Hosting and Infrastructure provider
  • Fireworks fireworks.ai Infrastructure provider; [Lambda Labs Trust Center](
  • Nooks nooks.ai Cloud GPU Infrastructure Provider

Service statusCSV of Lambda Labs's status page incidents · Atom feed of Lambda Labs's status page incidents

Aug 15: 1 incident (1 minor)Aug 16: no incident reportedAug 17: no incident reportedAug 18: 1 incident (1 no impact stated)Aug 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: 1 incident (1 minor)Sep 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: 1 incident (1 no impact stated)Oct 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 no impact stated)Oct 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: 1 incident (1 no impact stated)Oct 29: no incident reportedOct 30: no incident reportedOct 31: 1 incident (1 major)Nov 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: 1 incident (1 no impact stated)Nov 8: no incident reportedNov 9: no incident reportedNov 10: no incident reportedNov 11: no incident reportedNov 12: no incident reported

90 days agotoday

  • 9 incidents in 90 days
  • 2 major or critical
  • 2 h 56 min typical time to resolve
  • 8 h 54 min longest major
BeganIncidentImpactLasted
Service disruption in us-east-3no impact stated1 h 18 min
lambda.ai Unreachable Due to DNS Issuemajor2 h 31 min
Degraded instance launches and terminations in us-east-3no impact stated—
Experiencing issues with instance launches/terminations in us-west-1no impact stated2 h 56 min
US-SOUTH-2 Scheduled Maintenanceno impact stated2 h 23 min
US-SOUTH-3 Region Resources Not Visible on Dashboard, Impacting Launches and Terminationsminor2 h 6 min
Issue with Cloud Services API Keysmajor8 h 54 min
Network Maintenance in us-east-3no impact stated7 days

Incidents per month

0 3 6 Feb 2026: 4 incidents (2 major, 1 minor, 1 no impact stated) · partial: our history begins Feb 14 · typical time to resolve 3 h 31 min Mar 2026: 4 incidents (1 critical, 2 minor, 1 no impact stated) · typical time to resolve 19 h 11 min Apr 2026: 1 incident (1 minor) · typical time to resolve 49 min May 2026: 1 incident (1 minor) · typical time to resolve 3 h 22 min Jun 2026: 4 incidents (3 minor, 1 no impact stated) · typical time to resolve 1 h 44 min Jul 2026: 5 incidents (1 major, 4 minor) · typical time to resolve 3 h 2 min Aug 2026: 4 incidents (2 minor, 2 no impact stated) · typical time to resolve 21 days Sep 2026: 2 incidents (1 major, 1 minor) · typical time to resolve 8 h 54 min Oct 2026: 4 incidents (1 major, 3 no impact stated) · typical time to resolve 2 h 31 min Nov 2026: 1 incident (1 no impact stated) · typical time to resolve 1 h 18 min Feb 2026Mar Apr May Jun Jul Aug Sep Oct Nov

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

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

ChangesCSV of Lambda Labs's changes · Atom feed of Lambda Labs's changes

None since tracking began.

Rating badge for Lambda Labs's site

Lambda Labs transparency rating

It updates with the rating.

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