Check Estuary Status for live updates on platform performance, service interruptions, and scheduled maintenance to keep your data workflows running smoothly.
API
Operational
90 days ago
100.0
% uptime
Today
Management Portal
Operational
90 days ago
100.0
% uptime
Today
Connectors - Databases
Operational
90 days ago
100.0
% uptime
Today
Connectors - SaaS
Operational
90 days ago
100.0
% uptime
Today
Connectors - Filestores
Operational
90 days ago
100.0
% uptime
Today
Connectors - Destinations
Operational
90 days ago
100.0
% uptime
Today
Dekaf
Operational
90 days ago
100.0
% uptime
Today
Reporting
Operational
90 days ago
100.0
% uptime
Today
Runtime
Operational
90 days ago
100.0
% uptime
Today
Private Data Planes
Operational
90 days ago
100.0
% uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Resolved -
Reporting is now caught up, and this incident is resolved
Feb 25, 00:25 UTC
Monitoring -
Reporting was delayed for the last 2 hours, it's now catching up. You may have noticed data processing alerts if you have 1 hour delay configured.
Feb 25, 00:08 UTC
Resolved -
This incident has been resolved. All affected tasks will automatically recover - no action is necessary.
Feb 16, 19:44 UTC
Monitoring -
A fix has been implemented and we're monitoring recovery.
Feb 16, 19:26 UTC
Identified -
NetSuite SuiteAnalytics captures are currently failing on startup with a TLS connection error. This affects customers using the source-netsuite-v2 (SuiteAnalytics) connector. The source-netsuite-suiteql connector is not affected.
We've identified the issue and will provide an update once a fix has been released.
Feb 16, 17:46 UTC
The fix to that issue involved renaming blob storage files on recovery to make it impossible to duplicate BDEC files. Unfortunately a logic error in that led to a further issue where 52 total tables received corrupted data between 5:30 PM ET on February 13th and 8 PM ET on February 14th.
The Estuary support team will be reaching out to all affected customers to help with that recovery process.
Feb 15, 16:49 UTC
Resolved -
This incident is now resolved and was isolated to reporting delays
Feb 13, 07:33 UTC
Monitoring -
We are experiencing delays in reporting, which may lead to false alarms by our alerting system as well. Reporting is catching up, and expected to be back to normal within the next hour
Feb 13, 05:46 UTC