- Detected by Pingoru
- Aug 13, 2026, 09:08 PM UTC
- Resolved
- Aug 13, 2026, 10:05 PM UTC
- Duration
- 57m
Affected: Dialer
Timeline · 4 updates
-
investigating Aug 13, 2026, 09:39 PM UTC
We have received reports of agents unable to hear leads. We are treating this as a priority 1 issue and have a team of Engineers engaged in investigating this. Updates to follow.
-
investigating Aug 13, 2026, 10:35 PM UTC
Our investigations continue into the root cause. We are receiving reports of affected customers returning to normal operation, but we are not yet ready to declare that the issue is resolved.
-
investigating Aug 14, 2026, 12:24 AM UTC
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.
-
resolved Aug 14, 2026, 12:45 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Aug 06, 2026, 01:02 PM UTC
- Resolved
- Aug 06, 2026, 03:00 PM UTC
- Duration
- 1h 57m
Affected: Dialer
Timeline · 5 updates
-
investigating Aug 06, 2026, 01:19 PM UTC
We are receiving reports of customers unable to log in to Convoso with 500 error code: "Something went wrong". We are urgently investigating this as Priority issue.
-
monitoring Aug 06, 2026, 01:39 PM UTC
We have identified the issue and have been able to resolve the underlying cause. We are currently monitoring to ensure stability. Affected users should try again at this time. Further update to follow.
-
investigating Aug 06, 2026, 02:13 PM UTC
Reverted back to the Investigating stage as fresh reports of affected areas within our platform have been received. We have Senior Engineers and Leaders assigned to this issue and are treating this as our top priority.
-
monitoring Aug 06, 2026, 02:50 PM UTC
Users should be able to access the platform reliably at this time, but we are closely monitoring.
-
resolved Aug 06, 2026, 03:25 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jul 27, 2026, 03:54 PM UTC
- Resolved
- Jul 27, 2026, 06:06 PM UTC
- Duration
- 2h 11m
Affected: DialerCampaigns and Hopper
Timeline · 2 updates
-
investigating Jul 27, 2026, 06:15 PM UTC
We are currently investigating reports of outbound dialing degradation from a subset of our customers. We are treating this as a priority issue.
-
resolved Jul 27, 2026, 06:53 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jul 07, 2026, 06:11 PM UTC
- Resolved
- Jul 08, 2026, 02:45 AM UTC
- Duration
- 8h 33m
Affected: Campaigns and Hopper
Timeline · 2 updates
-
identified Jul 08, 2026, 12:16 AM UTC
We have identified an issue with a subset of numbers that are being used for the sending of SMS failing and displaying the error "Not registered with the TCR" when they are registered properly. This will be addressed with a code release after hours on 07/07/2026.
-
resolved Jul 08, 2026, 06:42 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 29, 2026, 04:04 PM UTC
- Resolved
- Jun 29, 2026, 04:11 PM UTC
- Duration
- 6m
Affected: Dialer
Timeline · 3 updates
-
investigating Jun 29, 2026, 04:37 PM UTC
We have received multiple reports from our clients that a subset of agents are experiencing Forced Pauses on the Agent Monitor. We are urgently investigating this.
-
monitoring Jun 29, 2026, 04:45 PM UTC
Network connectivity appears stable at present. We are continuing to closely monitor.
-
resolved Jun 29, 2026, 04:52 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2026, 11:55 PM UTC
- Resolved
- Jun 27, 2026, 01:10 AM UTC
- Duration
- 1h 15m
Affected: Dialer
Timeline · 3 updates
-
investigating Jun 27, 2026, 01:01 AM UTC
We have identified that users may be seeing a 500 error when attempting to access both the agent and admin UIs. This is a high-priority issue and we are urgently working on a resolution. Reports also include the dialer not placing outbound calls for some clients.
-
monitoring Jun 27, 2026, 01:06 AM UTC
Our Engineering team has restored service for many clients who can now login to Agent and Admin UI and outbound calls are being placed properly. We are continuing to investigate a small subset still affected.
-
resolved Jun 27, 2026, 01:19 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 01:00 PM UTC
- Resolved
- Jun 18, 2026, 02:16 PM UTC
- Duration
- 1h 15m
Affected: DialerReports and Dashboards
Timeline · 3 updates
-
identified Jun 18, 2026, 01:00 PM UTC
We have identified that users may be seeing a 500 error attempting to access both the agent and admin UIs. This is a high priority issue and we are urgently working on a resolution.
-
monitoring Jun 18, 2026, 01:05 PM UTC
This issue should be resolved but we are closely monitoring to validate full resolution.
-
resolved Jun 18, 2026, 02:16 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 12:50 PM UTC
- Resolved
- Jun 19, 2026, 12:58 PM UTC
- Duration
- 1d
Timeline · 3 updates
-
monitoring Jun 18, 2026, 12:50 PM UTC
Our team is aware of a delay with last night's FTP pushes for call recordings. A fix is actively being deployed and monitored at this time, with FTP pushes occurring this morning instead. We apologize for any inconvenience this may cause and will update here once work has completed.
-
monitoring Jun 18, 2026, 01:20 PM UTC
Work continues to resolve this issue, but please note the automated pushes may take some time. If recordings are needed sooner, manual pushes can be utilized by your team.
-
resolved Jun 19, 2026, 12:58 PM UTC
At this time this issue has been resolved. We apologize for any impacts appreciate your patience who worked to resolve this.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 03:19 PM UTC
- Resolved
- May 19, 2026, 06:42 PM UTC
- Duration
- 3h 23m
Affected: Dialer
Timeline · 4 updates
-
investigating May 19, 2026, 04:33 PM UTC
We are currently investigating reports of high agent wait times. Engineering teams are engaged as a priority event. More updates wil be provided as the investigation progresses.
-
identified May 19, 2026, 04:48 PM UTC
The issue has been identified, and remediation efforts are already underway.
-
identified May 19, 2026, 06:47 PM UTC
The backend work to resolve this issue is almost complete, and many clients will already have seen an improvement in agent wait times. We will confirm once it is fully resolved.
-
resolved May 19, 2026, 08:51 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 01, 2026, 02:52 PM UTC
- Resolved
- May 01, 2026, 03:25 PM UTC
- Duration
- 33m
Timeline · 2 updates
-
identified May 01, 2026, 02:52 PM UTC
Our support phone line is currently down due to emergency maintenance. Our team is ready to assist via email and chat. We apologize for the inconvenience and we will close this out once the maintenance is complete.
-
resolved May 01, 2026, 03:25 PM UTC
Our support phone line is once again available, we appreciate your patience as we worked to correct this.
Read the full incident report →
- Detected by Pingoru
- May 01, 2026, 01:39 PM UTC
- Resolved
- May 01, 2026, 05:15 PM UTC
- Duration
- 3h 35m
Affected: Dialer
Timeline · 3 updates
-
identified May 01, 2026, 03:29 PM UTC
Our team has identified an issue where a small collection of DIDs may experience inbound calls not properly routing. This is being handled as a Priority 1 Issue and we are actively correcting this across all affected accounts. We apologize for any impact this may cause and will provide updates as work progresses.
-
identified May 01, 2026, 04:27 PM UTC
Our team continues work to urgently resolve routing issues with the subset of impacted DIDs, with many already corrected.
-
resolved May 01, 2026, 05:20 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 03:52 PM UTC
- Resolved
- Apr 30, 2026, 03:03 PM UTC
- Duration
- 23h 11m
Affected: Dialer
Timeline · 4 updates
-
investigating Apr 29, 2026, 04:36 PM UTC
We are currently urgently investigating reports of intermittent audio degradation audio while on calls. This is being treated as a Priority 1 incident and work is ongoing to resolve.
-
investigating Apr 29, 2026, 06:56 PM UTC
Our investigation and examination remains ongoing, and we are still treating this as a priority event, and have engaged several external partners in addition to our own Engineering and Carrier teams.
-
monitoring Apr 29, 2026, 11:45 PM UTC
We continue to monitor this issue and are working closely with our providers and carriers. There have been no fresh reports submitted for multiple hours at this point. We are not yet ready to state this as resolved however, until a longer monitoring phase has been completed.
-
resolved Apr 30, 2026, 03:03 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 12:18 PM UTC
- Resolved
- Apr 15, 2026, 03:35 PM UTC
- Duration
- 3h 17m
Affected: Dialer
Timeline · 4 updates
-
investigating Apr 15, 2026, 01:55 PM UTC
We are currently aware of an issue affecting a subset of clients related to Registration errors and transferring calls. Our Engineering team is engaged, and we are treating this issue as a Priority. Updates to follow.
-
monitoring Apr 15, 2026, 02:13 PM UTC
We have identified the root cause and have corrected the issue. We are currently monitoring to ensure the resolution is complete and stable.
-
identified Apr 15, 2026, 03:06 PM UTC
We have reverted the stage as we have identified an additional instance of the concern, which we are investigating as a priority.
-
resolved Apr 15, 2026, 03:47 PM UTC
The issue has been fully resolved and the fix is confirmed stable. RFO will be issued in due course to impacted clients.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 04:59 PM UTC
- Resolved
- Mar 02, 2026, 07:08 PM UTC
- Duration
- 2h 9m
Affected: Campaigns and Hopper
Timeline · 3 updates
-
investigating Mar 02, 2026, 05:23 PM UTC
We have received reports of Agent Monitor being slow to load and/or not loading at all. This is under active investigation as a priority issue. Updates will be posted once available.
-
monitoring Mar 02, 2026, 06:08 PM UTC
We have isolated the issue and made adjustments to resolve this. We are currently monitoring closely to ensure platform stability and responsiveness.
-
resolved Mar 02, 2026, 07:42 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 04:50 PM UTC
- Resolved
- Mar 03, 2026, 12:12 AM UTC
- Duration
- 7h 22m
Affected: AWS route53
Timeline · 2 updates
-
monitoring Mar 02, 2026, 04:50 PM UTC
We are closely monitoring reports of Degraded Performance with Amazon AWS Route 53 services. At this time we are not seeing any impacts to the Convoso platform.
-
resolved Mar 03, 2026, 12:12 AM UTC
At this time Amazon has indicated issues with AWS Route 53 are resolved. Convoso did not see impacts from this external issue.
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 02:09 PM UTC
- Resolved
- Feb 27, 2026, 03:07 PM UTC
- Duration
- 58m
Affected: Dialer
Timeline · 3 updates
-
investigating Feb 27, 2026, 02:38 PM UTC
We are currently investigating reports of delays with call connections, treating this as a priority issue, and have engaged our engineering resources. We will provide updates as they become available.
-
monitoring Feb 27, 2026, 03:07 PM UTC
We have identified and corrected an issue and are actively monitoring for stability, and are seeing wait times for calls connecting return to normal levels.
-
resolved Feb 27, 2026, 03:30 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 06:07 PM UTC
- Resolved
- Feb 20, 2026, 06:40 PM UTC
- Duration
- 32m
Affected: DialerCampaigns and HopperScriptsAPIWorkflow AutomationLeadsReports and Dashboards
Timeline · 3 updates
-
identified Feb 20, 2026, 06:26 PM UTC
We have identified intermittent platform disconnects impacting our customers. We have escalated this internally and are treating this as a Priority 1 issue.
-
monitoring Feb 20, 2026, 06:30 PM UTC
We have identified an external network issue and have deployed a fix to avoid this provider. We are monitoring closely to validate full resolution. This issue is impacting other providers and is not specific to Convoso.
-
resolved Feb 20, 2026, 06:40 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 03:26 PM UTC
- Resolved
- Feb 19, 2026, 05:59 PM UTC
- Duration
- 2h 33m
Affected: Dialer
Timeline · 3 updates
-
investigating Feb 19, 2026, 04:42 PM UTC
We have identified a rise in congestion status calls. We are urgently investigating this as a Priority 1 issue at this time and will provide updates as work progresses.
-
monitoring Feb 19, 2026, 05:13 PM UTC
A fix has been deployed and we are closely monitoring to validate resolution.
-
resolved Feb 19, 2026, 05:59 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jan 31, 2026, 12:11 AM UTC
- Resolved
- Feb 05, 2026, 01:38 AM UTC
- Duration
- 5d 1h
Affected: Dialer
Timeline · 2 updates
-
investigating Jan 31, 2026, 12:11 AM UTC
We have completed our investigation into an increase in CG status calls observed by some customers. This behavior appears to be isolated in nature and is related to the deployment of spam blocking applications by endpoint carriers. Impact to customers is not widespread. We are running additional analytics and will reach out directly to affected customers to discuss next steps.
-
resolved Feb 05, 2026, 01:38 AM UTC
As our investigations have concluded, we will close this alert at this time.
Read the full incident report →
- Detected by Pingoru
- Nov 24, 2025, 02:39 PM UTC
- Resolved
- Nov 24, 2025, 04:01 PM UTC
- Duration
- 1h 22m
Affected: Reports and Dashboards
Timeline · 3 updates
-
investigating Nov 24, 2025, 02:32 PM UTC
We have received reports of data exports returning with zero bytes of data. We are investigating.
-
monitoring Nov 24, 2025, 02:48 PM UTC
A fix has been implemented and our team is closely monitoring to verify full resolution.
-
resolved Nov 24, 2025, 04:01 PM UTC
After an extensive review, we have confirmed no further impact as of 6:39 AM PST. Thank you for your understanding.
Read the full incident report →
- Detected by Pingoru
- Oct 23, 2025, 08:41 PM UTC
- Resolved
- Oct 23, 2025, 09:48 PM UTC
- Duration
- 1h 7m
Affected: Dialer
Timeline · 3 updates
-
identified Oct 23, 2025, 09:19 PM UTC
Our team is urgently working to resolve an issue that may cause delays to call handling. We have identified the source of the trouble and are working to restore service levels. This is a priority 1 issue.
-
monitoring Oct 23, 2025, 09:36 PM UTC
Our team has implemented a fix and are we are closely monitoring to validate full resolution.
-
resolved Oct 23, 2025, 09:48 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Oct 13, 2025, 06:13 PM UTC
- Resolved
- Oct 13, 2025, 06:13 PM UTC
- Duration
- —
Affected: Billing
Timeline · 1 update
-
resolved Oct 13, 2025, 06:13 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Sep 29, 2025, 06:32 PM UTC
- Resolved
- Oct 01, 2025, 05:53 PM UTC
- Duration
- 1d 23h
Affected: Leads
Timeline · 4 updates
-
identified Sep 29, 2025, 06:32 PM UTC
We have identified an issue with phone type detection for Leads (Landline, Mobile, etc). A fix has been applied, so new Leads will have the correct data. We are working urgently to correct the data for existing Leads. Customers may not be able to send SMS to affected leads until the Lead is corrected.
-
identified Sep 29, 2025, 11:10 PM UTC
Our team continues work to adjust the phone type of existing Leads back to their correct value. We will continue working on this throughout the night and we aim to have this resolved as soon as possible. As a reminder, new Leads will be inserted with the correct phone type.
-
identified Sep 30, 2025, 04:28 PM UTC
We continue to correct existing lead data, primarily overnight, to reduce impact to operations.
-
resolved Oct 01, 2025, 05:53 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Sep 26, 2025, 02:06 PM UTC
- Resolved
- Sep 26, 2025, 04:50 PM UTC
- Duration
- 2h 44m
Affected: DialerReports and Dashboards
Timeline · 6 updates
-
investigating Sep 26, 2025, 03:02 PM UTC
We are currently investigating reports of issues logging into the platform. We are treating this as a P1 event.
-
investigating Sep 26, 2025, 03:27 PM UTC
We have our engineering team actively engaged on resolving this issue.
-
identified Sep 26, 2025, 03:57 PM UTC
Our team is actively deploying a fix for users who may be unable to login at this time. We apologize for any impact this may have on your operations as we work urgently to resolve.
-
identified Sep 26, 2025, 04:00 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Sep 26, 2025, 04:48 PM UTC
A fix has been fully deployed and users should see little to no further impact as they log in. We are actively monitoring this issue closely to verify full resolution.
-
resolved Sep 26, 2025, 05:24 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Sep 12, 2025, 04:38 PM UTC
- Resolved
- Sep 12, 2025, 05:08 PM UTC
- Duration
- 30m
Affected: Dialer
Timeline · 2 updates
-
monitoring Sep 12, 2025, 05:13 PM UTC
We have identified intermittent pausing and delays in dialing and immediately raised this as Priority 1 issue. The root cause has been identified and a fix has been applied. We are monitoring closely to confirm full resolution.
-
resolved Sep 12, 2025, 05:27 PM UTC
A fix was deployed at 10:08 AM PST, and we have confirmed no further impact at this time. Customers who reported impact to Support will receive an RFO as soon it is completed. We appreciate your patience as we worked to resolve this issue and we apologize for any impact this may have had on your operations.
Read the full incident report →