Is Materialize Down?

Authentication has recovered. Console sign-in and new connections using app passwords are fully restored. --- [2026-11-10T20:56:43Z] (monitoring) Our authentication provider has fixed the issue, and console and pgwire logins are recovering. Some users may still see slow or failed logins for a short time. We’re keeping this incident open while we confirm all services are restored. --- [2026-11-10T20:51:05Z] (identified) Starting at approximately 20:20 UTC, an outage at our upstream authentication provider is preventing some users from authenticating to Materialize Cloud. This affects all Cloud regions. What’s affected • Logging in to the Materialize console • Opening new pgwire connections, including connections that use app passwords • Tools and services that open new connections or reconnect, such as connection poolers, BI tools, dbt runs, and other scheduled jobs. These may see authentication errors or timeouts. What’s not affected • Clusters are running normally. • Sources are still ingesting data, and sinks are still writing data, so we don’t expect any impact to data freshness. • Self-managed deployments are not affected. What you can do If you have pgwire connections that are already open, we recommend not restarting them or the services that use them until this is resolved. New connection attempts may fail until our provider recovers.

Between 21:12 UTC and 22:18 UTC on September 3, AWS experienced elevated error rates in its Security Token Service (STS) in the us-west-2 region, which AWS reported on its Health Dashboard. Materialize environments in that region use STS to obtain credentials for object storage access, and requests for those credentials failed or timed out during the event. Some environments in the region experienced degraded performance during this window. Query results remained correct throughout, and no data was lost. The upstream issue was resolved by AWS at 22:18 UTC and all affected environments recovered.

Upstream authentication vendor has fully resolved their incident. All impacted systems have recovered. --- [2026-08-20T13:59:19Z] (monitoring) We’re seeing pgwire authentication recover and are continuing to monitor the situation to ensure service remains stable. --- [2026-08-20T13:37:52Z] (identified) We’ve determined that this issue is related to an outage of our authentication provider and is limited to pgwire authentication. Sources and sinks continue to run as expected, and we do not expect this issue to impact data freshness. We are continuing to monitor the situation and work toward a resolution. --- [2026-08-20T13:31:51Z] (investigating) We are seeing issues across the platform potentially caused by an outage of an upstream vendor. We are actively investigating and looking into mitigations.