[VoiceOps] Plivo Offline, Domain Expired; Out of Business?

Peter Beckman beckman at angryox.com
Sun Apr 23 11:49:16 EDT 2017

Looks like they are calling it a "DNS" issue -- not sure they noticed that
their whois record expired and the root servers are using NOT their DNS
servers to resolve plivo.com domains.


I wonder if it might be faster or them to get an alternative domain up as a


     We are experiencing an issue with DNS resolution of plivo.com domains
     due to a registrar renewal expiration. We are actively working on it.

     We recommend all our customers to use google DNS and
     for the following domains: api.plivo.com, phone.plivo.com,
     app.plivo.com, manage.plivo.com, sbc.plivo.com, eu.sbc.plivo.com,
     asia.sbc.plivo.com, au.sbc.plivo.com, sa.sbc.plivo.com

     Note: Other DNS resolvers may work as soon as the DNS for plivo.com are
     propagated but we cannot guarantee the TTL (refresh time) as it is out
     of our control.

     We apologize for the inconvenience, we are doing our best to get the
     service back.

 	Recommended resolution: You can hardcode the following DNS entries while we are working on resolving the issue.
 	Last update : Sun Apr 23 15:07:56 UTC 2017
 	DNS name


 	Sun Apr 23 14:18:48 UTC 2017
 	While we are working with our DNS provider for plivo.com, we are currently deploying an alternative solution to get the service back online.

 	Sun Apr 23 13:22:10 UTC 2017
 	We are working with our provider to expedite the renewal of the DNS. We will update you shortly.

Might want to watch that Google Doc for updates


On Sun, 23 Apr 2017, Peter Beckman wrote:

> We use Plivo as a monitoring tool for SMS. They've been rock-solid and
> reliable, and did a good job of letting people know if things were broken.
> Their domain expired on April 17th, and now everything in their network is
> unreachable, including their status.plivo.com site.
> Is there anyone from Plivo on the list that cares to comment? There isn't
> anything on Twitter (@plivo) mentioning that they are aware of the
> situation and working on it, which concerns me. We started noticing issues
> mid-last week, but didn't dig into it (clearly should have).
> While their disappearance isn't affecting our customers, we have lost
> visibility of our off-net to on-net SMS testing.

Peter Beckman                                                  Internet Guy
beckman at angryox.com                                 http://www.angryox.com/

More information about the VoiceOps mailing list