Vonage Contact Centre (VCC) Status

Monitoring: Service is now recovered and we are monitoring. If you are still experiencing issues, please contact Support.

Investigating: We are currently aware of an ongoing issue affecting the EMEA node for the Contactpad and VCC admin portal failing to load. Our Incident Management team is investigating the issue with priority.

Monitoring: Service is now recovered and we are monitoring. If you are still experiencing issues, please contact Support.

Investigating: We are currently aware of an ongoing issue affecting the EMEA node for the Contactpad and VCC admin portal failing to load. Our Incident Management team is investigating the issue with priority.

Resolved: This issue has been resolved in Google Chrome after the new Chrome version (136.0.7103.92/.93) was deployed.

We are aware that some customers are still experiencing issues with the current stable release of Microsoft Edge. At this point in time, Microsoft have not published any communication on resolution timelines.

If you are experiencing this issue then please use one of the following options.

• Rollback Edge to a previous working version.
• Use an alternate telephony method such as PSTN.
• Use Google Chrome Beta 137 version or Google Chrome 136.0.7103.92/.93.
• Use an alternate browser such as Firefox.

Monitoring: Google have started rolling out a new Chrome version (136.0.7103.92/.93) which contains the fix for the WebRTC issue. If you have been affected by this issue, please install the new Google Chrome version.

Identified: Chromium is currently working to deploy a fixed version of Chrome 136. Currently, Chrome 137 (Beta version) is not affected by this issue.

If you are experiencing this issue then please use one of the following options.

• Rollback Chrome to 135 and pin at this version.
• Use an alternate telephony method such as PSTN.
• Use Google Chrome Beta 137 version.
• Use an alternate browser such as Firefox.

Identified: We have found an issue in Chromium browsers (Chrome and Edge) post version 135. Intermittently the browser API is very slow returning audio device information on request.

We have provided supporting information to the Chromium bug report. If you are experiencing this issue then please use one of the following options

• Rollback Chrome to 135 and pin at this version.
• Use an alternate browser such as Firefox.
• Use an alternate telephony method such as PSTN.

Investigating: The incident management team continues to investigate the issue as a top priority. If you are experiencing issues please perform the following troubleshooting:

• Rollback the latest Google Chrome version 136.
• Use an alternative browser like Firefox.
• Use other, alternative telephony methods, e.g. PSTN Please contact support for any questions.

Investigating: The incident management team continues to investigate the issue as a top priority. If you are experiencing issues please perform the following troubleshooting:

• Rollback the latest Google Chrome version 136.
• Use an alternative browser like Microsoft Edge.

Please contact support for any questions.

Investigating: We are currently aware of an ongoing issue affecting WebRTC in the EMEA, NAM and APAC regions. Our Incident Management team is investigating the issue with priority.

Monitoring: Service is now recovered and we are monitoring. If you are still experiencing issues, please contact Support.

Investigating: We are currently aware of an ongoing issue affecting the EMEA node for the Contactpad and VCC admin portal failing to load. Our Incident Management team is investigating the issue with priority.

Monitoring: Service is now recovered and we are monitoring. If you are still experiencing issues, please contact Support.

Investigating: We are currently aware of an ongoing issue affecting the EMEA node for the Contactpad and VCC admin portal failing to load. Our Incident Management team is investigating the issue with priority.

Resolved: This issue has been resolved in Google Chrome after the new Chrome version (136.0.7103.92/.93) was deployed.

We are aware that some customers are still experiencing issues with the current stable release of Microsoft Edge. At this point in time, Microsoft have not published any communication on resolution timelines.

If you are experiencing this issue then please use one of the following options.

• Rollback Edge to a previous working version.
• Use an alternate telephony method such as PSTN.
• Use Google Chrome Beta 137 version or Google Chrome 136.0.7103.92/.93.
• Use an alternate browser such as Firefox.

Monitoring: Google have started rolling out a new Chrome version (136.0.7103.92/.93) which contains the fix for the WebRTC issue. If you have been affected by this issue, please install the new Google Chrome version.

Identified: Chromium is currently working to deploy a fixed version of Chrome 136. Currently, Chrome 137 (Beta version) is not affected by this issue.

If you are experiencing this issue then please use one of the following options.

• Rollback Chrome to 135 and pin at this version.
• Use an alternate telephony method such as PSTN.
• Use Google Chrome Beta 137 version.
• Use an alternate browser such as Firefox.

Identified: We have found an issue in Chromium browsers (Chrome and Edge) post version 135. Intermittently the browser API is very slow returning audio device information on request.

We have provided supporting information to the Chromium bug report. If you are experiencing this issue then please use one of the following options

• Rollback Chrome to 135 and pin at this version.
• Use an alternate browser such as Firefox.
• Use an alternate telephony method such as PSTN.

Investigating: The incident management team continues to investigate the issue as a top priority. If you are experiencing issues please perform the following troubleshooting:

