Materialize

materialize.com (opens in new tab)Status page (opens in new tab)

Status page says: Operational since Oct 19
Last 90 days: 2 incidents, 1 major or critical
Rewrites caught: None so far
Next deprecation: None announced

Materialize incidents per day, last 90 days

Our copy of Materialize’s status page starts Aug 20; hatched days are before that. Select a day to jump to its incidents.

How Materialize reports incidents

Not enough incidents to compare Materialize with other vendors yet: a vendor needs 20 incidents in a year and 10 with full update detail (Materialize has 2 and 2).

Provisional. Built nightly from every archived version of each incident, last on Oct 19. Compare all vendors

Dependencies

What Materialize relies on and who relies on Materialize, as observed in status-page incidents: who they blame, where they say they run, and who fails at the same time. Observed, not verified.

Materialize depends on

Provider	Evidence	Signal
AWS	blamed in 1 incident; together in 1 outage event “…Degraded availability for Cloud customers in us-west-2 due to upstream AWS credential service disruption Between 21:12 UTC and 22:18 UTC on September 3, AWS experienced elevated error rates in its Sec…” incident	Likely

Outage events: AWS us-west-2, Sep 3.

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.