# Courier: Courier Send and Message Event Slowdown

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2025-02-13 22:32 UTC · Resolved: 2025-02-13 23:09 UTC · Duration: 36 min
- Updates: 3 · Affected components: API
- [Vendor status page: https://stspg.io/n0rt2x50z261](https://stspg.io/n0rt2x50z261)
- [Company: Courier](https://rewindex.com/company/courier.md)

## Part of an outage event

- [AWS outage, Feb 13, 2025: 11 vendors, 11 incidents](https://rewindex.com/events/2025-02-13-aws)
- This incident blames AWS as the cause. (hop 1, posted +0 min vs the first vendor naming AWS)
- Evidence: “…essage Event Slowdown The team has identified the issue related to network connections on AWS which resulted in a backup of messages on our pipeline. Messages are flowing through as expected, and the…”

```mermaid
flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>2 vendors, 1 blamed AWS<br/>Courier, Teleport"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>5 vendors, 4 blamed AWS<br/>Coralogix, SingleStore, Aptible, Snowflake +1"]:::blames
  root --> h4
  later["Later<br/>1 vendor, 1 blamed AWS<br/>Grafana Cloud"]:::blames
  root --> later
  me["Courier (this incident)<br/>posted +0 min"]:::me
  h1 --- me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **identified** 2025-02-13 22:32 UTC: The Courier team has identified a slowdown in sending notifications. This issue has been identified by our team and is closely monitoring. We do not expect any messages to drop. We will continue to monitor and update accordingly.
- **monitoring** 2025-02-13 22:51 UTC: Our team has identified a bottleneck in our system caused by timeouts on our sendworker. Our exponential backoff has caught up and messages are starting to go through.
- **resolved** 2025-02-13 23:09 UTC: The team has identified the issue related to network connections on AWS which resulted in a backup of messages on our pipeline. Messages are flowing through as expected, and the stream has caught up.


---
Canonical: https://rewindex.com/company/courier/incidents/11htlds4cqhz · Markdown: https://rewindex.com/company/courier/incidents/11htlds4cqhz.md · JSON: https://rewindex.com/api/v1/companies/courier/incidents/11htlds4cqhz · Generated 2026-10-19T23:17:14.599Z