Broadvoice Outage History

Broadvoice is up right now

Pingoru has recorded 50 incidents for Broadvoice: 7 in the last 12 months and 2 in the last 90 days.

Source: status.broadvoice.com

50incidents recorded
7last 12 months
2last 90 days
12 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct4%
Pingoru began tracking Broadvoice in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202622 of 744 (0%)
August 202600 of 744 (0%)
September 2026137 of 720 (5%)
October 2026121 of 520 (4%)

Incidents, newest first

Minor October 1, 2026 Issues with GoContact Analytics 21h 17m Reporting

Started Oct 01, 2026, 09:25 PM UTC· resolved Oct 02, 2026, 06:43 PM UTC

  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 1d 13h Device Provisioning, Device Registration

Started Sep 28, 2026, 01:23 AM UTC· resolved Sep 29, 2026, 02:38 PM UTC

  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 1h 13m Call Processing

Started Jul 14, 2026, 02:25 PM UTC· resolved Jul 14, 2026, 03:39 PM UTC

  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 18m Voice Inbound

Started Jul 13, 2026, 11:47 PM UTC· resolved Jul 14, 2026, 12:05 AM UTC

  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 2h 38m Call Processing, Call Quality, Call Recording, Communicator and 11 more

Started Jan 13, 2026, 09:57 PM UTC· resolved Jan 14, 2026, 12:36 AM UTC

  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 52m Portal

Started Jan 07, 2026, 01:33 PM UTC· resolved Jan 07, 2026, 02:26 PM UTC

  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 →

Critical January 5, 2026 P3 - Cloud NOS: PT worten.cloudcc.nos.pt - Unable to login mobile app 22h 3m Portal

Started Jan 05, 2026, 12:43 PM UTC· resolved Jan 06, 2026, 10:46 AM UTC

  1. investigating Jan 05, 2026, 12:43 PM UTC

    We are currently investigating this issue.

  2. identified Jan 05, 2026, 12:56 PM UTC

    Issue is only happening with the mobile APP. There were no interventions scheduled. We have identified via the LOGs that some users can login, so it is not affecting all of the customers. We are able to login with the Support team account login.

  3. identified Jan 05, 2026, 01:18 PM UTC

    Support team is able to replicate but DEV team is not able to replicate with the same user. We see successful login from several users. Requesting tests to the customer. DEV team login requests are reaching NGINX. Support team requests are not reaching NGINX. Support team gets the same error when trying with the 5G network. DEV team will try to replicate the domain to see live LOGs in the screen and share the results with the team once this is done.

  4. identified Jan 05, 2026, 02:12 PM UTC

    We are still waiting for DEV team to replicate the domain to see the live LOGs in the screen and share the results so that we can continue troubleshooting.

  5. identified Jan 05, 2026, 03:16 PM UTC

    DEV team continues to have difficulties to understand the root cause, changing the app to have more details about the error. New tests have started to try to reproduce the error while DEV team is trying to compile another APP version.

  6. identified Jan 05, 2026, 04:31 PM UTC

    DEV teams continues to try and determine the root cause of the issue. It could be related to NOS certificates, there is already one intervention scheduled for tonight to update some certificates in order to have fix the certificates missing in the trusted chain. Still it is not clear that the tonight's intervention will solve this current issue.

  7. identified Jan 05, 2026, 05:55 PM UTC

    We have just updated Android mobile phone to version 16 and we are now able to login using the Mobile APP in a device that was not able to access previously. We have narrowed the error... now it is only happening with Android devices with version 15 or lower. We are taking this approach as a work around, the tonight's intervention should be able to fix the error in all other devices otherwise we will need to continue the troubleshooting.

  8. identified Jan 05, 2026, 07:47 PM UTC

    Waiting for tonight's intervention (NOS Certificates Updates) to see if this is solving the problem for old Android devices with version 15 or lower.

  9. monitoring Jan 06, 2026, 09:45 AM UTC

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

  10. resolved Jan 06, 2026, 10:46 AM UTC

    This incident has been resolved. The intervention that took place to update the NOS Certificates solved the issue in all devices.

Read the full incident report →

Minor October 20, 2025 AWS outage update 18h 39m Call Processing, Call Quality, Call Recording, Communicator and 12 more

Started Oct 20, 2025, 07:58 PM UTC· resolved Oct 21, 2025, 02:37 PM UTC

  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 →

Minor July 22, 2025 The SMS service on B-Hive is currently experiencing some issues. 43m SMS

Started Jul 22, 2025, 02:44 PM UTC· resolved Jul 22, 2025, 03:27 PM UTC

  1. investigating Jul 22, 2025, 02:44 PM UTC

    We're currently experiencing issues with the SMS service on B-Hive. Our engineering teams are working to resolve it as quickly as possible.

  2. identified Jul 22, 2025, 02:55 PM UTC

    The cause has been determined, and the engineering team is now in the process of fixing it.

  3. identified Jul 22, 2025, 03:09 PM UTC

    The resolution is in progress and will be ready soon.

  4. monitoring Jul 22, 2025, 03:12 PM UTC

    The issue has been resolved and the fix applied. We’re currently monitoring the service to ensure continued stability.

  5. resolved Jul 22, 2025, 03:27 PM UTC

    All services are fully operational and stable.

Read the full incident report →

Major April 1, 2025 Incident Alert: Investigating Issue with Cloud 2 PT - Extension wasn't found on the server 6h 59m Portal, Voice Inbound

Started Apr 01, 2025, 08:30 AM UTC· resolved Apr 01, 2025, 03:30 PM UTC

  1. resolved Apr 01, 2025, 08:30 AM UTC

    Authentication issues in voice and the platform

Read the full incident report →

Minor March 28, 2025 Delays in Bhive Faxing 30m Virtual Fax

Started Mar 28, 2025, 05:10 PM UTC· resolved Mar 28, 2025, 05:40 PM UTC

  1. investigating Mar 28, 2025, 05:10 PM UTC

    We are currently investigating delays in sending and receiving faxes on the Bhive platform.

  2. identified Mar 28, 2025, 05:10 PM UTC

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

  3. resolved Mar 28, 2025, 05:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 17, 2024 Post dial delay on Bhive 3h 3m Call Processing

Started Dec 17, 2024, 09:15 PM UTC· resolved Dec 18, 2024, 12:18 AM UTC

  1. investigating Dec 17, 2024, 09:15 PM UTC

    We are currently investigating reports of long post dial delay from Bhive..

  2. resolved Dec 18, 2024, 12:18 AM UTC

    As of 2:35 PM PST today we have resolved the issue with PDD in our network.

Read the full incident report →