In an earlier blog post I mentioned that if a customer thinks they can dump VOIP.MS for another provider (because VOIP.MS is on the receiving end of a denial-of-service attack) and thus be clear of service troubles, the customer is probably mistaken. My reason for saying this is that whoever you switch to, they could well be next in line to be attacked.
And that seems to be just what is happening. One of the unbundled VOIP providers that might be thought to be a choice for who you might switch to from VOIP.MS is Bandwidth.com. They are really big (much bigger than VOIP.MS) and I find their systems much harder to use. But for some high-volume users who can somehow figure out how to use their systems, it is possible to save quite a bit of money using Bandwidth.com as compared with VOIP.MS.
And as you can read here, a denial-of-service attacker has just now apparently selected Bandwidth.com as a target. This affects ordinary end users of the company (such as one client of our firm) and it affects quite a few downstream companies that provide a variety of retail VOIP services, bundled and unbundled, including Twilio, Accent, Dialpad, Phone.com, and RingCentral.
There are several things that can be said about this. A first is that this reinforces my sense that it would be unwise to go to the trouble of migrating away from any particular provider of unbundled VOIP services with the idea that this would somehow mean that you would then no longer need to worry about problems like this. A second is that in a weird way I think it may turn out to be really smart to migrate to VOIP.MS, once they get suitable defenses all worked out, because they will have been among the earliest of the unbundled VOIP service providers to do so. (“What does not kill me makes me stronger”, that kind of thing.)