Some systems are experiencing issues.

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

Wildix Integrations Hub has been taken offline as a precaution following the disclosure of critical PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 (known as PHP2Shell). We know this interrupts any workflows that depend on the integrations, and we’re sorry for the disruption. We concluded that keeping the service offline until the fixes are applied is necessary to protect your data and our infrastructure.

While the service is offline, integrations configured through Wildix Integrations Hub will not sync or run. Other PBX features are not affected.

We expect the service to be available again later today and will post an update here as soon as it is restored.

For details on the vulnerabilities, see PHP’s security advisory: https://www.php.net/archive/2026.php#2026-10-21-5

Update – PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619

Most cloud PBXs have now been updated with the patched PHP versions. A small number remain, and our team is handling them individually. No action is required from partners for cloud PBXs.

All Wildix cloud services remain fully operational.

On-premise PBXs without auto-upgrade enabled should be updated as soon as possible, if this hasn’t been done already.

Update – PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619

All Wildix cloud services have been updated with the patched PHP versions and are fully operational, including Legacy Kite, Legacy File Sharing, Zoho Integration Service and Wildix Integrations Hub. The rollout to cloud PBXs is in progress. No action is required from partners.

On-premise PBXs without auto-upgrade enabled should be updated as soon as possible, if this hasn’t been done already.

We will post a final update once the cloud PBX rollout is complete.

Update – PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619

On 21 October 2026, the PHP project disclosed two critical vulnerabilities in the PHP runtime, CVE-2026-109618 and CVE-2026-109619 (CVSS 4.0: 9.2). Both could allow remote code execution without authentication. PHP has released fixed versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP’s advisory: https://www.php.net/archive/2026.php#2026-10-21-5

Wildix PBX

Supported PBX versions run on PHP 8.2 (WMS 6 and WMS 7 up to 7.08) and 8.4 (WMS 7.09 and later). Patched packages for on-premise PBXs are available in all Wildix repositories.

• Cloud PBXs: The update is being rolled out by Wildix. No action is required from partners. We will post an update here once the rollout is complete.

• On-premise PBXs with auto-upgrade enabled will receive the update automatically.

• On-premise PBXs without auto-upgrade must be updated manually as soon as possible.

• PBXs on versions older than WMS 6 must be upgraded to WMS 6 or WMS 7 as soon as possible.

Wildix services Our teams are applying the patched version across our infrastructure.

As a precaution, the following services have been taken offline until patching is complete:

•Legacy Kite •Legacy File Sharing •Zoho Integration Service •Wildix Integrations Hub

Other PBX features are not affected by this maintenance.

We will post further updates here as services are restored.

We are carrying out urgent security work following the disclosure of vulnerabilities affecting certain PHP-based services. As a precaution, access to some Wildix services may be temporarily unavailable while we apply protective measures and investigate potential exposure. We will post further updates here as work progresses and we can confirm the impact and recovery timelines.

For more information about this vulnerability, please refer to the CERT-EU security advisory: https://cert.europa.eu/publications/security-advisories/2026-018

Service has been restored. In case you are still experiencing any issues, please contact our technical support

We are currently experiencing performance issues with chats and presence.

Service has been restored. In case you are still experiencing any issues, please contact our technical support

We’re currently experiencing degraded performance issues with SSL Certification Service. Our team is working to restore normal performance levels.

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

We are currently experiencing performance issues with Cloud Analytics.

Following the previously reported outage, we identified that the issue impacted data processing for a subset of customers. During 13:58 to 15:13 UTC, some customers experienced loss of CDRs, transcriptions and Sales Intelligence data. Data generated during this time window cannot be recovered. The service has been fully restored and is operating normally. We have confirmed that the issue is no longer affecting incoming data. We are conducting an internal review and implementing additional safeguards to prevent similar incidents in the future. We sincerely apologize for the impact - we understand how critical this data is and are treating this incident with the highest priority.

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

We are currently experiencing issues with the authorization service.

Maintenance work has been successfully completed. In case you are still experiencing any issues, please contact our technical support.

We will be performing scheduled maintenance on Portal on 05.04.2026 06:00-07:00 UTC timezone During this time some services might be temporarily unavailable.

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

We are currently experiencing an issue with the licensing function.

CLASSOUND service has been restored.

One of CLASSOUND local lines is currently experiencing an outage with terminating calls traffic to +33 dial codes numbers in France. Our technical team is actively working to resolve this issue as quickly as possible.

The Portal performance issue has been fixed, and all affected operations are working normally.

We are currently experiencing Portal performance issues. As a result, PBX upgrades may fail, license updates may not be applied, and provisioning of new PBXs may not complete successfully. Our team is investigating the issue.

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

Our technical team is actively working to resolve this issue as quickly as possible.

Maintenance work has been successfully completed. In case you are still experiencing any issues, please contact our technical support.

