# FireHydrant: Phone spam causing latency issues

> FireHydrant status incident “Phone spam causing latency issues” on 2026-05-26: impact minor (vendor’s label), 30 h, 4 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/firehydrant/incidents/02552946-17b5-41af-88b2-9daf36326349
Last updated: 2026-05-27T20:01:11Z

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-05-26 14:28 UTC · Resolved: 2026-05-27 20:01 UTC · Duration: 30 h
- Updates: 4
- [Vendor status page: https://status.firehydrant.com/incidents/02552946-17b5-41af-88b2-9daf36326349](https://status.firehydrant.com/incidents/02552946-17b5-41af-88b2-9daf36326349)
- [Company: FireHydrant](https://rewindex.com/company/firehydrant.md)

## Timeline of updates

- **resolved** 2026-05-26 16:17 UTC: We're mitigating an advanced DDoS attack on FireHydrant's servers. We've introduced a change to prevent bad actors from attempting to add phone numbers to new accounts, and latency has returned to normal levels for FireHydrant. However, we're still being cautious about unblocking all traffic from this DDoS attack and are working toward a durable fix that will unblock functionality that was being abused. We apologize for the inconvenience and will provide an update soon.
- **resolved** 2026-05-26 21:20 UTC: We have mitigated the DDoS attack which was causing latency on FireHydrant's servers. Moreover, we've implemented a fix to restore the functionality which was temporarily inhibitied. With this restored, application and api are working normally.
- **monitoring** 2026-05-27 17:41 UTC: Update: We have seen another spike in spam account creation. To help avoid latency issues that could be caused from this attack, we have temporarily disabled the ability to set up phone notifications in FireHydrant. Background: Starting Monday, FireHydrant's on-call API was targeted as part of a DDoS attack. The attackers created tens of thousands of new FireHydrant accounts and attempted to add phone numbers at rapid scale (millions of individual phone numbers) with the intent of leveraging Signals to "page" them. FireHydrant Signals functionality has had phone verification since day one, so attackers didn't get to that point; however, the sheer volume of requests to our infrastructure caused the latency issues customers experienced, and we're truly sorry for the inconvenience.
- **monitoring** 2026-05-27 20:00 UTC: We've applied multiple mitigations and are seeing the DDoS attack recede. Phone management has been enabled again.

## Cite this

Status incident (vendor impact label: minor) posted by FireHydrant, started 2026-05-26 14:28 UTC, resolved after 30 h, 4 update(s).

- Canonical URL: https://rewindex.com/company/firehydrant/incidents/02552946-17b5-41af-88b2-9daf36326349
- Citation: FireHydrant, “Phone spam causing latency issues” (2026-05-26 14:28 UTC). Archived by Rewindex: https://rewindex.com/company/firehydrant/incidents/02552946-17b5-41af-88b2-9daf36326349 (CC BY 4.0).
- Markdown link: `[FireHydrant: Phone spam causing latency issues (2026-05-26)](https://rewindex.com/company/firehydrant/incidents/02552946-17b5-41af-88b2-9daf36326349)`


---
Canonical: https://rewindex.com/company/firehydrant/incidents/02552946-17b5-41af-88b2-9daf36326349 · Markdown: https://rewindex.com/company/firehydrant/incidents/02552946-17b5-41af-88b2-9daf36326349.md · JSON: https://rewindex.com/api/v1/companies/firehydrant/incidents/02552946-17b5-41af-88b2-9daf36326349 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T15:35:53.277Z