Matillion: Billing Portal may be under-reporting usage of METL Instances
AWS outage, Mar 9, 2022 · 12 vendors, 12 incidents
Matillion’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +37 min vs the first vendor naming AWS)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>2 vendors, 2 blamed AWS<br/>Courier, Unbounce"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed AWS<br/>Xero"]:::blames
root --> h4
me["Matillion (this incident)<br/>posted +37 min"]:::me
root -.->|"same window"| meFull 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.
Timeline of updates
- resolved
During an outage at a third party provider, we were unable to consume usage reports from METL instances between 20:40 and 21:00 (UTC). Customers whose instances were reporting usage between these times may have seen their usage under-reported overnight. We have now confirmed this has been corrected, and all usage should information should now be up to date.
From Matillion’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.matillion.com (opens in new tab).