All Systems Operational

About This Site

Check Estuary Status for live updates on platform performance, service interruptions, and scheduled maintenance to keep your data workflows running smoothly.

Uptime over the past 90 days. View historical uptime.
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
99.97 % uptime
Today
Connectors - SaaS ? Operational
90 days ago
99.97 % uptime
Today
Connectors - Filestores ? Operational
90 days ago
99.97 % uptime
Today
Connectors - Destinations ? Operational
90 days ago
99.97 % uptime
Today
Dekaf ? Operational
90 days ago
99.98 % uptime
Today
Reporting ? Operational
90 days ago
99.98 % uptime
Today
Runtime ? Operational
90 days ago
99.87 % 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.

No incidents or maintenance related to this downtime.

Mar 23, 2025

No incidents reported today.

Mar 22, 2025

No incidents reported.

Mar 21, 2025

No incidents reported.

Mar 20, 2025

No incidents reported.

Mar 19, 2025
high error rates in AWS EU data plane
Resolved - Systems have been healthy for the last 6 hours, this issue is resolved.
Mar 19, 23:59 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 19, 17:45 UTC
Identified - We've identified an issue that's affecting many of the tasks running in our public AWS EU data plane. This issue is also preventing stats from being read from that data plane, so it will appear that no tasks running there are making progress (although some are still making progress). We're working on rolling out a fix ASAP. No other data planes are affected.
Mar 19, 17:16 UTC
Mar 18, 2025
EU data plane outage (1:52 to 3:53 UTC, 18/03/2025)
Resolved - Our public EU data plane experienced an outage from 1:52 UTC to 3:53 UTC today, this is resolved now and affected connectors should automatically resume. No other data planes were affected (you would not be impacted unless you have explicitly chosen the public EU data plane).

Please reach out to support if you have any concerns.
Mar 18, 04:11 UTC
Mar 17, 2025

No incidents reported.

Mar 16, 2025

No incidents reported.

Mar 15, 2025
Continued runtime degraded performance
Resolved - This incident has been resolved.
Mar 15, 23:09 UTC
Identified - Starting yesterday, we've seen intermittent but escalating failures of DNS resolution in the primary public data-plane, which runs in a Google Kubernetes Cluster. We've traced the problem back to low-level Google-managed components within that cluster and have been engaging their support. Thus far, their recommendations have unfortunately made the problem worse today and we're currently seeing further-elevated task errors due to failures of DNS resolution. We're escalating as much as we can and going back and forth with Google support -- this has been frustrating because we're fairly beholden to them, given how deep the issue is within the bowels of the Google-managed environment, but we'll provide updates as we can.

Private data-planes, as well as the EU data-plane, are not affected. We've been planning a migration off of this legacy Kubernetes cluster to our new data-plane infrastructure, but unfortunately aren't yet in a position to kick it off.

This is ongoing for a very small percentage (less than 5%) of tasks and Google’s fixes didn’t fully help.
Mar 15, 01:44 UTC
Runtime degraded performance
Resolved - This incident has been resolved.
Mar 15, 03:00 UTC
Update - We are rolling an update with Google's help and it has improved tasks. They are recovering.
Mar 14, 22:19 UTC
Update - We are continuing to investigate this issue.
Mar 14, 20:39 UTC
Investigating - Starting yesterday, we've seen intermittent but escalating failures of DNS resolution in the primary public data-plane, which runs in a Google Kubernetes Cluster. We've traced the problem back to low-level Google-managed components within that cluster and have been engaging their support. Thus far, their recommendations have unfortunately made the problem worse today and we're currently seeing further-elevated task errors due to failures of DNS resolution. We're escalating as much as we can and going back and forth with Google support -- this has been frustrating because we're fairly beholden to them, given how deep the issue is within the bowels of the Google-managed environment, but we'll provide updates as we can.

Private data-planes, as well as the EU data-plane, are not affected. We've been planning a migration off of this legacy Kubernetes cluster to our new data-plane infrastructure, but unfortunately aren't yet in a position to kick it off.
Mar 14, 18:30 UTC
Mar 14, 2025
Mar 13, 2025
Accidental Alert Emails
Resolved - This incident has been resolved.
Mar 13, 14:44 UTC
Identified - Alert emails received between midnight and 2 AM ET on March 13th. They were sent in error due to an upgrade in our alert system that unintentionally resent historical and currently irrelevant alerts.
Mar 13, 12:47 UTC
Mar 12, 2025
Control-plane Scheduled Maintenance
Completed - The scheduled maintenance has been completed.
Mar 12, 12:57 UTC
Verifying - Verification is currently underway for the maintenance items.
Mar 12, 11:44 UTC
Update - The migration was successful and everything seems to be operating as expected. I'm putting the UI back into service. We'll continue to monitor
Mar 12, 11:43 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 12, 10:30 UTC
Scheduled - [The previous maintenance was scheduled early accidentally]
We will be performing some upgrades related to monitoring and observability of tasks. During this time, there may be some brief delays in reporting of task stats, inferred schema updates, and alerts. The UI will also be unavailable for a portion of the upgrade.

We don't plan to introduce any interruptions to ongoing data processing, so your tasks should continue to run as usual.
Mar 12, 06:55 UTC
Mar 11, 2025
Reporting Delay
Resolved - This incident has been resolved.
Mar 11, 23:48 UTC
Identified - Reporting is currently behind and that will cause no data alerts even though data is flowing.
Mar 11, 21:12 UTC
Mar 10, 2025

No incidents reported.

Mar 9, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage