Phone spam causing latency issues

{"note"=>"**Update:**\nWe 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.\n\n**Background:**\nStarting 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.\n\nFireHydrant 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."}

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.

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.