Materialize: Cloud Connectivity Issues Due to Authentication Provider Outage
Affected components: aws/eu-west-1aws/eu-west-1aws/us-east-1aws/us-east-1aws/us-west-2aws/us-west-2ConsoleConsole
Timeline of updates
- identifiedEdited
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. - 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.
- resolved
Authentication has recovered. Console sign-in and new connections using app passwords are fully restored.
Changes Rewindex caught on this incident
- Major incident: Cloud Connectivity Issues Due to Authentication Provider Outage
- Incident silently edited: Cloud Connectivity Issues Due to Authentication Provider Outage
- Incident silently edited: Cloud Connectivity Issues Due to Authentication Provider Outage
- Incident updated: Cloud Connectivity Issues Due to Authentication Provider Outage
- Incident updated: Cloud Connectivity Issues Due to Authentication Provider Outage
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.materialize.com (opens in new tab).
Cite this
Status incident (vendor impact label: major) posted by Materialize, started 2026-11-10 20:26 UTC, resolved after 1.8 h, 3 update(s); edited after publishing.
- Title
- Cloud Connectivity Issues Due to Authentication Provider Outage
- Vendor
- Materialize
- Date
- URL
- https://rewindex.com/company/materialize/incidents/01M73J7SC61WHPK1GS5ZQP51P1
Materialize profileRecent Materialize incidentsAll outages on November 10, 2026Materialize in November 2026MarkdownJSON