# Discord: Message Sending Issue

> Discord status incident “Message Sending Issue” on 2018-01-19: impact none (vendor’s label), 49 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/discord/incidents/l6v0h52b7p8t
Last updated: 2018-01-19T18:37:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2018-01-19 17:48 UTC · Resolved: 2018-01-19 18:37 UTC · Duration: 49 min
- Updates: 1
- [Vendor status page: https://discordstatus.com/incidents/l6v0h52b7p8t](https://discordstatus.com/incidents/l6v0h52b7p8t)
- [Company: Discord](https://rewindex.com/company/discord.md)

## Timeline of updates

- **resolved** 2018-01-19 18:37 UTC: This won't be a long postmortem per our usual standards, but since this is the fourth time this has happened in the past two weeks I wanted to let you know what's been going on. In summary, there is a known issue in our stack when certain user behavior happens. We end up seeing Cassandra performance tank on the nodes that are serving that partition. This leads to our API servers being busy sending very slow requests to those partitions. This ends up causing the API servers to back up with requests which ends up affecting even users who aren't on the slow partitions. The fix for this generally is to implement what is called a 'circuit breaker': a timeout mechanism that blacklists the offending partition so further requests fail quickly and don't impact other users. We had rolled out some code to do that earlier in the week, but due to a bug with the implementation it didn't trigger during today's outage. We're fixing that now. Furthermore, we're also updating our procedures to make sure that when we implement these kinds of things going forward we'll have a manual testing step to ensure it actually works as intended. We wrote unit tests and everything looked good, but nobody actually verified that the functionality worked. We use Discord a lot and we know you do too. We're sorry for the interruptions that this has caused.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## Cite this

Status incident (vendor impact label: none) posted by Discord, started 2018-01-19 17:48 UTC, resolved after 49 min, 1 update(s).

- Canonical URL: https://rewindex.com/company/discord/incidents/l6v0h52b7p8t
- Citation: Discord, “Message Sending Issue” (2018-01-19 17:48 UTC). Archived by Rewindex: https://rewindex.com/company/discord/incidents/l6v0h52b7p8t (CC BY 4.0).
- Markdown link: `[Discord: Message Sending Issue (2018-01-19)](https://rewindex.com/company/discord/incidents/l6v0h52b7p8t)`


---
Canonical: https://rewindex.com/company/discord/incidents/l6v0h52b7p8t · Markdown: https://rewindex.com/company/discord/incidents/l6v0h52b7p8t.md · JSON: https://rewindex.com/api/v1/companies/discord/incidents/l6v0h52b7p8t · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T14:49:04.165Z