January 9, at 10:35 CET CLASSOUND Service faced critical call routing issues because of a wrong configuration inserted by human error that caused routing errors in the production clusters.
Recovery of 100 % of incoming routes and 95 % of outgoing routes was achieved by 13:20 CET. 5% of the remaining outgoing routes were restored by 16:30 CET.
The configuration issue was not detected on the stage clusters due to a failure of auto-tests. All necessary improvements are being applied to auto-tests and release procedures to prevent a similar situation from happening in the future.
Fixed
3 years ago
2023-01-09 17:24 UTC
Service has been restored.
Recovery of 100 % of incoming routes and 95 % of outgoing routes was achieved by 11:20 GMT, 5 % of remaining outgoing routes was restored by 14:30 GMT.
In case you are still experiencing any issues, please contact our technical support.
Watching
3 years ago
2023-01-09 11:39 UTC
We have observed service recovery and finalizing repairs. This incident will be resolved when we confirm all repairs are complete
Investigating
3 years ago
2023-01-09 10:39 UTC
We involved additional teams in resolving this issue and we also took measures to mitigate the impact of this incident as much as possible.
Reported
3 years ago
2023-01-09 09:55 UTC
We are observing an increased number of failed calls and currently working on this issue.
Service has been restored. In case you are still experiencing any issues, please contact our technical support.
Investigating
3 years ago
2022-12-29 21:34 UTC
WMP temporarily is not accessible due to investigation work on it. This indirectly affects multiple services, mostly it affected that requesting new licenses is impossible. We are doing our best to fix this issue ASAP.
Investigating
3 years ago
2022-12-29 18:11 UTC
We involved additional teams in resolving this issue and we also took measures to mitigate the impact of this incident as much as possible.
Reported
3 years ago
2022-12-29 14:14 UTC
We observe increased amount of errors coming from WMP regarding license adjustments. We are investigating.
Wildix will be performing general maintenance of DNS services. During this maintenance window (17/12), we expect to see zero periods of service degradation. We are performing this operation to improve our overall services’ reliability and quality. If you have any questions, please, do not hesitate to reach out to us via our Tech Support teams.
Note that after the migration, it will be impossible to reach PBX using its serial number in FQDN, e.g. 221123456789.wildixin.com.
Case has been resolved. Kindly contact technical support in case you face any performance issues with Zoho service.
Investigating
3 years ago
2022-12-17 23:09 UTC
Due to emergency maintenance following the potential vulnerability in the Zoho integration, PBXs involved might become unavailable for a few seconds during the next hour.
Reported
3 years ago
2022-12-16 17:19 UTC
We detected a potential vulnerability in the Zoho integration which will be disabled for the moment.
Internet connectivity issue for the us-east-2 region has resolved at 09:06 PM UTC. In case you are still experiencing any issues, please contact our technical support.
Reported
3 years ago
2022-12-05 20:39 UTC
AWS is having some issues in the US East regions, which are affecting our Cloud PBXs in these areas. We are working with AWS to reduce the impact to a minimum.