Historical record of incidents for Fuze
Report: "Fuze Incident - Issue with Fuze Data"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We are now detecting some degraded performance on our Data platform. This may impact end-user services. We are working diligently to address the issue and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
We have implemented a fix for the issue, and expect that all services are functioning as expected. Some data may not be immediately available as the backlog is processed. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We are experiencing an outage on our Data platform. This will impact end-user services. Data.fuze.com is currently not available. We are working diligently to identify the cause of the issue and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Android mobile application not alerting while in background"
Last updateThis incident has been resolved and service has been restored to normal operation. We apologize for any inconvenience caused.
We are continuing to work on a fix for this issue.
We continue our work on the solution to the issue but more effort is still required to reach service restoration. The next update will be provided by 14:00 UTC tomorrow, 12th of Sep (10:00 US Eastern Time).
We continue to work on the solution to the issue in order to restore services to normal. Thank you for your patience while we work to get this issue resolved. We will provide further updates as they become available.
The issue has been identified and a fix is being implemented. We thank you for your patience as we continue to work on this issue and will provide updates as they become available.
We're still working through this issue and we apologize for any inconvenience caused. The next update will be provided by 11:00 UTC.
We thank you for your patience as we work through this issue. We are continuing to investigate the problem and will provide an update by 09:00 UTC. We apologise for any inconvenience caused.
We are taking steps to try to rectify the issue. We apologize for the inconvenience caused. We will continue to provide further updates.
Our internal teams are continuing to look into this issue. We will continue to provide updates as soon as they are available. We appreciate your patience and understanding.
We continue to troubleshoot this issue. Thank you for your continued patience. We will provide further updates once they become available.
We thank you for your continued patience as we investigate this issue. We will continue to provide updates as we progress.
We are continuing to investigate the issue. We will provide further details once they become available. We apologize for any inconvenience caused.
We are currently investigating a reported issue with the Fuze mobile application not alerting for incoming calls or messages when the app is in the background. We will provide further updates once they become available. We apologize for any inconvenience caused.
Report: "Fuze Incident - Issue with Call Parking"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 774. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 774. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We continue to work on a solution to the issue in order to restore services to normal. Thank you for your patience while we work to get this issue identified and resolved.
We have identified a potential cause of the issue and are actively working to resolve it as quickly as possible. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We continue to investigate the issue in order to determine the cause. Thank you for your patience while we work to get this issue identified and resolved.
We are receiving reports of some degraded performance on our platform. Users may be unable to use the park call feature. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with outbound calling"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 8474. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 8474. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We continue to investigate the issue in order to determine the cause. Thank you for your patience while we work to get this issue identified and resolved.
We are currently investigating reports that a subset of users are unable to make outbound calls. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Fuze Desktop/Web"
Last updateWe have had no further reports of the issue and now all services are functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that the services are recovering as expected. We will monitor this incident before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have identified a potential cause of the error message stating "unable to connect to the server" when accessing Fuze Desktop and Fuze Web and we are actively working to resolve it as quickly as possible. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We are continuing to investigate this issue.
We are currently investigating reports that a subset of users are receiving an error message indicating that they are "unable to connect to the server" when accessing Fuze Desktop and Fuze Web. We are working diligently to identify the cause of the issue and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Queues"
Last updateWe have resolved the issue, and expect that all services are functioning normally. Internal tests have also confirmed all services running as normal Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue and services are now recovered. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 8229. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue and services are recovering. During this time users may experience some latency with logging into call queues, Chat services, Chat History, Push Notifications, and Presence sync. The team will continue to do final system recovery to eliminate any remaining latency. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 8229. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We continue to work on a solution to the issue. Thank you for your patience while we work to get this issue identified and resolved.
We continue to work to restore services to normal. Thank you for your patience while we work to get this issue resolved.
We have identified the cause of the issue and are actively working to resolve it as quickly as possible. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved. Users can still log in and out of queues using star codes: *501 Login a queue member to all queues they are a part of dynamically. *500 Logout a queue member from all queues they are a part of dynamically. *571 Pause a queue member in all queues they are a part of dynamically. *570 UnPause a queue member in all queues they are part of dynamically.
We continue to investigate the issue in order to determine the cause. End Users can still log in and out of queues using star codes: *501 Login a queue member to all queues they are a part of dynamically. *500 Logout a queue member from all queues they are a part of dynamically. *571 Pause a queue member in all queues they are a part of dynamically. *570 UnPause a queue member in all queues they are part of dynamically. Thank you for your patience while we work to get this issue identified and resolved.
We are currently investigating reports that a subset of users are experiencing problems on our Chat and Contact Center platforms. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
We are currently investigating reports that a subset of users are experiencing problems on our Contact Center platform. This may impact end-user services. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Calling"
Last updateWe have confirmed with our third-party cloud provider that the issue is now resolved. If you are still encountering issues please contact Fuze support. We appreciate your patience with us as we worked to resolve this issue.
We are continuing to monitor the recovery of services. We thank you for your patience as we confirm the resolution of the issue.
We are seeing some recovery in the services. We will continue to monitor until we are confident that the issue is resolved. We thank you for your patience while we work through this issue.
The third-party provider is continuing to work on resolving the issue. We will continue to provide updates as they become available. Thank you for your patience.
We are continuing to work with our third-party provider toward fully resolving the issue. Thank you for your continued patience and we will continue to provide regular updates.
The third-party provider is continuing to work toward fully resolving the issue and has seen some positive gains with their mitigation steps. Thank you for your continued patience and we will continue to provide regular updates.
The third-party provider has identified the issue and is currently working on resolving it. We will continue to provide regular updates as the third-party works to resolve the issue and service is returned to normal. Thank you for your continued patience.
We continue to work with the third-party cloud provider on a solution to the issue in order to restore services to normal. Thank you for your patience while we work to get this issue identified and resolved.
We continue to work with the third-party on a solution to the issue in order to restore services to normal. Thank you for your patience while we work to get this issue identified and resolved.
We have identified a potential cause of the issue and are actively working with the third-party to resolve it as quickly as possible. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We are currently investigating reports that a subset of problems on our Calling platform. This may impact end-user services. Symptoms may include one way audio or calls not connecting. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Fuze Contact Center"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 8148. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 8148. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have identified the issue and are actively working to resolve it as quickly as possible. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We are currently investigating reports that a subset of users are unable to access the Fuze Contact Center platform. We are working diligently to identify the issue and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience. Users can still log in and out of queues using star codes: *501 Login a queue member to all queues they are a part of dynamically. *500 Logout a queue member from all queues they are a part of dynamically. *571 Pause a queue member in all queues they are a part of dynamically. *570 UnPause a queue member in all queues they are part of dynamically.
Report: "Fuze Incident - Issue with Fuze Data / Data API"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident IM-2876. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue during the emergency maintenance, and expect that all services are functioning as expected. We will monitor this incident overnight before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident IM-2876. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
Fuze will be performing emergency maintenance on our Data and REST API reporting platforms to address the issues we have been experiencing since Friday afternoon. What will you experience during the work? Our temporary solution will be removed during this period in order for the maintenance to progress. Users may experience an interruption to Fuze reporting services for the duration of the maintenance. Reports scheduled during the maintenance period will be delayed until completion. When are we doing this? Start: Monday, June 26th 15:00 EST (GMT-5) End: Monday, June 26th 17:00 EST (GMT-5) What happens if it doesn't go as planned? Maintenance will be reverted and the temporary solution will be reinstated Who should you contact with questions? Please reach out to us; we would be happy to talk to you! U.S. Toll-Free +1 866 379 9442 United States +1 617.603.2299 Australia +61 2 8607 8029 France +33 97 518 6686 Germany +49 32 22 109 6038 Greece +30 211 198 3039 Ireland +353 76 888 7202 Israel +972 3 763 0658 Italy +39 02 94 75 2581 Japan +81 34 589 4674 Netherlands +31 20 241 0144 United Kingdom +44 330 808 0131 or visit our support page at fuzecommunity.force.com/support
We are continuing to investigate the issue in order to determine the root cause. Our temporary solution will remain in place until a resolution is achieved Thank you for your patience while we work to get this issue identified and resolved.
We are continuing to investigate the issue in order to determine the cause. At this time, we have deployed a temporary solution to alleviate the issues being experienced while we continue to identify and resolve this issue. In the interim, users may periodically be logged out of Fuze Data and be required to log back in to reinitiate the session. Thank you for your patience while we work to get this issue identified and resolved.
We are detecting some degraded performance on our Data and Data API platforms. This may impact end-user services. Expected symptoms include Fuze Data not loading periodically and the Data API not exporting records. We are working diligently to identify the cause of the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Fuze Discover Displaying Data"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident IM-2878. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have identified a potential cause of the issue and are actively working to resolve it as quickly as possible. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We are detecting some degraded performance on our Fuze Discover platform. This may impact admin services. Expected symptoms will include not being able to report against data processed on June 25th for calls, meetings, and queue data. We are working diligently to identify the cause of the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with FuzeCC"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident INC-5495. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident INC-5495. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We are experiencing a partial outage on our FuzeCC platform for Fuze Desktop, Web, and Mobile. This will impact end-user services. Expected symptoms will include not being able to visualize queues and agents within FuzeCC as well as being unable to use FuzeCC to log in/out, and pausing/unpausing for queues. Star codes are not impacted by this outage, included below are four customer-wide star codes that all customers can use for their agents in the interim while we continue to investigate this issue. *501 - dynamic log in *500 - dynamic log out *571 - dynamic pause *570 - dynamic unpause We are working diligently to identify the cause of the issue and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Fuze Discover"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5492. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5492. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We are detecting some degraded performance on our Fuze Discover platform. This may impact admin services. Expected symptoms will include not being able to report against large data sets such as data over long periods of time or heavy utilization. Fuze View (data.fuze.com) is not impacted by this issue. We are working diligently to identify the cause of the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Presence for Fuze Desktop/Web"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident INC-5490. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident INC-5490. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We are currently investigating reports that a subset of users are experiencing presence problems on our Desktop and Web applications. This may impact end-user services. Expected symptoms will include delays to presence updates such as "On a call" and "In a meeting" or appearing as "Unknown". Calling and messaging functionality is not impacted by this issue. We are working diligently to identify the cause of the issue and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Fuze Discover Displaying Data"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident INC-5489. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have received reports that Fuze Discover is now working as intended, and expect that all services are functioning as expected. We will continue to monitor this incident until we have verified that no further issues will occur. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident INC-5489. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We continue to work on a solution to the issue in order to restore services to normal. At this time, we have determined that call, meeting, and queue data is taking longer than expected to process into Fuze Discover and that certain scheduled reports are not being sent via email. Thank you for your patience while we work to get this issue identified and resolved.
We have identified a potential cause of the issue with a third-party provider and can confirm at this time that all data for March 19th is now populating within Fuze Discover as intended. We will continue to provide updates as we have them regarding our progress in determining the root cause of this issue. Thank you for your patience while we work to get this issue resolved.
We are detecting some degraded performance on our Fuze Discover platform. This may impact admin services. Expected symptoms will include not being able to report against data processed on March 19th for calls, meetings, and queue data. Fuze View (data.fuze.com) is not impacted by this issue. We are working diligently to identify the cause of the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with sound files"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We are detecting some degraded performance on our Portal and Hub platforms. Expected symptoms are sound files cannot be played or uploaded to the portal and Hub. We are working diligently to identify the cause of the issue and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Calling"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5471. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We continue to investigate the issue in order to determine the cause. Thank you for your patience while we work to get this issue identified and resolved.
We are detecting some degraded performance on our Calling platform. This will impact end-user services. Users may be unable to place calls. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Fuze Hub"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5429. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5429. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We continue to work on a solution to the issue in order to restore services to normal. Thank you for your patience while we work to get this issue identified and resolved.
We have identified a potential cause of the issue and are actively working to resolve it as quickly as possible. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We are currently investigating reports that a subset of users are unable to access the Fuze Hub platform. This will not impact end-user services. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Outage on our Hub platform"
Last updateWe can confirm that the service is now operational as usual. Please let our support team know if you encounter any further issues. May thanks
We are experiencing an outage on our Hub platform. End-user services may be impacted. We are working diligently to identify the cause of the issue and will provide regular updates as we have them. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Fuze Hub"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We are experiencing an outage on our Hub platform. End-user services are not impacted. We are working diligently to identify the cause of the issue and will provide regular updates as we have them. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Degraded Performance"
Last updateWe have implemented a fix for the issue, and expect that all services are functioning as expected. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5390. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services will begin to function as expected as the system catches up on the backlog of notifications over the next hour. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services will begin to function as expected as the system catches up on the backlog of notifications. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5390. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have identified the cause of the issue and are actively working to resolve it as quickly as possible. Expected symptoms may include the following: - Chat messages being delayed in sending or chat messages failing to load - Presence not updating correctly - Intermittent "Meetings are not available" banner being displayed with Meetings being slow to join. Users may also experience issues with in-meeting actions (mute, unmute, share screen, etc) - Fuze CC being unresponsive for agents and supervisors. Agents are confirmed to still be able to login/pause/un-pause via Star Code We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We are detecting some degraded performance on our Chat, Presence, and Meetings platforms at this time. This may impact end-user services. Expected symptoms may include the following: - Chat messages being delayed in sending or chat messages failing to load - Presence not updating correctly - Intermittent "Meetings are not available" banner being displayed with Meetings being slow to join. Users may also experience issues with in-meeting actions (mute, unmute, share screen, etc) - Fuze CC being unresponsive for agents and supervisors. Agents are confirmed to still be able to login/pause/un-pause via Star Code We are working diligently to identify the cause of the issue and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Chat, Presence, and Meetings"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5389. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services will begin to function as expected as the system catches up on the backlog of notifications. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5389. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have identified the cause of the issue and are actively working to resolve it as quickly as possible. Expected symptoms may include the following: - Chat messages being delayed in sending or chat messages failing to load - Presence not updating correctly - Intermittent "Meetings are not available" banner being displayed with Meetings being slow to join. Users may also experience issues with in-meeting actions (mute, unmute, share screen, etc) - Fuze CC being unresponsive for agents and supervisors. Agents are confirmed to still be able to login/pause/un-pause via Star Code We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We are detecting some degraded performance on our Chat, Presence, and Meetings platforms at this time. This may impact end-user services. Expected symptoms will include chat messages being delayed in sending or chat messages failing to load, Presence not updating correctly, and intermittent "Meetings are not available" banner being displayed with Meetings being slow to join. We are working diligently to identify the cause of the issue and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
We are detecting some degraded performance on our Chat platform at this time. This may impact end-user services. Expected symptoms will include chat messages being delayed in sending or chat messages failing to load. We are working diligently to identify the cause of the issue and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Nice InContact"
Last updateThis incident has been resolved.
We have identified the issue with InContact and a workaround is available. Please reach out to support to have it applied if users are still experiencing issues.
InContact customers in EMEA may be experiencing one way audio on calls. We are working with InContact to direct traffic to a different datacenter in order to restore services to normal. Thank you for your patience while we work to get this issue resolved.
Report: "Fuze Incident - Continued Issue with Legacy Fuze Contact Center"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5338. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. In order for the fix to be applied, please re-download Legacy Fuze Contact Center (FCC) from the Fuze Portal (Support - FCC Support) and click on the JNLP file link. Once the application is reinstalled, you will be able to access the system without any further issues. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5338. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We are currently investigating reports that a subset of users are continuing to experience connection problems on our Legacy Fuze Contact Center (FCC) platform. This may impact end-user services. Expected symptoms will include receiving an error message when launching Legacy Fuze Contact Center regarding an expired certificate. At this time, Fuze CC (based out of Fuze Desktop/Web) is not experiencing this issue and will continue to work as expected. In the interim, we have identified a temporary workaround that several customers have had success with. If you are currently facing this issue please reach out to our Support team and reference Incident 5338 so that an engineer can provide you with the necessary steps in a PDF. We are working diligently to identify the cause of the issue and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Legacy Fuze Contact Center"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5338. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5338. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have identified the cause of the issue and are actively working to resolve it as quickly as possible. In the interim, we have identified a temporary workaround. If you are currently facing this issue please reach out to our Support team and reference Incident 5338 so that an engineer can provide you with the necessary steps in a PDF. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We are currently investigating reports that a subset of users are experiencing connection problems on our Legacy Fuze Contact Center (FCC) platform. This may impact end-user services. Expected symptoms will include receiving an error message when launching Legacy Fuze Contact Center regarding an expired certificate. At this time, Fuze CC (based out of Fuze Desktop/Web) is not experiencing this issue and will continue to work as expected. We are working diligently to identify the cause of the issue and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Polycom Device Claim / ZTP (Zero Touch Provisioning)"
Last updateThis incident has been resolved.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5336. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have identified the cause of the issue and are actively working with the manufacturer to resolve it as quickly as possible. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We are currently experiencing an outage on our DPS platform due to a manufacturer updating their ZTP solution. This will impact end-user services. Expected symptoms will include being unable to use Device Claim in the Hub for Polycom devices. Device Claim for Yealink devices is not impacted at this time. We are working diligently with the manufacturer on this issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Intermittent issue with Portal"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We are performing a rolling restarting the Fuze Portal service, some users may get bumped back to the log in screen during this process. Please login to the portal if necessary.
We have identified a potential cause of the issue and are actively working to resolve it as quickly as possible. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We are experiencing a partial outage on our Portal platform. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience. If you attempt an action using the portal and get an error, please refresh and try again.
Report: "Fuze Incident - Issue with Portal"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have identified a potential cause of the issue and are actively working to resolve it as quickly as possible. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We are experiencing a partial outage on our Portal platform. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Portal"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5312.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5312. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We are continuing to work on a solution to the issue in order to restore services to normal. At this time the portal is available, but performance may be degraded. Thank you for your patience while we work to get this issue resolved.
We have identified the cause of the issue and are actively working to resolve it as quickly as possible. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We are experiencing a partial outage on our Portal platform. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Hub"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5278.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5278. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We are receiving reports that users are unable to make changes to services, create new services, or delete services in the Hub We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with making/receiving calls"
Last updateAfter continued monitoring there was no sign of an issue on the Fuze network
After investigation we have found no issues with Fuze Voice services. Customers may be experiencing local carrier connectivity related issues. If you continue to experience issues please reach out to Fuze Support for assistance.
We are experiencing a partial outage on our Calling platform. This will impact some end-user services. Impacted customers will not be able to make or receive calls We are working diligently to identify the cause of the issue and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Call History Developer API"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5266.
We have implemented a fix for the issue, and expect that all API services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5266. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have identified a potential cause of the issue and are actively working to resolve it as quickly as possible. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We continue to investigate the issue in order to determine the cause. Thank you for your patience while we work to get this issue identified and resolved.
We are currently investigating reports that a small subset of customers are unable to access call history through the Developer API. Attempting to get call history from the Developer API will get a timeout error (HTTP 408). This will not affect end-user calling, meetings, or chat services. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Meetings and Chat"
Last updateThis incident has been resolved. If you are continuing to experience any issues please first restart your Fuze application and then raise with Fuze support, referencing the ticket ID INC-5244.
As services are now restored we will move this incident into monitoring. If you continue to experience issues please liaise with Fuze Support and reference ticket ID INC-5244
We are seeing recovery of all systems across Fuze. However some minor components, such as Call History, may take a longer period of time to restore. We do not expect this to continue impacting major services such as Calling, Queue Login/out or Meetings. If you are still experiencing issues with with presence or contact loading, please restart your Fuze Desktop application. If issues are still occurring please raise with Fuze Support and reference the ID INC-5244
We have identified the fault of the issue and are proceeding to implement a fix and restore services. We will continue to provide updates as service is restored. Thank you for your continued patience.
We are continuing to investigate this issue and will continue to provide updates as soon as we have them. Thank you for your continued patience as this issue is being addressed.
We are continuing to investigate this issue and will provide regular updates as and when we have them. Thank you for your continued patience as we work to resolve this issue.
We are detecting some degraded performance on our Chat & Meetings platform. This may impact end-user services. Possible symptoms include an inability to create/join Fuze meetings and delayed chat messages. We are working diligently to identify the cause of the issue and will provide regular updates, as we have them, until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Platform Stability"
Last updateWe have had no further reports of the issue and show all services as functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5211.
We are continuing to monitor for any further issues.
Amazon Web Services have implemented a fix and we are now seeing service being restored. We will continue to monitor this incident for another 30 minutes before closing. If you are experiencing any related issues please contact Fuze Support and reference INC-5210.
We are detecting some degraded performance on our Calling & Meetings platform. This is due to ongoing issues with Amazon Web Services. This may impact end-user services. Possible symptoms may include a delays in calls, messages and meetings We are working diligently with the provider and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "AWS outage 15-DEC-21"
Last updateWe have had no further reports of the issue and show all services as functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have been notified that the AWS outage has been resolved. We are monitoring the situation and, moving forward, we expect all services to be up and running.
We are experiencing a partial outage on multiple Fuze systems including but not limited to Voice, Chat, Contact Center, Data/Discover, Portal/Hub, and our login services, due to ongoing issues with AWS (https://status.aws.amazon.com/). We are monitoring this situation closely and will provide updates as they become available.
Report: "Fuze Incident - Issue with Logging into Fuze Desktop"
Last updateThis incident has been marked as resolved.
A fix has been implemented and we are now monitoring the results. If you continue to experience issues please raise a case with Fuze Support and reference ID: INC-5203. After 30 minutes we will mark this incident as resolved.
The issue has been identified and a fix is currently being implemented. Thank you for your continued patience as we work to resolve this issue. We will continue to provide updates as soon as we have them.
We are detecting some degraded performance on our Fuze Desktop platform. This may impact end-user services. Possible symptoms may include an inability to fully log into Fuze Desktop We are working diligently to identify the cause of the issue and will provide regular updates as we have them until the issue has been resolved. We apologise for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Ongoing Issues with AWS"
Last updateWe have had no further reports of the issue and show all services as functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5196. Thank you for your patience while we worked to resolve this issue.
The provider has indicated that resolution steps have been implemented and we expect that all Fuze services are operational. Some users may continue to experience issues with delayed presence on Fuze Desktop and Web, however, this should clear up as events continue to process We will monitor this event for the next 30 minutes before setting the status to "Resolved." If you continue to experience issues, please contact support via the Community. To ensure the quickest feedback, please make reference to Incident-5196.
We continue to work with the provider on a solution to the issue and are beginning to see signs of stability across the platform. Thank you for your continued patience while we work to get this issue fully resolved.
At this time, we have determined that multiple Fuze systems are being impacted by this issue, however, our voice platform continues to work without any degradation. We will continue to work with the provider on a solution to the issue in order to restore services to normal. Thank you for your patience while we work to get this issue identified and resolved.
We are continuing to investigate this issue.
We are experiencing a partial outage on multiple Fuze systems including but not limited to Chat, Contact Center, Data/Discover, Portal/Hub, and our login services. We suspect this is due to ongoing issues with AWS (https://status.aws.amazon.com/). We are working closely with the provider and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Issue with Outbound Calling"
Last updateThis incident has been marked as resolved. If you continue to experience any issues related to this please raise a case with Fuze support and reference INC-5179
The 3rd party carrier have resolved the issue, and expect that all services are functioning as expected. We will monitor this event for the next 30 minutes before setting the status to "Resolved." If you continue to experience issues, please contact support via the Community. To ensure the quickest feedback, please make reference to incident 5179 Thank you!
We have made a change and re-routed outbound calls to avoid the affected Carrier in Canada, and confirmed that this is now working as expected. The issue with inbound call is still being investigated and we will continue to monitor the updates from underlying Carrier. We thank you for your patience while this issue is addressed by the carrier.
Upon further investigation, we have identified that the issue is with an upstream carrier that provides service to a small subset of users in Canada. We are working with the carrier to identify and resolve the issue. We will post updates as they become available.
We are currently investigating a 3rd party carrier issue that is causing intermittent issues on outbound calls for a subset of users. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Portal"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5152.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5152.
We are currently investigating reports that a subset of users are unable to access our Admin Portal. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Queue Login"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5143.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5143.
The issue has been identified and a fix is currently being implemented. We will provide further updates as soon as possible.
We are continuing to investigate this issue and will continue to provides updates as soon as they are made available.
We are currently investigating reports that a subset of users are experiencing login problems on our Contact Center platform. This may impact end-user services. Expected symptoms may include an inability for agents to login to their designated queues. We are working diligently to identify the cause issue and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Creating New Services with "700" Numbers"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5134. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5134. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We continue to work on a solution to the issue in order to restore services to normal. Our engineering team has identified the cause of the issue and in the next (30) minutes the Portal and Hub will be rebooted for the change to be deployed to resolve this issue. During this time, you maybe be sent back to the Portal home page. Thank you for your patience while we work to get this issue identified and resolved.
We have identified the cause of the issue that is causing issues with "700" numbers and are actively working to resolve it as quickly as possible. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We are currently investigating reports that a subset of users are experiencing issues with creating new services on our Portal and Hub platforms. We are working diligently to identify the cause of the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Outbound Calling"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5127. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5124. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have identified the cause of the issue and are actively working to resolve it as quickly as possible. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We are currently investigating reports that a subset of users are experiencing outbound calls failing. We suspect this is due to potential issues with an underlying carrier. This may impact end-user services. We are working diligently to identify the cause of the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Buddy Watch & Parking"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5123. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the Buddy Watch and Call Parking issue, and expect that all services are functioning as expected. We will monitor the services overnight. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5123. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have identified the cause of the issue with Buddy Watches and Call Parking and are actively working to resolve it as quickly as possible. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We are detecting some degraded performance on our Calling platform. This may impact end-user services. Possible symptoms include issues with parking calls and using Buddy Watch. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with {Issue/Symptom description}"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5115. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to Incident 5115. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We are investigating reports of issues with outbound calling. This may impact end-user services. Possible symptoms include intermittent fast busy signal when dialing out. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Underlying Carrier"
Last updateWe have had no further reports of the issue and show all services as functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5101. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We are continuing to monitor with the carrier for further reports of issues however at this time all systems are operating as expected with successful call completion. If you are still experiencing issues, please contact Fuze support and reference Incident 5101.
Our carrier is now reporting that all systems are operating as expected and successful call completion. We will continue to monitor for the next few hours before resolving this incident. If you are still experiencing issues, please contact Fuze support and reference incident 5101.
We have received new reports from our underlying carrier that a subset of users may be experiencing continued issues at this time with voice functionality. This issue is the result of a known nationwide outage that is impacting a carrier utilized by multiple telecom vendors. We will continue to monitor and request updates from the carrier and post them as we receive them. We thank you for your patience while this issue is addressed by the carrier.
Our underlying carrier is now reporting that all services have returned to normal again. Our customers are also reporting that no further issues are being observed. We will continue to monitor the situation for the next few hours before resolving this incident. If you are experiencing any further problems, please reach out to Fuze support and reference incident number 5101.
A subset of users may be experiencing continued issues at this time with voice functionality. This issue is the result of a known nationwide outage that is impacting an underlying carrier utilized by multiple telecom vendors. We will continue to monitor and request updates from the carrier and post them as we receive them. We thank you for your patience while this issue is addressed by the carrier.
Report: "Fuze Incident - Issue with Underlying Carrier"
Last updateWe have continued to monitor the situation and our underlying carrier is no longer reporting any further network issues. We will now resolve this incident but will continue to closely monitor the situation. If you experience any further issues, please contact Fuze Support via the Community and reference incident 5101.
Our underlying carrier are now reporting that all services have returned to normal again. Our customers are also reporting that no further issues are being observed. We will continue to monitor the situation for the next few hours before resolving this incident. If you are experiencing any further problems, please reach out to Fuze support and reference incident number 5101.
A subset of users may be experiencing continued issues at this time with voice functionality. This issue is the result of a known nationwide outage that is impacting an underlying carrier utilized by multiple telecom vendors. We will continue to monitor and request updates from the carrier and post them as we receive them. We thank you for your patience while this issue is addressed by the carrier.
The Fuze Carrier Relations team is continuing to push the underlying carrier for updates regarding the ongoing outage impacting voice calling and DTMF tone functionality. We will continue to update the Fuze Status Page (status.fuze.com) periodically until a resolution has been reached.
The Fuze Carrier Relations team is continuing to push the underlying carrier for updates regarding the ongoing outage impacting voice calling and DTMF tone functionality. We will continue to update the Fuze Status Page (status.fuze.com) periodically until a resolution has been reached.
A subset of users may be experiencing issues with inbound phone calls due to an issue with an underlying carrier. They continue to investigate the issue and we will post any further updates as we have them.
A subset of users may be experiencing issues with inbound phone calls due to an issue with an underlying carrier. They continue to investigate the issue and we will post any further updates as we have them.
We continue to actively investigate the issue with our underlying carrier. Possible symptoms include inbound/outbound calls failing to select numbers as well as DTMF tones not being picked up in menus. Thank you for your patience while we work to get this issue identified and resolved.
We have received a report from an underlying carrier that they are experiencing intermittent issues which may impact our platform. Possible symptoms include inbound/outbound calls failing to select numbers as well as DTMF tones not being picked up in menus. We are working diligently with the carrier to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with DTMF"
Last updateOur underlying carrier has confirmed that their network has returned to normal operation and working as expected. We have also had no further reports of any further issues from our customers. We will resolve this incident, but continue to monitor with our carrier. If you experience any further issues, please contact Fuze Support via Fuze Community for assistance and reference incident 5101 We apologize for any inconvenience caused and thank you for your patience while we worked with our Carrier to resolve this issue.
Our underlying carrier is now reporting that their network behavior has returned to normal and our customers have reported everything is behaving as expected. We will continue to monitor the situation for any changes. If you are still experiencing issues, please contact Fuze Support.
The Fuze Carrier Relations team is continuing to push the underlying carrier for updates regarding the ongoing outage impacting voice calling and DTMF tone functionality. We will continue to update the Fuze Status Page (status.fuze.com) periodically until a resolution has been reached.
The underlying carrier is continuing to investigate the issue in order to determine the cause. There are no new updates at this time. Thank you for your patience while we work to get this issue identified and resolved.
At this time the underlying carrier is continuing to investigate the issue in order to determine the cause. Thank you for your patience while we work to get this issue identified and resolved.
Due to an issue with an underlying carrier, we are experiencing issues on our calling platform. Possible symptoms include tones not being picked up when calling into menus and one-way audio where the caller is unable to hear the menu. We are working diligently with the carrier to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
We are receiving reports of issues with DTMF on our Calling platform. Possible symptoms include tones not being picked up when calling into menus and one-way audio where the caller is unable to hear the menu. We are working diligently to identify the cause of the issue and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Fuze Reporting"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5092. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5092. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We are detecting some degraded performance on our Fuze Reporting platform. This may impact end-user services. Possible symptoms include reports loading slowly or failing to load. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Outbound calling"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5090. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We are no longer receiving reports of the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5090. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We are receiving reports of issues with outbound calling in our Desktop application affecting a subset of users. We are working diligently to identify the issue and will provide regular updates as we have them and until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Fuze Desktop/Web"
Last updateWe have resolved the login issue and will be reaching out to the the small number of users affected. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident 5080.
We have identified a potential cause of the issue and are actively working to resolve it as quickly as possible. If users are continuing to report issues at this time, please consider using the Web client as we believe that it is now fully operational. There continues to be a risk for a small subset of users on Fuze Desktop to receive this error message and an investigation into those issues is ongoing. Thank you for your patience while we work to get this issue resolved.
We are currently investigating reports that a subset of users are receiving an error message indicating that they are "unable to connect to the server" when accessing Fuze Desktop and Fuze Web. We are working diligently to identify the cause of the issue and will provide regular updates as we have them until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.
Report: "Fuze Incident - Issue with Audio (South Africa)"
Last updateWe have had no further reports of the issue and show all services functioning as expected. This incident is now closed. If you experience any further issues related to this topic, please contact Fuze Support via the Community for assistance. To ensure the quickest feedback, please make reference to incident INC-5079. Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have implemented a fix for the issue, and expect that all services are functioning as expected. We will monitor this incident for the next 30 minutes before setting the status to "Resolved”. If you continue to experience issues, please contact support via the Community for assistance. To ensure the quickest feedback, please make reference to incident INC-5079. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.
We have identified the cause of the issue and are actively working to resolve it as quickly as possible. We will continue to provide updates as we have them regarding our progress. Thank you for your patience while we work to get this issue resolved.
We are continuing to investigate this issue and will provide an update as soon as possible. Thank you for your continued patience.
We are detecting some degraded performance on our calling platform. We suspect this is due to potential issues with an underlying carrier. This may impact end-user services. Possible symptoms may include calls connected without audio in South Africa. We are working diligently to identify the cause of this issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience this may cause and appreciate your patience.