• Rollback the latest Google Chrome version 136.
• Use an alternative browser like Firefox.
• Use other, alternative telephony methods, e.g. PSTN Please contact support for any questions.

Investigating: The incident management team continues to investigate the issue as a top priority. If you are experiencing issues please perform the following troubleshooting:

• Rollback the latest Google Chrome version 136.
• Use an alternative browser like Microsoft Edge.

Please contact support for any questions.

Investigating: We are currently aware of an ongoing issue affecting WebRTC in the EMEA, NAM and APAC regions. Our Incident Management team is investigating the issue with priority.

Resolved: This issue has been resolved in Google Chrome after the new Chrome version (136.0.7103.92/.93) was deployed.

We are aware that some customers are still experiencing issues with the current stable release of Microsoft Edge. At this point in time, Microsoft have not published any communication on resolution timelines.

If you are experiencing this issue then please use one of the following options.

• Rollback Edge to a previous working version.
• Use an alternate telephony method such as PSTN.
• Use Google Chrome Beta 137 version or Google Chrome 136.0.7103.92/.93.
• Use an alternate browser such as Firefox.

Monitoring: Google have started rolling out a new Chrome version (136.0.7103.92/.93) which contains the fix for the WebRTC issue. If you have been affected by this issue, please install the new Google Chrome version.

Identified: Chromium is currently working to deploy a fixed version of Chrome 136. Currently, Chrome 137 (Beta version) is not affected by this issue.

If you are experiencing this issue then please use one of the following options.

• Rollback Chrome to 135 and pin at this version.
• Use an alternate telephony method such as PSTN.
• Use Google Chrome Beta 137 version.
• Use an alternate browser such as Firefox.

Identified: We have found an issue in Chromium browsers (Chrome and Edge) post version 135. Intermittently the browser API is very slow returning audio device information on request.

We have provided supporting information to the Chromium bug report. If you are experiencing this issue then please use one of the following options

• Rollback Chrome to 135 and pin at this version.
• Use an alternate browser such as Firefox.
• Use an alternate telephony method such as PSTN.

Investigating: The incident management team continues to investigate the issue as a top priority. If you are experiencing issues please perform the following troubleshooting:

• Rollback the latest Google Chrome version 136.
• Use an alternative browser like Firefox.
• Use other, alternative telephony methods, e.g. PSTN Please contact support for any questions.

Investigating: The incident management team continues to investigate the issue as a top priority. If you are experiencing issues please perform the following troubleshooting:

• Rollback the latest Google Chrome version 136.
• Use an alternative browser like Microsoft Edge.

Please contact support for any questions.

Investigating: We are currently aware of an ongoing issue affecting WebRTC in the EMEA, NAM and APAC regions. Our Incident Management team is investigating the issue with priority.

Resolved: This issue has been resolved in Google Chrome after the new Chrome version (136.0.7103.92/.93) was deployed.

We are aware that some customers are still experiencing issues with the current stable release of Microsoft Edge. At this point in time, Microsoft have not published any communication on resolution timelines.

If you are experiencing this issue then please use one of the following options.

• Rollback Edge to a previous working version.
• Use an alternate telephony method such as PSTN.
• Use Google Chrome Beta 137 version or Google Chrome 136.0.7103.92/.93.
• Use an alternate browser such as Firefox.

Monitoring: Google have started rolling out a new Chrome version (136.0.7103.92/.93) which contains the fix for the WebRTC issue. If you have been affected by this issue, please install the new Google Chrome version.

Identified: Chromium is currently working to deploy a fixed version of Chrome 136. Currently, Chrome 137 (Beta version) is not affected by this issue.

If you are experiencing this issue then please use one of the following options.

• Rollback Chrome to 135 and pin at this version.
• Use an alternate telephony method such as PSTN.
• Use Google Chrome Beta 137 version.
• Use an alternate browser such as Firefox.

Identified: We have found an issue in Chromium browsers (Chrome and Edge) post version 135. Intermittently the browser API is very slow returning audio device information on request.

We have provided supporting information to the Chromium bug report. If you are experiencing this issue then please use one of the following options

• Rollback Chrome to 135 and pin at this version.
• Use an alternate browser such as Firefox.
• Use an alternate telephony method such as PSTN.

Investigating: The incident management team continues to investigate the issue as a top priority. If you are experiencing issues please perform the following troubleshooting:

• Rollback the latest Google Chrome version 136.
• Use an alternative browser like Firefox.
• Use other, alternative telephony methods, e.g. PSTN Please contact support for any questions.

Investigating: The incident management team continues to investigate the issue as a top priority. If you are experiencing issues please perform the following troubleshooting:

• Rollback the latest Google Chrome version 136.
• Use an alternative browser like Microsoft Edge.

Please contact support for any questions.

Investigating: We are currently aware of an ongoing issue affecting WebRTC in the EMEA, NAM and APAC regions. Our Incident Management team is investigating the issue with priority.

