Convoso Outage History

A fix has been implemented we have all verified emails should once again be sending as expected. We apologize for any impact this may have had to your operations and thank you for your patience as we worked urgently to correct this. Customers who reported impact will receive an RFO once internal investigations conclude.

We have confirmed that full operation was restored by 3.05 pm PT, and by this time, multiple customers had advised that the issue was cleared. An RFO will be issued in due course to all reporting customers. We apologize to all affected customers for the degraded service.

After a period of monitoring, we are able to see successful logins across our servers, and all components of the platform are working properly. This incident is being closed at this time. All reporting customers will receive an RFO in due course. Convoso extends an apology to all our clients for this disruption to your operations.

The issue was identified and fully restored for all affected customers by 11.06 am PDT. An RFO will be issued in due course. We thank you for your patience as we investigated and rectified the issue.

This incident has been resolved.

We have verified network connectivity, and our backbone provider is fully operational. We apologize for this incident. Reporting clients will receive an RFO in due course.

We have confirmed the issue as resolved for all clients. We would like to take this opportunity to apologize for the disruption to your business. Also, we are acutely aware of the impact and worked as quickly as possible to restore full functionality. Thank you for your patience and understanding.

At this time we have confirmed that the issue was resolved with the prior update and will be closing out this notice. Customers who reported impact will receive an RFO as soon as possible. We apologize for the inconvenience and appreciate your patience as we worked urgently to resolve this.

At this time this issue has been resolved. We apologize for any impacts appreciate your patience who worked to resolve this.

We're pleased to report that this issue is resolved. No further impact is expected. Convoso would like to take this opportunity to apologize for the degraded service and advise that we continue to closely monitor this for continued stability. Clients who submitted a Support ticket will be sent an RFO in due course.

Our support phone line is once again available, we appreciate your patience as we worked to correct this.

As of 10:15 AM PST, work has completed to resolve any remaining routing issues. We are monitoring to validate this resolution. We apologize for any impacts this may have had operations and appreciate your patience as we worked to correct this. Customers who reported impact to our Support team will receive an RFO once internal investigations have concluded.

After appropriate monitoring and morning checks, we are satisfied that this issue has now been resolved. There will be an RFO issued to reporting clients in due course. Thank you for your patience as this issue was worked through.

The issue has been fully resolved and the fix is confirmed stable. RFO will be issued in due course to impacted clients.

After a period of intensive monitoring, we are satisfied that this incident is resolved and our platform is operating as expected. We appreciate your patience while we investigated and resolved this. Customers who reported an impact with our Support team will receive an RFO once the investigation is complete.

At this time Amazon has indicated issues with AWS Route 53 are resolved. Convoso did not see impacts from this external issue.

At this time, we have confirmed resolution and restoration of normal call handling. We appreciate your patience as we worked urgently to resolve this issue. Customers who reported impact to our Support team will receive an RFO as soon as internal investigations conclude.

At this time, we have confirmed that the adjustments made to bypass the affected external provider have restored stable connectivity for our customers. We appreciate your patience while we implemented this solution. Customers who reported impact to our Support team will receive a RFO once the investigation is complete.

At this time, we have confirmed resolution and restoration of normal call handling. We appreciate your patience as we worked urgently to resolve this issue. Customers who reported impact to our support team will receive an RFO as soon as internal investigations conclude.

As our investigations have concluded, we will close this alert at this time.

After an extensive review, we have confirmed no further impact as of 6:39 AM PST. Thank you for your understanding.

At this time we have validated resolution internally and customers should no longer see delays with call handling. We apologize for the impact this may have had on your operations and we appreciate your patience as we worked urgently to resolve this. Customers who reported impact to our support team will receive an RFO once it is completed.

Due to an outage with our ticketing provider, emails to our Support and Billing teams may not have properly created a ticket for us to assist you. We apologize for any inconvenience this may have caused. If you reached out to our team and did not get a reply or a ticket number, please create a new ticket or forward your old one to our team and we'll assist you as soon as possible. Once again we apologize for any delays in assistance and we're here to help.

At this time, the data correction should be complete. We will be sending an RFO to customers who reported impact to our support team as soon as possible. We appreciate your patience as we worked to fix and then correct the data related to this issue, and we apologize for any impact this may have had on your operations.

Our team has confirmed full resolution of login issues as of 9:50 AM PST. Customers who reported impact to our Support Team will receive an RFO as soon as internal work concludes. We apologize for any impact this may have had on your operations and appreciate your patience as we worked to resolve this issue.