Some Cisco Webex users still have some problems with the collaboration system more than a week after the service was shut down. According to the company's website, a major disruption began on September 25 and closed all Webex services, including calls, meetings, control center, hybrid services and equipment.
At that time, the company stated that "Webex Teams services are currently affected by an ongoing service interruption. Engineering resources are online and working to restore services. We apologize for the impact and all hands are on the deck to restore the services of Teams, Meetings, Calls, Attention and Context ".
During the following week, most of the services returned to normal, although slowly and with some problems. The Webex team wrote on October 2:
"The Webex Teams service continues to experience high service latency, engineers continue to complete tasks in our service remediation list, and these efforts take more time than we would like." Latency is due to overload of a service As part of last week's incident recovery process, the team is working on some implementations of additional services, along with the addition of some additional network controls that will allow connections to remain connected for a longer period of time. that should address part of the connection. "Some Webex devices are now online and can make calls, however, incoming calls and other pairing functions will not be available. Webex's Equipment and Calendar services continue to experience latency and errors when connecting to the service. "
A Webex publication on October 4 shows that some problems, such as poor performance, are in progress:
"Engineering continues to work on engineering tasks to address the remaining outstanding elements. Some users of Webex Teams continue to experience inconsistent results with some user spaces. While many of the data in the space have been restored and are fully operational, there are still some user spaces that do not appear or appear but the messages and calls do not work.
These user experiences are caused by a condition where the list or space data is incorrect. Engineering continues to work on code solutions. The engineering team is looking to provide a solution for some of the 1: 1 spaces affected first, followed by a broader code solution. The solution is in the testing phase and a broader code solution is being developed. It is taking us longer than we would like, but we are working diligently to address the problems. "
Other Webex publications detail other problems that the company has had in the complete restoration of services. On October 3, Webex reported:
"The metrics and monitors confirm that the network connectivity in the equipment infrastructure works in the expected way." The latency problem experienced with the client of the Webex Teams has also been addressed for our consumer customers.
Engineering continues to work on the remaining elements to restore Cisco Webex Teams services. The ongoing data restoration tasks were completed on time, and all data restoration activities have been completed. The remaining problems affect the access of users to the spaces and capabilities of One Button to Push in some Space meetings. Some users continue to experience problems accessing and sending messages to specific spaces. The engineering teams continue to work on a code solution to address those deteriorated spaces, and an ETA will be provided as soon as one is available. "
So far, many details have not been given about what actually caused the interruption, but an analysis of the root cause is underway and there could be a report of the results, observers say.
