Is Convoso down?

Last checked 2m ago
Current status
Convoso is up

No incidents right now.

Official status page: http://status.convoso.com · Polled every 5 minutes · 10 components tracked

Convoso is operational right now. Last checked 2m ago; the most recent incident resolved 25d ago.

Real-time Convoso status, recent outages, and incident history — pulled directly from Convoso's official status page at http://status.convoso.com every 5 minutes. Pingoru tracks 10 Convoso services and has captured 5 incidents in the last 90 days (99.44% uptime). Get email, Slack, Discord, or webhook alerts the moment Convoso reports a new incident — free for 5 monitors, no credit card.

Users who monitor Convoso also follow these Telephony services: Twilio Aircall Dialpad Loom Plivo Nextiva Mitel OneSignal Attentive Grasshopper View all 6,000+ providers
Convoso uptime 99.44% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 3h 23m
    Started May 19, 2026, 03:19 PM UTC · Resolved May 19, 2026, 06:42 PM UTC
    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.

    Latest: 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 tha…

  2. Resolved 33m
    Started May 01, 2026, 02:52 PM UTC · Resolved May 01, 2026, 03:25 PM UTC
    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.

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

  3. Resolved 3h 35m
    Started May 01, 2026, 01:39 PM UTC · Resolved May 01, 2026, 05:15 PM UTC
    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.

    Latest: 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 operat…

  4. Resolved 23h 11m
    Started Apr 29, 2026, 03:52 PM UTC · Resolved Apr 30, 2026, 03:03 PM UTC
    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.

    Latest: 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 f…

  5. Resolved 3h 17m
    Started Apr 15, 2026, 12:18 PM UTC · Resolved Apr 15, 2026, 03:35 PM UTC
    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.

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

Outage history

Past 90 days · 5 incidents View full outage history →