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.55 % 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.55 % uptime
Today
Dekaf ? Operational
90 days ago
99.98 % uptime
Today
Reporting ? Operational
90 days ago
98.58 % uptime
Today
Runtime ? Operational
90 days ago
99.58 % 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 28, 2025

No incidents reported today.

Mar 27, 2025
Partial outage in us public data plane
Resolved - This incident has been resolved.
Mar 27, 14:49 UTC
Update - All impacted derivations are now active as of 30 minutes ago.

Summary: There was a partial outage for reporting, captures, materializations, and derivations in the public US data plane. We are now recovered and monitoring. There are some clean up items and a post mortem to come.

If you have data flows that are still seem impacted please reach out via slack or to support@estuary.dev. If you suspect any missing or duplicative data and would like to backfill to be sure your dataset is complete (or for any reason) in the next 15 days, we will provide a full credit. Please just email support@estuary.dev with backfill details (reason, time, size in GB).
Mar 27, 03:31 UTC
Update - We've begun re-enabling derivations and that will happen over the next couple of hours.

We have backfilled most of the captures that had an outage, and are planning to backfill a few more overnight. If you're seeing any issues and would like to backfill to be sure your dataset is complete, or for any reason in the next 15 days, we will eat the cost and provide a full credit. That is on us for this issue. Please just email support@estuary.dev with backfill details (reason, time, size in GB).
Mar 27, 01:09 UTC
Monitoring - Everything has been resolved except derivations which are being addressed now
Mar 26, 21:57 UTC
Update - US Data Plane Update:
- 1/3rd of materializations are recovered
- Stats are current
Mar 26, 20:11 UTC
Update - - Captures are all recovered
- Stats are catching up
- Materializations are being enabled and backfilled now. This process will take some time to fully complete but materializations are starting to come back now. It will take at least a couple of hours to be fully completed.
Mar 26, 18:47 UTC
Update - - All but a handful of captures have begun recovery
- Stats will be back up and running momentarily
- Recovery for materializations is now our primary focus
Mar 26, 16:49 UTC
Update - - Tasks not in the US-public data plane are all healthy but lacking reporting.
- Tasks in the US-public data plane that are green are running but lacking reporting.
- Tasks in the US-public data plane that aren’t green will need manual recovery that we are working on. This will involve a re-backfill that will be automatically done and credited for small tasks. Large tasks will be done manually and a member of the team will reach out if that is necessary.
Mar 26, 12:35 UTC
Update - Several tasks in the default public US data plane are not running (if your task is green it's running).
Reporting is also currently down, so if your task is running you will not see stats updating.
We're working on a fix and expect it to be a few hours until it's complete.
Mar 26, 07:30 UTC
Identified - The issue has been identified and a fix for some tasks has been rolled out. We're working on a more comprehensive fix.
Mar 26, 05:26 UTC
Investigating - Some connector are paused in the US public data plane. We are investigating.

Tasks may see issues like "INDEX_HAS_GREATER_OFFSET"
Mar 26, 01:29 UTC
Mar 26, 2025
Private Data Planes Outage
Resolved - This incident has been resolved.
Mar 26, 01:26 UTC
Monitoring - The fix has been rolled out and we are monitoring private data planes and the EU data plane.
Mar 26, 00:16 UTC
Update - We've identified the issue as being caused by linux kernes update, and we're working on downgrading the kernel version across our fleet.
Mar 25, 23:10 UTC
Identified - We have identified an issue with private data planes where some or all tasks may be failing on private data planes. We are rolling out a fix for the issue and expect tasks to recover shortly.
Mar 25, 22:02 UTC
Mar 25, 2025
Mar 24, 2025

No incidents reported.

Mar 23, 2025

No incidents reported.

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
← Incident History Powered by Atlassian Statuspage