Identified: We are progressing a network impairment in China affecting voice traffic. We are currently working with our carrier for resolution and await feedback.

Investigating: We are currently aware of an ongoing issue affecting inbound numbers to certain Chinese number ranges. Our Incident Management team is investigating the issue with priority.

Resolved: This issue has been resolved in Google Chrome after the new Chrome version (136.0.7103.92/.93) was deployed.

We are aware that some customers are still experiencing issues with the current stable release of Microsoft Edge. At this point in time, Microsoft have not published any communication on resolution timelines.

If you are experiencing this issue then please use one of the following options.

• Rollback Edge to a previous working version.
• Use an alternate telephony method such as PSTN.
• Use Google Chrome Beta 137 version or Google Chrome 136.0.7103.92/.93.
• Use an alternate browser such as Firefox.

Monitoring: Google have started rolling out a new Chrome version (136.0.7103.92/.93) which contains the fix for the WebRTC issue. If you have been affected by this issue, please install the new Google Chrome version.

Identified: Chromium is currently working to deploy a fixed version of Chrome 136. Currently, Chrome 137 (Beta version) is not affected by this issue.

If you are experiencing this issue then please use one of the following options.

• Rollback Chrome to 135 and pin at this version.
• Use an alternate telephony method such as PSTN.
• Use Google Chrome Beta 137 version.
• Use an alternate browser such as Firefox.

Identified: We have found an issue in Chromium browsers (Chrome and Edge) post version 135. Intermittently the browser API is very slow returning audio device information on request.

We have provided supporting information to the Chromium bug report. If you are experiencing this issue then please use one of the following options

• Rollback Chrome to 135 and pin at this version.
• Use an alternate browser such as Firefox.
• Use an alternate telephony method such as PSTN.

Investigating: The incident management team continues to investigate the issue as a top priority. If you are experiencing issues please perform the following troubleshooting:

• Rollback the latest Google Chrome version 136.
• Use an alternative browser like Firefox.
• Use other, alternative telephony methods, e.g. PSTN Please contact support for any questions.

Investigating: The incident management team continues to investigate the issue as a top priority. If you are experiencing issues please perform the following troubleshooting:

• Rollback the latest Google Chrome version 136.
• Use an alternative browser like Microsoft Edge.

Please contact support for any questions.

Investigating: We are currently aware of an ongoing issue affecting WebRTC in the EMEA, NAM and APAC regions. Our Incident Management team is investigating the issue with priority.

Identified: We are progressing a network impairment in China affecting voice traffic. We are currently working with our carrier for resolution and await feedback.

Investigating: We are currently aware of an ongoing issue affecting inbound numbers to certain Chinese number ranges. Our Incident Management team is investigating the issue with priority.

Resolved: This issue has been resolved in Google Chrome after the new Chrome version (136.0.7103.92/.93) was deployed.

We are aware that some customers are still experiencing issues with the current stable release of Microsoft Edge. At this point in time, Microsoft have not published any communication on resolution timelines.

If you are experiencing this issue then please use one of the following options.

• Rollback Edge to a previous working version.
• Use an alternate telephony method such as PSTN.
• Use Google Chrome Beta 137 version or Google Chrome 136.0.7103.92/.93.
• Use an alternate browser such as Firefox.

Monitoring: Google have started rolling out a new Chrome version (136.0.7103.92/.93) which contains the fix for the WebRTC issue. If you have been affected by this issue, please install the new Google Chrome version.

Identified: Chromium is currently working to deploy a fixed version of Chrome 136. Currently, Chrome 137 (Beta version) is not affected by this issue.

If you are experiencing this issue then please use one of the following options.

• Rollback Chrome to 135 and pin at this version.
• Use an alternate telephony method such as PSTN.
• Use Google Chrome Beta 137 version.
• Use an alternate browser such as Firefox.

Identified: We have found an issue in Chromium browsers (Chrome and Edge) post version 135. Intermittently the browser API is very slow returning audio device information on request.

We have provided supporting information to the Chromium bug report. If you are experiencing this issue then please use one of the following options

• Rollback Chrome to 135 and pin at this version.
• Use an alternate browser such as Firefox.
• Use an alternate telephony method such as PSTN.

Investigating: The incident management team continues to investigate the issue as a top priority. If you are experiencing issues please perform the following troubleshooting:

• Rollback the latest Google Chrome version 136.
• Use an alternative browser like Firefox.
• Use other, alternative telephony methods, e.g. PSTN Please contact support for any questions.

Investigating: The incident management team continues to investigate the issue as a top priority. If you are experiencing issues please perform the following troubleshooting:

• Rollback the latest Google Chrome version 136.
• Use an alternative browser like Microsoft Edge.

Please contact support for any questions.

Investigating: We are currently aware of an ongoing issue affecting WebRTC in the EMEA, NAM and APAC regions. Our Incident Management team is investigating the issue with priority.