Yugabyte
Not listed by any tracked vendor.
Documents
| Document | Verified | Changed | Evidence |
|---|---|---|---|
| Trust center | snapshot | ||
| Subprocessor list | snapshot | ||
| Data processing addendum | snapshot | ||
| Privacy policy | snapshot | ||
| Terms | snapshot | ||
| Status page statuspage | snapshot |
Subprocessors
19 third parties, 5 affiliates. CSV · Atom
| Name | Purpose | Location | Listed since |
|---|---|---|---|
| Amazon Web Services, Inc. | Data storage and processing | ||
| Amplitude, Inc. | Digital analytics | ||
| DataDog, Inc. | Audit logging | ||
| Google Cloud Platform | Data storage and processing | ||
| Hubspot, Inc. | CRM | ||
| Madkudu, Inc. | Product & Sales Analytics | ||
| Microsoft Azure | Data storage and processing | ||
| Netsuite, Inc. | Billing and accounting | ||
| Okta, Inc. | Customer identity management | ||
| Orb, Inc. | Billing | ||
| Pagerduty, Inc. | Incident management | ||
| Rudderstack, Inc. | Product Analytics | ||
| Salesforce.com, Inc. | Customer relationship management | ||
| Segment.io, Inc. | Data pipeline for analytics | ||
| SendSafely, Inc. | Customer communications | ||
| Slack Technologies, Inc. | Used to communicate with remote support agents and engineers within Yugabyte | ||
| Stripe, Inc. | Payment processing | ||
| Zendesk, Inc. | Used to receive and track customer support | ||
| ZeroBounce, Inc. | Email Validation |
Service status
2 incidents in the last 90 days (2 major or critical, 0 minor, 0 with no stated impact) · typically resolved in 4 h 54 min · longest major: 4 h 54 min
| Began | Incident | Impact | Lasted |
|---|---|---|---|
| YugbyteDB Aeon GCP Capacity constraints in us-central1 | major | 4 h 54 min evidence | |
| Issues with Cluster Creation and Editing | critical | 15 min evidence | |
| Cluster Status Inaccuracy | major | 16 h 44 min evidence | |
| Inaccurate Metrics Reporting | major | 4 h 9 min evidence | |
| Major outage of Yugabyte DB Aeon Management Services | critical | 4 h 7 min evidence |
As Yugabyte's status page reports its own incidents (scheduled maintenance left out), read every few hours since .
Changes
None since tracking began.