Materialize Outage History

Pingoru has recorded 11 incidents for Materialize: 6 in the last 12 months and 2 in the last 90 days.

11incidents recorded

6last 12 months

2last 90 days

14 hourstypical duration

Incidents per month

Share of hours with an open incident, any severity

Pingoru began tracking Materialize in April 2026, so earlier months are not shown. Hover a bar for its value.

Show as a table

Incidents, newest first

Started Sep 03, 2026, 09:12 PM UTC· resolved Sep 03, 2026, 10:18 PM UTC

resolved Sep 03, 2026, 09:43 PM UTC

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.

Major August 20, 2026 Upstream vendor causing authentication related issues 1h 8m Cloud regions (aws/us-east-1), Cloud regions (aws/eu-west-1), Cloud regions (aws/us-west-2)

Started Aug 20, 2026, 01:31 PM UTC· resolved Aug 20, 2026, 02:39 PM UTC

investigating Aug 20, 2026, 01:31 PM UTC

We are seeing issues across the platform potentially caused by an outage of an upstream vendor. We are actively investigating and looking into mitigations.
identified Aug 20, 2026, 01:37 PM UTC

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.
monitoring Aug 20, 2026, 01:59 PM UTC

We’re seeing pgwire authentication recover and are continuing to monitor the situation to ensure service remains stable.
resolved Aug 20, 2026, 02:39 PM UTC

Upstream authentication vendor has fully resolved their incident. All impacted systems have recovered.

Started Jun 08, 2026, 05:32 PM UTC· resolved Jun 09, 2026, 05:05 PM UTC

investigating Jun 08, 2026, 05:32 PM UTC

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

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

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.
resolved Jun 09, 2026, 05:05 PM UTC

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

Minor May 8, 2026 Degraded performance of us-east-1 1d 14h Cloud regions (aws/us-east-1)

Started May 08, 2026, 03:17 AM UTC· resolved May 09, 2026, 05:53 PM UTC

identified May 08, 2026, 03:17 AM UTC

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.
monitoring May 08, 2026, 03:36 AM UTC

We are continuing to monitor as things recover
resolved May 09, 2026, 05:53 PM UTC

We are no longer observing impact to Materialize services, and this incident is now resolved.

Minor March 2, 2026 Degraded Performance – Cluster Creation for Replicas ≥ 1600cc 19h 43m Cloud regions (aws/us-east-1), Cloud regions (aws/eu-west-1), Cloud regions (aws/us-west-2)

Started Mar 02, 2026, 08:02 PM UTC· resolved Mar 03, 2026, 03:46 PM UTC

investigating Mar 02, 2026, 08:02 PM UTC

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.
investigating Mar 03, 2026, 02:23 AM UTC

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.
resolved Mar 03, 2026, 03:46 PM UTC

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.