Rewindex

CompaniesMatillionIncidents

Matillion: Third party system outage impacting Public API access only

MinorStatus: resolvedStarted Resolved (1.4 h)2 updatesstspg.io (opens in new tab)
Part of an outage event

Cloudflare outage, Nov 18, 2025 · 77 vendors, 81 incidents

Matillion’s incident started in the same window without naming Cloudflare (timing only, not evidence of a link). (timing only, posted +2 h 18 min vs the first vendor naming Cloudflare)

Swipe sideways to see the whole diagram.

same windowCloudflareown incident not archivedWithin an hour13 vendors, 13 blamed CloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamed CloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, Maven Central +4Matillion (this incident)posted +2 h 18 min
same windowCloudflareown incident not archivedWithin an hour13 vendors, 13 blamedCloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamedCloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, MavenCentral +4Matillion (this incident)posted +2 h 18 min
Matillion is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>13 vendors, 13 blamed Cloudflare<br/>Stytch, Zed, NordLayer +10"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>19 vendors, 19 blamed Cloudflare<br/>GitLab, Gorgias, Cursor +16"]:::blames
  root --> h4
  later["Later<br/>7 vendors, 7 blamed Cloudflare<br/>RudderStack, Brex, Maven Central +4"]:::blames
  root --> later
  me["Matillion (this incident)<br/>posted +2 h 18 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: DesignerEU Region - DesignerDesignerUS Region - Designer

Timeline of updates

  1. identified

    A third party is experiencing an ongoing incident that is causing our public API to return intermittent 500 errors. This will not impact any scheduled or design-time activities happening within the user interface.

  2. resolved

    The third party has resolved their ongoing incident. The public API is now functioning as intended.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Matillion profileRecent Matillion incidentsMarkdownJSON