Is Melo Technology down?

We have received reports and can confirm that **Melo SIP is currently experiencing an issue affecting outbound dialing following a recent system update**. Our technical team is actively investigating the issue and working to restore normal service as quickly as possible. We will provide further updates as additional information becomes available.

MeloSIP Click2Call Workaround Available We have identified a temporary workaround for users who need to make calls using MeloSIP Click2Call while our team works on an update. In the MeloSIP Chrome extension: - Enable “Dynamic Caller ID.” - Enter your business phone number in the “Default Caller ID” field. This should restore Click2Call functionality until the MeloSIP application update is released. Alternatively, users can continue making calls by manually dialling numbers using the traditional dial method. For clarification: This issue is limited specifically to MeloSIP Click2Call functionality. Regular manual dialling is not affected. Our team is actively working on the MeloSIP update and will provide another notice once the fix is available.

We have released an updated version of MeloSIP Click2Call — version 11.2.6 — which includes the fix for the current Click2Call issue. The update has been submitted to the **Google Chrome Web Store** and is currently awaiting Google's approval. Unfortunately, the timing of that approval is outside of our control. Once Google approves and publishes version 11.2.6, users should only need to update the MeloSIP Click2Call Chrome extension to restore normal service. We are actively monitoring the Chrome Web Store for approval and will update this ticket as soon as the new version becomes publicly available.

The latest version of MeloSIP Click2Call, version 11.2.6, is now available in the Google Chrome Web Store and is ready to be updated by our users. If you temporarily enabled Dynamic Caller ID as part of the earlier workaround, please disable it after updating. Once version 11.2.6 has been installed, MeloSIP Click2Call service should be fully restored to normal operation. If you experience any difficulty updating the extension or require assistance, please contact Melo Technology Technical Support: Phone: 1-888-635-6835, Option 3 From your Melo phone: Dial 611 Email: [[email protected]](mailto:[email protected]) Our team will be glad to assist you. Thank you for your patience while we worked to resolve this issue. This incident is now resolved and the ticket is being closed.

Currently investigating an issue affecting outbound calls for some users. We’re actively working to identify the cause and restore normal calling as quickly as possible.

We are actively restarting one of our primary node servers. Services will be offline momentarily.

We are continuing our investigation and have activated our engineers to investigate the dialing issue with urgency.

Services are restored. We are continuing our investigation and monitoring closely.

This incident has been resolved.

