Materialize Outage History

Materialize had 10 outages in the last 2 years totaling 88h 5m of downtime — averaging 0.4 incidents per month.

There were 10 Materialize outages since July 28, 2025 totaling 88h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.materialize.com

Minor June 9, 2026

Networking issues affecting source ingestion

Detected by Pingoru: Jun 09, 2026, 05:05 PM UTC
Resolved: Jun 09, 2026, 05:05 PM UTC
Duration: —

Timeline · 5 updates

investigating Jun 08, 2026, 05:32 PM UTC

Status: Investigating We are currently investigating networking issues that are affecting ingestion for certain sources. Some sources may experience delayed or stalled data ingestion as a result. Our team is actively looking into the cause and we will provide an update as soon as we have more information.
identified Jun 08, 2026, 06:04 PM UTC

Status: Identified We have identified the cause of the stalled ingestion issue affecting some sources, related to a recent network change on our side. A fix is in progress, and adding our current egress IP ranges (https://materialize.com/docs/ingest-data/network-security/static-ips/) to your allowlist will restore ingestion in the meantime.
monitoring Jun 08, 2026, 06:48 PM UTC

Status: Monitoring We have rolled out a fix for the network change that caused delayed or stalled ingestion on some sources. Affected sources should now be reconnecting and catching up. We are monitoring to confirm full recovery and will post a final update once we have verified things are stable.
monitoring Jun 09, 2026, 03:44 PM UTC

Status: Monitoring The network change affecting source ingestion has been reverted and all affected sources have recovered.
resolved Jun 09, 2026, 05:05 PM UTC

Status: Resolved The network change affecting source ingestion has been reverted and all affected sources have recovered.

Read the full incident report →

Minor May 9, 2026

Degraded performance of us-east-1

Detected by Pingoru: May 09, 2026, 05:53 PM UTC
Resolved: May 09, 2026, 05:53 PM UTC
Duration: —

Affected: aws/us-east-1

Timeline · 3 updates

identified May 08, 2026, 03:17 AM UTC

Status: Identified Due to an upstream thermal event, some clusters in us-east-1 may be experiencing degraded performance or replica restarts. We have redirected new node provisioning to healthy datacenter targets, and are monitoring the situation. Affected components aws/us-east-1 (Degraded performance)
monitoring May 08, 2026, 03:36 AM UTC

Status: Monitoring We are continuing to monitor as things recover Affected components aws/us-east-1 (Degraded performance)
resolved May 09, 2026, 05:53 PM UTC

Status: Resolved We are no longer observing impact to Materialize services, and this incident is now resolved. Affected components aws/us-east-1 (Operational)

Read the full incident report →

Minor March 3, 2026

Degraded Performance – Cluster Creation for Replicas ≥ 1600cc

Detected by Pingoru: Mar 03, 2026, 03:46 PM UTC
Resolved: Mar 03, 2026, 03:46 PM UTC
Duration: —

Affected: aws/us-east-1aws/eu-west-1aws/us-west-2

Timeline · 3 updates

investigating Mar 02, 2026, 08:02 PM UTC

Status: Investigating We are currently investigating an issue impacting cluster creation for replicas sized greater than or equal to 1600cc. Customers may experience delays or clusters remaining in a pending state during provisioning. Smaller replica sizes are not affected. Our engineering team is actively working to identify the root cause and mitigate the issue. Affected components aws/eu-west-1 (Degraded performance) aws/us-east-1 (Degraded performance) aws/us-west-2 (Degraded performance)
investigating Mar 03, 2026, 02:23 AM UTC

Status: Investigating We are continuing to investigate an issue impacting cluster creation for legacy cc replicas sized greater than or equal to 1600cc. Customers may experience delays or see clusters remain in a pending state during provisioning. We have confirmed that this issue does not affect M.1 cluster sizes. Only legacy cc clusters are impacted at this time. Our engineering team is actively working to identify the root cause and implement a mitigation. We will provide further updates as we have more information. Affected components aws/eu-west-1 (Degraded performance) aws/us-east-1 (Degraded performance) aws/us-west-2 (Degraded performance)
resolved Mar 03, 2026, 03:46 PM UTC

Status: Resolved We have identified and resolved the issue impacting cluster creation for large legacy cc replicas. Cluster provisioning is now functioning normally. M.1 cluster sizes were not affected during this incident. Affected components aws/us-east-1 (Operational) aws/us-west-2 (Operational) aws/eu-west-1 (Operational)