Past Incidents

We performed a failback of ZynoTalk's voice services to our primary cloud on Friday night, but we once again saw networking issues on Saturday, so we once again failed over to our backup provider.

Our primary cloud provider, while stable for the past 4 days, continues to acknowledge backbone issues on their status page: https://status.us.ovhcloud.com/pages/incident/59dd23da8827c804746f1664/68d599bf3bce720551d2d77c

Until they have determined the cause and a full resolution, we're going to leave voice services running on our backup provider.

When we do eventually failback to our primary provider, the transition will be performed late at night, will take approximately 5 minutes, and phones will automatically reboot to ensure a smooth handoff.

As we have stabilized any issues with the backup provider, and improved and tested our automated failover & failback workflows, we're going to close this incident as ZynoSuite & ZynoTalk customers are no longer impacted.

Around 5pm ET, our cloud provider against began experiencing intermittent issues and we failed ZynoTalk's voice services over to our backup cloud provider.

While our primary provider has been stable since 6:30pm ET, we're going to leave the ZynoTalk voice services running on our backup provider through Friday to be safe. We'll close this incident once we fully switch back.

Our cloud provider's connectivity issues seem to have smoothed out. We're continuing to monitor the situation.

We'll also be developing a plan for our systems to automatically operate across multiple providers in parallel so that we're protected against a single provider's issues causing platform outages.

Telnyx has fixed the issue as this morning and we've confirmed we're now receiving caller ID on inbound calls.