rewindex

CompaniesFireHydrantIncidents

FireHydrant: Phone spam causing latency issues

MinorStatus: resolvedStarted Resolved (30 h)4 updatesstatus.firehydrant.com (opens in new tab)

Timeline of updates

  1. resolved

    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.

  2. resolved

    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.

  3. monitoring

    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.

  4. monitoring

    We've applied multiple mitigations and are seeing the DDoS attack recede. Phone management has been enabled again.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.firehydrant.com (opens in new tab).

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).

Title
Phone spam causing latency issues
Vendor
FireHydrant
Date
URL
https://rewindex.com/company/firehydrant/incidents/02552946-17b5-41af-88b2-9daf36326349

FireHydrant profileRecent FireHydrant incidentsAll outages on May 26, 2026FireHydrant in May 2026MarkdownJSON