Courier: An incident with Courier's hosting infrastructure has been identified and is impacting access to service.
AWS outage, Jun 13, 2023 · 56 vendors, 56 incidents
Courier’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +0 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/>13 vendors, 13 blamed AWS<br/>Pipedream, Wiz, Temporal Cloud +10"]:::blames
root --> h1
h4["1 to 4 hours later<br/>7 vendors, 6 blamed AWS<br/>CockroachDB, Vanta, Asana +4"]:::blames
root --> h4
me["Courier (this incident)<br/>posted +0 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.
Affected components: Hosting Infrastructure - AWS dynamodb-us-east-1Hosting Infrastructure - AWS kinesis-us-east-1Hosting Infrastructure - AWS sqs-us-east-1Hosting Infrastructure - AWS lambda-us-east-1Hosting Infrastructure - AWS elasticsearch-us-east-1
Timeline of updates
- investigating
The engineering team is currently investing and working with the support team of our provider infrastructure.
- investigating
We are continuing to investigate this issue.
- investigating
The extent of the outage with our service provider continues to increase. The team is closely monitoring.
- monitoring
Systems should be returning to a normal operating state. Our engineering team will continue to monitor.
- resolved
Services have been fully restored
Changes Rewindex caught on this incident
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).