RFO: Root Cause & Service Restoration Update Voice Service Interruption — August 12, 2026 Melo Technology takes the reliability and security of our communications infrastructure exceptionally seriously. We are providing this update to give our clients a clear and transparent account of the service disruption experienced this morning, while appropriately protecting operational and security-sensitive details. Executive Summary At approximately 8:03 a.m. Toronto TIme, Melo Technology's infrastructure monitoring systems began generating a series of abnormal alerts affecting our primary voice infrastructure. Our engineering team immediately began investigating. Shortly afterward, we identified intermittent failures affecting the completion of some outbound calls. We also began receiving reports from clients who were unable to complete certain calls. Our initial investigation showed that some calls were being rejected by upstream telecommunications carriers. We immediately engaged our carrier partners and software engineering team to determine the source of the failures. Through that joint investigation, we determined that the underlying issue originated within traffic reaching our infrastructure. Melo Technology was the target of a distributed denial-of-service \(DDoS\) attack. The attack generated an abnormally high volume of traffic against portions of our telecommunications infrastructure. As a result of that traffic, one of our upstream carriers automatically implemented protective rate-limiting measures. Those protections caused some legitimate calls to be temporarily rejected or prevented from completing. Our engineers, carrier partners and software team worked together to identify the traffic pattern, isolate the source of the disruption and implement mitigation measures. Service has now been restored. Service was fully restored at 9:10 a.m. EDT. Client Impact The impact of this incident was limited to service availability. During the affected period, some clients experienced intermittent difficulty completing outbound telephone calls. Calls that were successfully established continued to operate normally. There was no compromise of Melo Technology's systems or client environments as part of this incident. Our investigation found: No evidence of unauthorized access to client data No evidence that customer information was accessed, altered or disclosed No evidence of call interception or access to call content No compromise of credentials or client accounts No intrusion into our systems or network No ransomware, malware or other system compromise This was a denial-of-service event, not a data breach or system intrusion. The objective and effect of the attack were to disrupt the availability of services by overwhelming infrastructure with traffic. Apart from the temporary inability to complete some calls, the confidentiality and integrity of our systems, client information and communications remained protected. Root Cause The root cause was a deliberate volume-based attack directed toward telecommunications infrastructure operated by Melo Technology. The resulting abnormal traffic volume triggered protective measures within portions of the carrier network, including rate limiting. While those safeguards operated as designed to protect telecommunications infrastructure from excessive traffic, they also temporarily affected legitimate outbound call traffic. Once our teams correlated the carrier behaviour with the abnormal traffic reaching our infrastructure, we were able to identify the attack and implement appropriate controls to mitigate it. For security reasons, we will not publish specific details regarding the attack vector, affected interfaces, network architecture, firewall controls or mitigation techniques used. Providing that level of detail could unnecessarily expose information that may assist future attackers. Response and Remediation Melo Technology's infrastructure monitoring detected the abnormal conditions immediately, allowing our team to begin investigating at 8:03 a.m. Throughout the incident, our engineering team worked directly with our telecommunications carriers and software partners to trace the call failures and distinguish legitimate carrier issues from the underlying traffic event. Once the source was identified, mitigation measures were implemented to isolate the malicious traffic and restore normal telecommunications service. We have also implemented additional protective controls as part of the response and are continuing to review the incident for opportunities to further strengthen our infrastructure. Security Review We recognize that any incident involving the words DDoS attack can understandably raise questions about the security of customer information. We want to be clear: Melo Technology was not hacked. A DDoS attack is fundamentally different from an intrusion or data breach. In this case, an external party attempted to disrupt service by generating excessive traffic. Our investigation has found no indication that the attacker obtained access to our systems, customer information, communications or internal resources. The incident affected the availability of a portion of our voice service for a brief period. It did not compromise the confidentiality or integrity of the information entrusted to us. Moving Forward Although service has been fully restored, our work does not end with restoration. Melo Technology is conducting a complete post-incident review alongside our technology and carrier partners. We are reviewing traffic controls, carrier protections, monitoring thresholds and additional defensive measures designed to further reduce the impact of similar attacks in the future. Security incidents and service interruptions are treated with the highest level of seriousness within our organization. We design our infrastructure with multiple layers of monitoring and protection specifically because telecommunications systems are critical to the businesses that depend on them. This morning's incident demonstrated the importance of those systems: our monitoring detected abnormal behaviour immediately, our engineers responded at once, and our carrier and software partners worked with us to identify and remediate the issue. We sincerely appreciate the patience of clients who experienced difficulty completing calls during the incident. All services are currently operational, and we continue to actively monitor our infrastructure. Thank you for your trust in Melo Technology. Melo Technology

We have identified an issue affecting some incoming calls to local and toll-free numbers. The problem appears to be related to a recent carrier upgrade. We are actively working with the carrier to restore normal incoming call routing as quickly as possible and are treating this as a priority. This issue is effecting only incoming calls and expected to resolved momentarily.

The routing issue has been corrected by our underlying carrier. Calls are flowing properly now. We will monitor for some time and then close the ticket after we see calls flowing as normal.

We have confirmed all calls are flowing properly now and the carrier has closed their ticket. The service issue has been resolved. Thank you for your patience.

We are currently investigating reports that some customers may be experiencing delays when placing outgoing calls. This issue is commonly known as post-dial delay, where additional seconds may pass after dialling before the call connects. During this time, callers may hear silence or “dead air” before the call proceeds. Our team is actively investigating the issue with our carrier partners and will provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience while we work to resolve this as quickly as possible.

We have identified that some outbound calls are experiencing post-dial delay, where there may be a period of silence before the call begins ringing or connects. Based on our current investigation, the issue appears to be affecting outbound carrier routing and does not appear to be caused by our platform before the call is handed off to the carrier. We are continuing to work with our carrier partners to investigate and will provide further updates as more information becomes available.

We have engaged our primary carrier and are currently routing outbound calls through our secondary provider to reduce the impact to our customers. Service has improved significantly, but some customers may still experience intermittent post-dial delay on outbound calls due to shared routes. This is not a service outage, and the vast majority of calls are completing successfully. In affected cases, calls may take longer than usual to begin ringing or connect. We are continuing to monitor call performance and work with our carrier partners toward full resolution. Thank-you for your patience.

We have received confirmation that routing adjustments have been made to correct the outbound calling issue. As of 12:37 PM EDT, call performance appears stable. Outbound calls are completing normally, and recent monitoring shows post-dial delay has returned to expected levels. We are moving this incident to resolved/monitoring and will continue to observe call performance to ensure stability. Please call support if you are experiencing any issues.