Contentful: Some requests: Increased latency on CMA
AWS outage, Jul 28, 2020 · 18 vendors, 18 incidents
Contentful’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +1 h 43 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/>3 vendors, 3 blamed AWS<br/>Honeycomb, Twilio, Chargebee"]:::blames
root --> h1
h4["1 to 4 hours later<br/>2 vendors, 1 blamed AWS<br/>Stream (GetStream), Elastic Cloud"]:::blames
root --> h4
me["Contentful (this incident)<br/>posted +1 h 43 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
This incident has been resolved.
From Contentful’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 www.contentfulstatus.com (opens in new tab).