# Close: Degraded Dialer Performance

> Close status incident “Degraded Dialer Performance” on 2025-03-10: impact minor (vendor’s label), 25 min, 4 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/close/incidents/x7sfct92xpkx
Last updated: 2025-03-12T17:39:13Z

- Impact (vendor’s label): minor
- Status: postmortem
- Started: 2025-03-10 16:02 UTC · Resolved: 2025-03-10 16:28 UTC · Duration: 25 min
- Updates: 4 · Affected components: Dialer, Phone - Dialer
- [Vendor status page: https://stspg.io/tt0hq1wgtcth](https://stspg.io/tt0hq1wgtcth)
- [Company: Close](https://rewindex.com/company/close.md)

## Timeline of updates

- **investigating** 2025-03-10 16:02 UTC: We've become aware of degraded performance of our Dialer service. We are investigating the issue. Updates will be posted as they become available.
- **monitoring** 2025-03-10 16:21 UTC: We are continuing to investigate the cause of the degraded performance of our Dialer system. Our Dialer system is now functioning normally. We are monitoring performance.
- **resolved** 2025-03-10 16:28 UTC: This incident has been resolved.
- **postmortem** 2025-03-12 17:39 UTC: Close sincerely apologizes for the interruption of our service. We take the stability of our platform very seriously. Below is an explanation of what happened and how we will prevent another such interruption from occurring. Impact Dialer functionality was impaired for 58 minutes from 15:20 UTC to 16:18 UTC on March 10th 2025. During this time the Dialer feature could get stuck in “connecting” state. Root Cause and Resolution The issue was triggered at 15:20 UTC by a service rebalance that caused a number of client connections to close simultaneously. When these clients attempted to reconnect, the sudden spike in traffic that occurred in peak traffic conditions exceeded system limits, leading to service disruptions. Our team quickly identified the cause and worked to stabilize the system. We restored normal operations by 16:18 UTC. To prevent similar incidents in the future, we are reviewing system thresholds and improving our ability to handle sudden increases in demand. Timeline \* 15:20 UTC - a service rebalance occurs, starting a wave of new connections being established \* 15:21 UTC - a portion of requests starts getting dropped due to rate limits \* 15:28 UTC - alerts trigger and our response team began identifying the root cause \* 15:36 UTC - the rate of dropped requests subsides, but then increases again soon due to a wave-like pattern of retries \* 16:18 UTC - final wave of increased errors finishes and situation returns to normal operational levels

## Cite this

Status incident (vendor impact label: minor) posted by Close, started 2025-03-10 16:02 UTC, resolved after 25 min, 4 update(s).

- Canonical URL: https://rewindex.com/company/close/incidents/x7sfct92xpkx
- Citation: Close, “Degraded Dialer Performance” (2025-03-10 16:02 UTC). Archived by Rewindex: https://rewindex.com/company/close/incidents/x7sfct92xpkx (CC BY 4.0).
- Markdown link: `[Close: Degraded Dialer Performance (2025-03-10)](https://rewindex.com/company/close/incidents/x7sfct92xpkx)`


---
Canonical: https://rewindex.com/company/close/incidents/x7sfct92xpkx · Markdown: https://rewindex.com/company/close/incidents/x7sfct92xpkx.md · JSON: https://rewindex.com/api/v1/companies/close/incidents/x7sfct92xpkx · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T14:19:53.601Z