Melo Technology Outage History

Melo Technology is up right now

Melo Technology had 13 outages in the last 2 years totaling 28h 4m of downtime — averaging 0.5 incidents per month.

There were 13 Melo Technology outages since October 20, 2025 totaling 28h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.melotel.com

Notice August 24, 2026

Melo SIP Outbound Dialing Issue

Detected by Pingoru
Aug 24, 2026, 01:45 PM UTC
Resolved
Aug 24, 2026, 02:48 PM UTC
Duration
1h 3m
Affected: Click2Call
Timeline · 4 updates
  1. investigating Aug 24, 2026, 01:45 PM UTC

    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.

  2. identified Aug 24, 2026, 01:51 PM UTC

    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.

  3. monitoring Aug 24, 2026, 02:03 PM UTC

    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.

  4. resolved Aug 24, 2026, 02:48 PM UTC

    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.

Read the full incident report →

Notice July 20, 2026

Incoming Calls Failing

Detected by Pingoru
Jul 20, 2026, 01:34 PM UTC
Resolved
Jul 20, 2026, 02:05 PM UTC
Duration
30m
Affected: Canadian DIDsUSA DIDsToll Free DIDs
Timeline · 3 updates
  1. identified Jul 20, 2026, 01:34 PM UTC

    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.

  2. monitoring Jul 20, 2026, 01:56 PM UTC

    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.

  3. resolved Jul 20, 2026, 02:05 PM UTC

    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.

Read the full incident report →

Notice June 25, 2026

Outgoing Call Delays / Post-Dial Delay

Detected by Pingoru
Jun 25, 2026, 03:26 PM UTC
Resolved
Jun 25, 2026, 04:48 PM UTC
Duration
1h 22m
Affected: Outgoing Calls
Timeline · 4 updates
  1. investigating Jun 25, 2026, 03:26 PM UTC

    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.

  2. identified Jun 25, 2026, 03:48 PM UTC

    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.

  3. monitoring Jun 25, 2026, 03:52 PM UTC

    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.

  4. resolved Jun 25, 2026, 04:48 PM UTC

    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.

Read the full incident report →

Notice June 13, 2026

Calling Failure

Detected by Pingoru
Jun 13, 2026, 01:09 PM UTC
Resolved
Jun 13, 2026, 01:26 PM UTC
Duration
16m
Affected: Canadian DIDsUSA DIDsToll Free DIDsOutgoing CallsInternational Calling
Timeline · 2 updates
  1. investigating Jun 13, 2026, 01:09 PM UTC

    We have become aware of an issue impacting calls across our platform. Our team is actively investigating. The service impact appears to affect both inbound and outbound calling.

  2. resolved Jun 13, 2026, 01:26 PM UTC

    Service has been restored. We apologize for the disruption and appreciate your patience while our team worked to resolve the issue. We are continuing to investigate the root cause and will provide further updates if needed.

Read the full incident report →

Notice April 15, 2026

Service Restored: Phone Call Issue Resolved

Detected by Pingoru
Apr 15, 2026, 12:08 PM UTC
Resolved
Apr 15, 2026, 12:08 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 15, 2026, 12:08 PM UTC

    We are aware of an earlier issue impacting phone call functionality. The issue has now been resolved, and we will continue to monitor to ensure ongoing stability.

Read the full incident report →

Notice February 23, 2026

CloudSoftphone Registration Troubles

Detected by Pingoru
Feb 23, 2026, 04:17 PM UTC
Resolved
Feb 24, 2026, 01:16 PM UTC
Duration
20h 58m
Affected: Cloud Softphone SIP App
Timeline · 3 updates
  1. identified Feb 23, 2026, 04:17 PM UTC

    We are investigating trouble with our CloudSoftphone app since it's recent update causing devices not to register. We hope to provide updates shorty.

  2. identified Feb 23, 2026, 04:55 PM UTC

    We have identified an issue with a recent update to the Cloud Softphone application. New registrations are currently failing on the latest versions of the Cloud Softphone desktop and mobile apps. At this time, we are holding off on issuing new registration QR codes until the issue is resolved. Please do not reset your device, as doing so will remove your current configuration and may result in a loss of service until a fix is in place. We are actively working on a solution and hope to provide an update soon. We sincerely apologize for the inconvenience and are treating this matter as a high priority.

  3. resolved Feb 24, 2026, 01:16 PM UTC

    Yesterday, we experienced an issue affecting new registrations on the Cloud Softphone application. After investigating, we identified the root cause as a recent update to Cloud Softphone that introduced a problem related to the secure registration certificate. As a result, new registrations were failing on both the desktop and mobile versions of the application. Once a corrective update was rolled out to the latest versions of Cloud Softphone (desktop and mobile), registration functionality was restored and the app began registering normally again. We sincerely apologize for the inconvenience this caused and appreciate your patience while we worked to resolve the issue.

