Broadvoice Outage History

Broadvoice is up right now

Broadvoice had 8 outages in the last 2 years totaling 104h 18m of downtime — averaging 0.3 incidents per month.

There were 8 Broadvoice outages since October 20, 2025 totaling 104h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.broadvoice.com

Minor October 1, 2026

Issues with GoContact Analytics

Detected by Pingoru
Oct 01, 2026, 09:25 PM UTC
Resolved
Oct 02, 2026, 06:43 PM UTC
Duration
21h 17m
Affected: Reporting
Timeline · 4 updates
  1. identified Oct 01, 2026, 09:25 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Oct 02, 2026, 03:21 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Oct 02, 2026, 03:22 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Oct 02, 2026, 06:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 28, 2026

Service Degradation Affecting Customer Using Polycom Devices Going Offline

Detected by Pingoru
Sep 28, 2026, 01:23 AM UTC
Resolved
Sep 29, 2026, 02:38 PM UTC
Duration
1d 13h
Affected: Device ProvisioningDevice Registration
Timeline · 5 updates
  1. identified Sep 28, 2026, 01:23 AM UTC

    We are currently investigating a service degradation with a subset of users with Polycom devices going offline. Our team is actively working to identify the impact and root cause. We will provide an update as soon as more information becomes available. We appreciate your patience as we work to resolve this issue.

  2. monitoring Sep 28, 2026, 04:35 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. identified Sep 28, 2026, 02:57 PM UTC

    The issue has been identified and a fix is being implemented.

  4. identified Sep 28, 2026, 09:25 PM UTC

    We are continuing to work on a fix for this issue.

  5. resolved Sep 29, 2026, 02:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 14, 2026

Bhive Call Park Issues

Detected by Pingoru
Jul 14, 2026, 02:25 PM UTC
Resolved
Jul 14, 2026, 03:39 PM UTC
Duration
1h 13m
Affected: Call Processing
Timeline · 5 updates
  1. investigating Jul 14, 2026, 02:25 PM UTC

    We are currently investigating an issue affecting the retrieval of parked calls in b-Hive for a specific scenario in one region. Our engineering team is actively working to identify the root cause and restore normal functionality as quickly as possible.

  2. identified Jul 14, 2026, 02:40 PM UTC

    We have identified the issue, and our engineering team is actively working to resolve it.

  3. identified Jul 14, 2026, 02:57 PM UTC

    Our engineering team has implemented a fix. Service should now be restored, and we are continuing to monitor the situation.

  4. monitoring Jul 14, 2026, 03:00 PM UTC

    We are actively monitoring the service to confirm that it remains stable and is performing as expected

  5. resolved Jul 14, 2026, 03:39 PM UTC

    The incident is resolved.

Read the full incident report →

Minor July 13, 2026

P3 - Inbound Call Routing Issue

Detected by Pingoru
Jul 13, 2026, 11:47 PM UTC
Resolved
Jul 14, 2026, 12:05 AM UTC
Duration
18m
Affected: Voice Inbound
Timeline · 2 updates
  1. investigating Jul 13, 2026, 11:47 PM UTC

    We are currently investigating this issue.

  2. resolved Jul 14, 2026, 12:05 AM UTC

    This was posted in error and there are no known issues at the current time.

Read the full incident report →

Minor January 13, 2026

Calling and Registration issues on B-hive Platform

Detected by Pingoru
Jan 13, 2026, 09:57 PM UTC
Resolved
Jan 14, 2026, 12:36 AM UTC
Duration
2h 38m
Affected: Call ProcessingCall QualityCall RecordingCommunicatorContact CenterDevice ProvisioningDevice RegistrationEdge SD-WANMobile iPhone & Android AppNotificationsPortalSIP TrunkingSMSVirtual FaxVoicemail
Timeline · 3 updates
  1. investigating Jan 13, 2026, 09:57 PM UTC

    We are currently investigating this issue.

  2. monitoring Jan 13, 2026, 10:18 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 14, 2026, 12:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 7, 2026

US-LA - CLOUD1 ipcom-coppel.gocontact.com

Detected by Pingoru
Jan 07, 2026, 01:33 PM UTC
Resolved
Jan 07, 2026, 02:26 PM UTC
Duration
52m
Affected: Portal
Timeline · 4 updates
  1. investigating Jan 07, 2026, 01:33 PM UTC

    We are currently investigating this issue.

  2. identified Jan 07, 2026, 01:40 PM UTC

    us-l1-cloud1-g3 it's not available, this is why we have the intermittent issues

  3. monitoring Jan 07, 2026, 02:03 PM UTC

    Client confirmed that the problem is solved. Still working on us-la-coresite-cloud1-g3-vpn.

  4. resolved Jan 07, 2026, 02:26 PM UTC

    We received a report of intermittent access issues with the GoContact platform. After investigation by our engineering team, we identified that one of the GoContact servers had stalled and become unresponsive, which was causing the reported issues. The affected server has been removed from the platform, and the system is now stable with no further disruptions observed. At this time, the incident does not appear to be related to the planned intervention performed earlier.

Read the full incident report →

Minor October 20, 2025

AWS outage update

Detected by Pingoru
Oct 20, 2025, 07:58 PM UTC
Resolved
Oct 21, 2025, 02:37 PM UTC
Duration
18h 39m
Affected: Call ProcessingCall QualityCall RecordingCommunicatorContact CenterDevice ProvisioningDevice RegistrationEdge SD-WANMobile iPhone & Android AppNotificationsPortalSIP TrunkingSMSWebsiteVirtual FaxVoicemail
Timeline · 3 updates
  1. identified Oct 20, 2025, 07:58 PM UTC

    We are currently monitoring a widespread AWS outage that may be impacting the performance of some of our services. While our systems remain operational, customers may experience intermittent delays or degraded performance in certain areas. Our engineering team is actively working to mitigate any impact and is closely tracking AWS’s recovery efforts. We will provide updates as more information becomes available. We appreciate your patience and understanding.

  2. monitoring Oct 21, 2025, 01:53 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Oct 21, 2025, 02:37 PM UTC

    This incident has been resolved.

Read the full incident report →