We will be performing scheduled maintenance on Portal on 11:00-12:00 2026-03-14 UTC During this time some services might be temporarily unavailable.

Services has been restored. In case you are still experiencing any issues, please contact our technical support.

Chats and conferences are significantly affected. Users may be unable to send or receive messages, and conferences may fail to start or remain stable.

Services has been restored. In case you are still experiencing any issues, please contact our technical support.

Chats and conferences in x-bees are significantly affected. Users may be unable to send or receive messages, and conferences may fail to start or remain stable.

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

We are currently experiencing a partial outage in the US East. Some users may experience connectivity issues. We are investigating the issue and will provide updates as more information becomes available.

Message: Service has been restored. In case you are still experiencing any issues, please contact our technical support.

PBXs using Voicebot may experience performance degradation.

We are experiencing performance issues with Voicebot.

We are currently experiencing a complete outage in the UAE and Bahrain region. Our team is actively working to resolve the issue and restore systems online.

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

We indentifited the root cause and working on restore this service .

We’re experiencing a service outage with WMP. Our team is currently working to restore the service.

Message: Service has been restored. In case you are still experiencing any issues, please contact our technical support.

We are currently experiencing a partial outage in the Middle East. Some users may experience connectivity issues. We are investigating the issue and will provide updates as more information becomes available.

A fix has been implemented, and we are seeing a significant improvement in service performance. Services are now back online. We are continuing to monitor performance to verify full resolution.

Chats and conferences in x-bees are significantly affected. Users may be unable to send or receive messages, and conferences may fail to start or remain stable.

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

We’re investigating an issue impacting chats. Users may see message delays, instability, or search issues. A mitigation is in progress, and we’ll share updates as we have them.

We are currently experiencing performance issues with chats

We are currently experiencing performance issues with chats

A fix has been implemented, and we are seeing a significant improvement in service performance. Services are now back online. We are continuing to monitor performance to verify full resolution.

The incident previously reported as degraded performance has now been escalated to a Major Outage due to increased impact.

Users may experience message delivery delays, intermittent chat instability, and issues joining or maintaining conferences. We are working on resolving the issues.

We’re currently experiencing degraded performance issues with chats. Our team is working to restore normal performance levels.

Maintenance work has been successfully completed. In case you are still experiencing any issues, please contact our technical support.

We will be performing scheduled maintenance on portal on 2026-02-24 03:00-05:00 UTC time zone. During this time some services might be temporarily unavailable.

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

We are currently investigating an issue with partial data loss in our Group Chats service, which is affecting a subset of our partners. Our engineering team is actively working to identify the root cause and restore the service to full functionality. We will provide further updates as more information becomes available.

The incident impacting Voice services in Spain has been identified and resolved.

The root cause was related to a network-level outage affecting upstream connectivity within the Spain region. This issue caused call routing failures and service degradation for multiple customers.

The Classound resolution team worked in coordination with the upstream carrier to:

Identify the affected network segment

Re-route traffic where possible to minimize impact

Restore stable connectivity

Monitor service recovery across all impacted routes

Voice services have now been fully restored, and monitoring confirms that traffic levels and call success rates have returned to normal.

We will continue enhanced monitoring to ensure service stability We apologize for the impact and appreciate your patience during this major incident.

CLASSOUND service has been restored.

The issue was caused by temporary connectivity disruptions on the national operator Movistar network in Spain. The situation was addressed in coordination with the local line representative, and the service is now operating normally.

There is an ongoing known issue with Movistar in Spain that may affect inbound calls to +34 numbers.

We are actively coordinating with the local line representative to resolve the situation.

One of CLASSOUND's local lines is currently experiencing an outage affecting inbound call termination to numbers with +34 dial codes in Spain.

Our technical team is actively working to resolve this issue as quickly as possible.

Service has been restored. The issue was caused by a bottleneck in the load balancer, which prevented some users from creating new chats or loading existing chat history. In case you are still experiencing any issues, please contact our technical support.

We are currently experiencing an issue with the Group Chats service. New group chats cannot be created at this time. Our team is actively working to restore full functionality and will provide updates as soon as possible.

We have successfully updated the certificates. If you experience any issues, please contact our support team for assistance.

We are currently working on updating SSL certificates for a small number of customers whose certificates were automatically renewed between February 11–13. This update will restore full service access for affected users.

Our team is actively performing these updates and monitoring progress. If you experience any issues, please contact our support team for assistance.

Earlier today, Group Chats experienced a temporary disruption related to SSL certificate validation. The service has been restored and is now fully operational.

A small number of customers - less than 3% - whose certificates were automatically renewed between February 11-13 may still experience issues accessing group chats. Our team is actively working to update these certificates and restore full access.

If you are affected, please contact our support team for assistance.

Group chat services are now restored and fully operational. If you experience difficulty connecting to group chats or have lost access to rooms, please reach out to our support team for assistance in restoring access.