Read the full incident report →

Notice February 17, 2026

Service Notice – 611 Technical Support

Detected by Pingoru
Feb 17, 2026, 02:43 PM UTC
Resolved
Feb 17, 2026, 03:34 PM UTC
Duration
50m
Timeline · 2 updates
  1. identified Feb 17, 2026, 02:43 PM UTC

    We are currently aware of a routing issue affecting calls to our 611 Technical Support line. As a result, some calls may not be connecting properly. Our team is actively investigating and working to resolve this matter as quickly as possible. In the meantime, if you require technical assistance, please contact us directly at 416-479-0993 (press option 3) or email [email protected] and our team will be happy to assist you. We appreciate your patience and will provide an update as soon as this issue has been fully resolved. — Melo Technology Support Team

  2. resolved Feb 17, 2026, 03:34 PM UTC

    The routing issue affecting our 611 Technical Support line has now been fully resolved. Calls to 611 are operating normally. Thank you for your patience and understanding while we worked to correct this matter. If you continue to experience any difficulties, please do not hesitate to contact our support team.

Read the full incident report →

Notice January 5, 2026

Some Outgoing Routes Failing

Detected by Pingoru
Jan 05, 2026, 11:37 PM UTC
Resolved
Jan 05, 2026, 11:58 PM UTC
Duration
21m
Affected: Outgoing Calls
Timeline · 4 updates
  1. investigating Jan 05, 2026, 11:37 PM UTC

    We are currently investigating a problem with some of our primary route partners responding with failed calls. We are investigating this and working to a resolution asap.

  2. investigating Jan 05, 2026, 11:51 PM UTC

    We are continuing to investigate the outgoing calling problem. This issue has been elevated to Major outgoing calling outage. We hope to provide answers very shortly.

  3. monitoring Jan 05, 2026, 11:53 PM UTC

    The outgoing call routing has been restored and calls are now completing. We are continuing out investigating.

  4. resolved Jan 05, 2026, 11:58 PM UTC

    The issue affecting outgoing call routing has been fully resolved and service has been restored. Following corrective actions, outbound calls are completing normally. We will continue to closely monitor the platform to ensure ongoing stability. We apologize for any inconvenience this may have caused and appreciate everyone’s patience while we worked through this issue.

Read the full incident report →

Notice November 11, 2025

Line Registration Failing

Detected by Pingoru
Nov 11, 2025, 07:47 PM UTC
Resolved
Nov 11, 2025, 07:51 PM UTC
Duration
4m
Timeline · 2 updates
  1. monitoring Nov 11, 2025, 07:47 PM UTC

    We are currently monitoring lines that have just become unregistered preventing calls from completing. Services are restored, we are continuing to monitor the situation.

  2. resolved Nov 11, 2025, 07:51 PM UTC

    The issue affecting line registration has been identified, and temporary maintenance has been completed. Services have been fully restored and are currently stable. Additional maintenance will be performed tonight to implement a permanent fix.

Read the full incident report →

Notice November 9, 2025

Call Completion Issues

Detected by Pingoru
Nov 09, 2025, 04:43 PM UTC
Resolved
Nov 09, 2025, 04:44 PM UTC
Duration
1m
Timeline · 2 updates
  1. investigating Nov 09, 2025, 04:43 PM UTC

    We have become aware of an issue with some incoming and outgoing calls completing. We are investigating and will provide an update shorty.

  2. resolved Nov 09, 2025, 04:44 PM UTC

    Calls are now completing.

Read the full incident report →

Notice October 20, 2025

Device Registration Issue Affecting Call Functionality

Detected by Pingoru
Oct 20, 2025, 11:28 AM UTC
Resolved
Oct 20, 2025, 11:39 AM UTC
Duration
10m
Affected: SIP Registration
Timeline · 4 updates
  1. investigating Oct 20, 2025, 11:28 AM UTC

    We are currently investigating an issue causing some devices to fail registration, which is preventing affected users from making telephone calls. Our team is working to resolve this as quickly as possible and will provide updates shortly.

  2. investigating Oct 20, 2025, 11:32 AM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 20, 2025, 11:33 AM UTC

    We are currently investigating an issue causing some devices to fail registration, which is preventing affected users from making telephone calls. Our team is working to resolve this as quickly as possible and will provide updates shortly.

  4. resolved Oct 20, 2025, 11:39 AM UTC

    The trouble with device registration has been resolved.

Read the full incident report →