Between 01:55 and 02:15 UTC on November 19, 2026, some environments in AWS us-east-1 couldn't reach their external sources. Only workloads running in availability zone us-east-1b were affected. During that time, data from those sources wasn't ingested. Materialized views, indexes and sinks that depend on them stopped updating, and some queries may have been slow or timed out while waiting for fresh results.
Connectivity came back at about 02:15 UTC. Affected sources reconnected automatically, resumed from where they left off and caught up within about a minute. We don't expect any data loss, and no action is needed from customers.
Our initial investigation points to a network connectivity issue affecting outbound traffic from us-east-1b. We're still confirming the root cause and are improving our monitoring so we detect this kind of issue sooner.
We apologize for the disruption. If you're still seeing unexpected behavior, please contact support.
Resolved
Between 01:55 and 02:15 UTC on November 19, 2026, some environments in AWS us-east-1 couldn't reach their external sources. Only workloads running in availability zone us-east-1b were affected. During that time, data from those sources wasn't ingested. Materialized views, indexes and sinks that depend on them stopped updating, and some queries may have been slow or timed out while waiting for fresh results.
Connectivity came back at about 02:15 UTC. Affected sources reconnected automatically, resumed from where they left off and caught up within about a minute. We don't expect any data loss, and no action is needed from customers.
Our initial investigation points to a network connectivity issue affecting outbound traffic from us-east-1b. We're still confirming the root cause and are improving our monitoring so we detect this kind of issue sooner.
We apologize for the disruption. If you're still seeing unexpected behavior, please contact support.