We’re currently experiencing outage on Group Chats service. Our team is working to restore the service.

CLASSOUND service has been restored.

The initial root cause has been identified and isolated. Corrective actions are currently being implemented to prevent recurrence, including additional safeguards and adaptations following the recent performance refactoring changes. Our team continues to closely monitor the service to ensure stability.

CLASSOUND service is currently experiencing an outage affecting the termination of a small portion of call traffic to various destinations. At this time, the issue has been identified as a service regression following recent performance refactoring implementations.

Our technical team is actively working to resolve this issue as quickly as possible.

Portal performance has been restored and service is operating normally

Some users may experience slow load times or failed requests. We’re actively investigating and working to mitigate the issue.

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

Message: We’re experiencing a service outage with Portal. Our team is currently working to restore the service.

Maintenance work has been successfully completed. In case you are still experiencing any issues, please contact our technical support.

We will be performing scheduled maintenance on Wizyconf on Saturday, 2026-01-24, 8:00 - 9:00 AM UTC time. During this time some services might be temporarily unavailable.

We have concluded our investigation into the recent incident affecting presences, the live view in x-bees, and the Cloud Analytics service. All services have been fully restored and are operating normally.

Our investigation confirmed that a temporary performance issue on January 8th caused a delay in data processing. As a result, some data, such as presence statuses, call records, and analytics, was not immediately visible to our users.

We are pleased to report that our team has successfully processed all queued data from the affected period. All your information is now fully available and accurately reflected in all related services, including Cloud Analytics.

We have taken steps to reinforce our systems to prevent similar issues in the future. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding.

We are continuing to investigate the incident affecting presences, live view in x-bees and Cloud Analytics service, that occurred yesterday. While primary functionality has been restored, we are conducting an in-depth review to ensure the service is completely stable and all effects of the incident have been fully addressed. Our team is working diligently to complete all necessary actions as quickly as possible.

Maintenance work has been successfully completed. It took a little longer than expected, we apologize for the inconvenience. In case you are still experiencing any issues, please contact our technical support.

We will be performing scheduled maintenance on Wizyconf on Saturday, 2025-11-29, 7:00 - 8:00 AM UTC time. During this time some services might be temporarily unavailable.

The issue has been resolved, and all services are now fully operational. We apologize for any inconvenience caused and thank you for your patience.

We are observing an increased error rate during PBX upgrade process. Our team is working to identify the root cause and restore full functionality.

The issue has been resolved, and all services are now fully operational. We apologize for any inconvenience caused and thank you for your patience.

We are currently facing difficulties retrieving data from WMP via the web interface. The my.wildix.com is unable to load. Our dedicated development team is actively investigating the issue and working to restore full functionality as quickly as possible. We appreciate your patience and understanding.

Maintenance work has been successfully completed. In case you are still experiencing any issues, please contact our technical support.

We will be performing scheduled maintenance on the Portal (WMP) and Salesforce from Saturday, 22 November 2025, 08:00 UTC to Monday, 24 November 2025, 08:00 UTC. During this time, some services may be temporarily unavailable.

Message: Service has been restored. In case you are still experiencing any issues, please contact our technical support.

We will be performing scheduled maintenance on Wizyconf on Saturday, 2025-11-22, 7:00 - 8:00 AM UTC time. During this time some services might be temporarily unavailable.

We will be performing scheduled maintenance on Cloud Analytics from Wednesday, 12 November 2025, 22:00 UTC to Thursday, 13 November 2025, 02:00 UTC. During this time some services might be temporarily unavailable.

Maintenance work has been successfully completed. In case you are still experiencing any issues, please contact our technical support.

We will perform scheduled maintenance on Auth services, 2025-11-08 7:00 UTC. During this time, service could be temporarily unavailable.

We will perform scheduled maintenance on Auth services, 2025-11-07. During this time, service could be temporarily unavailable.

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

One of CLASSOUND local lines is currently experiencing an outage with terminating inbound calls traffic to +49 dial codes numbers in Germany.

Our technical team is actively working to resolve this issue as quickly as possible.

Maintenance work has been successfully completed. In case you are still experiencing any issues, please contact our technical support.

We will be performing scheduled maintenance on Wizyconf on Wednesday, 2025-11-05, 6:00 - 6:30 AM UTC time. During this time some services might be temporarily unavailable.

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

APNF engineering has initiated an update to restore service. Full recovery is expected within the next several hours.

The issue occurred following an update by ARCEP that affected the routing of the Wildix prefix. Our technical team is in close contact with ARCEP and APNF to update the prefix database and restore full service as soon as possible.

The issue was caused by the removal of the Wildix prefix from the French routing database following an ARCEP update. APNF engineering re-applied and propagated the prefix configuration, restoring full service.

Preventive measures are now being implemented in collaboration with APNF and ARCEP to ensure future stability and avoid similar disruptions.