Estuary
Documents
| Document | Verified | Changed | Evidence |
|---|---|---|---|
| Subprocessor list | snapshot | ||
| Data processing addendum | snapshot | ||
| Privacy policy | snapshot | ||
| Terms | snapshot | ||
| Security page | snapshot | ||
| security.txt | snapshot | ||
| Status page incident.io | snapshot |
Subprocessors
| Name | Purpose | Location | Listed since |
|---|---|---|---|
| Amazon Web Services | Cloud Infrastructure | Customer Selected Regions | |
| Google Cloud Platform | Cloud Infrastructure | US and Customer Selected Regions | |
| Logrocket | Customer Support | United States | |
| Microsoft Azure | Cloud Infrastructure | Customer Selected Regions | |
| Pylon | Customer Support | United States | |
| Supabase | Database & API Services | United States |
Listed as a subprocessor by (4)
Purposes as each company states them.
Service status
- 4 incidents in 90 days
- 2 major or critical
- 4 h 31 min typical time to resolve
- 6 h 46 min longest major
| Began | Incident | Impact | Lasted |
|---|---|---|---|
| Delayed Data for Redshift Materializations | minor | 4 h 31 min | |
| An individual private data plane is experiencing no data movement | major | 1 h 3 min | |
| Dekaf materializations stalled on public AWS us-east-1 & GCP us-central1 data planes | major | 6 h 46 min | |
| Stalled Tasks in GCP Public Dataplane | minor | 1 h 26 min | |
| Data processing and reporting delays on us-east-1 public data plane | major | 45 min | |
| Dekaf Failures | critical | 2 h 29 min | |
| Public GCP us-central1-c2 data plane outage | major | 3 h 28 min | |
| Test Incident | minor | 4 min |
As Estuary's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)
Changes
None since tracking began.