- 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
-
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.
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Aug 12, 2026, 12:48 PM UTC
- Resolved
- Aug 12, 2026, 02:20 PM UTC
- Duration
- 1h 32m
Affected: Outgoing Calls
Timeline · 6 updates
Read the full incident report →
- 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
-
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.
-
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.
-
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 →
- 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
-
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.
-
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.
-
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.
-
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 →
- 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
-
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.
-
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 →
- Detected by Pingoru
- Apr 15, 2026, 12:08 PM UTC
- Resolved
- Apr 15, 2026, 12:08 PM UTC
- Duration
- –
Timeline · 1 update
-
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 →
- 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
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Feb 17, 2026, 02:43 PM UTC
- Resolved
- Feb 17, 2026, 03:34 PM UTC
- Duration
- 50m
Timeline · 2 updates
-
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
-
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 →
- 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
-
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.
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Nov 12, 2025, 03:53 PM UTC
- Resolved
- Nov 12, 2025, 04:46 PM UTC
- Duration
- 53m
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Nov 11, 2025, 07:47 PM UTC
- Resolved
- Nov 11, 2025, 07:51 PM UTC
- Duration
- 4m
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Nov 09, 2025, 04:43 PM UTC
- Resolved
- Nov 09, 2025, 04:44 PM UTC
- Duration
- 1m
Timeline · 2 updates
-
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.
-
resolved Nov 09, 2025, 04:44 PM UTC
Calls are now completing.
Read the full incident report →
- 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
-
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.
-
investigating Oct 20, 2025, 11:32 AM UTC
We are continuing to investigate this issue.
-
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.
-
resolved Oct 20, 2025, 11:39 AM UTC
The trouble with device registration has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 11, 2025, 02:16 PM UTC
- Resolved
- Jul 11, 2025, 02:37 PM UTC
- Duration
- 20m
Timeline · 3 updates
-
investigating Jul 11, 2025, 02:16 PM UTC
We are currently aware of reports indicating internet service interruptions affecting customers using Videotron internet. This ticket has been opened to facilitate ongoing monitoring and communication regarding the situation. We are awaiting further updates from Videotron and will post any new information here as it becomes available.
-
monitoring Jul 11, 2025, 02:19 PM UTC
During our investigation, we have observed hundreds of similar outage reports affecting Videotron internet users. We remain on hold, awaiting confirmation and an estimated time for resolution from a Videotron engineer. We will continue to monitor the situation and share updates as they become available.
-
resolved Jul 11, 2025, 02:37 PM UTC
Although we were unable to reach a Videotron engineer and remain on hold, we have confirmed that all affected customers under our care have had their internet service restored. As a result, we are no longer actively monitoring this outage and will now be closing this ticket. If you have any further questions, concerns, or ongoing issues related to Videotron internet service, we recommend contacting Videotron directly. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2025, 12:07 PM UTC
- Resolved
- Jun 03, 2025, 01:34 PM UTC
- Duration
- 1h 27m
Timeline · 2 updates
-
investigating Jun 03, 2025, 12:07 PM UTC
We are currently investigating an issue where certain phone terminal devices are unexpectedly becoming unresponsive and rebooting. Our team is working closely with Poly/HP to identify the root cause. At this time, the issue appears to be affecting only a small number of devices. If you are experiencing this problem, we kindly ask that you report it to our support team at [email protected]. We will continue to provide updates through this ticket as more information becomes available. Thank you for your patience and cooperation.
-
resolved Jun 03, 2025, 01:34 PM UTC
We have identified the cause of the recent freeze-and-reboot issue affecting some Polycom devices. The problem has been traced to a specific Polycom firmware version—5.8. Devices running the updated firmware version 5.9 are no longer experiencing this issue. As this impacts only a small number of customers, we are now closing this ticket. Our team will reach out directly to the affected users to coordinate the necessary firmware upgrades. If your organization is experiencing the issue and have not been contacted by our team, please report it to support at [email protected]. Thank you for your understanding and continued support.
Read the full incident report →
- Detected by Pingoru
- May 21, 2025, 01:50 PM UTC
- Resolved
- May 21, 2025, 02:12 PM UTC
- Duration
- 22m
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- May 12, 2025, 07:42 PM UTC
- Resolved
- May 12, 2025, 08:48 PM UTC
- Duration
- 1h 6m
Affected: Intelligent Call Recap
Timeline · 3 updates
-
investigating May 12, 2025, 07:42 PM UTC
We are currently experiencing a service disruption affecting Siclytics Intelligent Call Recap. Users may encounter a “500 Server Error” on screen, and automated call recaps are not completing as expected. Our team is actively investigating the issue and working to resolve it as quickly as possible. We will provide an update as soon as more information becomes available.
-
investigating May 12, 2025, 08:48 PM UTC
We are continuing to investigate this issue.
-
resolved May 12, 2025, 08:48 PM UTC
Resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2025, 07:52 PM UTC
- Resolved
- Mar 19, 2025, 08:59 PM UTC
- Duration
- 1h 7m
Affected: MeloTel Customer PortalClick2Call
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Mar 13, 2025, 04:12 PM UTC
- Resolved
- Mar 13, 2025, 04:19 PM UTC
- Duration
- 6m
Affected: SIClytics Web GUIMonitor Whisper PanelDID Orderinge911 Provisioning Service
Timeline · 2 updates
-
investigating Mar 13, 2025, 04:12 PM UTC
We're Investigating SIClytics 502 Bad Gateway, making the dashboard unavailable.
-
resolved Mar 13, 2025, 04:19 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2025, 05:38 PM UTC
- Resolved
- Feb 27, 2025, 01:21 PM UTC
- Duration
- 19h 43m
Timeline · 2 updates
-
monitoring Feb 26, 2025, 05:38 PM UTC
We are currently monitoring a service disruption affecting Slack, impacting messaging, sign-ins, and other resources. While this issue is not directly related to Melo Technology services, we understand that many of our customers rely on this platform. As a courtesy, we are providing this update and will continue to monitor the situation. We will share any relevant updates as they become available. We apologize for any inconvenience this may cause when attempting to contact our team via Slack. You can monitor the situation here: https://slack-status.com/2025-02/1b757d1d0f444c34
-
resolved Feb 27, 2025, 01:21 PM UTC
While Slack has not officially issued an all-clear, they are reporting only minimal service impact. As a result, we will close this ticket and reopen it if necessary.
Read the full incident report →
- Detected by Pingoru
- Feb 06, 2025, 03:32 PM UTC
- Resolved
- Feb 06, 2025, 03:33 PM UTC
- Duration
- 43s
Affected: SIClytics Web GUIMonitor Whisper PanelDID Orderinge911 Provisioning Service
Timeline · 2 updates
-
investigating Feb 06, 2025, 03:32 PM UTC
We are investigating Siclytics service showing 502 Bad Gateway. Updates to follow.
-
resolved Feb 06, 2025, 03:33 PM UTC
Siclytics service has been restored.
Read the full incident report →
- Detected by Pingoru
- Jan 17, 2025, 04:53 PM UTC
- Resolved
- Jan 17, 2025, 06:30 PM UTC
- Duration
- 1h 37m
Affected: Cloud Softphone SIP App
Timeline · 3 updates
-
investigating Jan 17, 2025, 04:53 PM UTC
We are aware of an issue with incoming and outgoing messaging or originating from the cloud Softphone mobile app. We are currently working on a resolution to this and hope to provide an update soon.
-
monitoring Jan 17, 2025, 05:37 PM UTC
We have identified that the recent issue with sending or receiving SMS messages was caused by a maintenance update. Corrections have been made to the deployment, and SMS functionality is now being restored for most users. If you are still experiencing difficulties with sending or receiving SMS messages, please contact our customer support team at 416-479-0993. They can assist you in resetting your cloud softphone by providing a new registration code. We appreciate your patience and will provide further updates shortly.
-
resolved Jan 17, 2025, 06:30 PM UTC
SMS services through CloudSoftphone have been restored. If you continue to experience any further issues, please contact technical support directly.
Read the full incident report →
- Detected by Pingoru
- Jan 06, 2025, 09:15 PM UTC
- Resolved
- Jan 07, 2025, 10:13 AM UTC
- Duration
- 12h 58m
Affected: SMS MarketingMeloText SMS/MMS Services
Timeline · 3 updates
-
investigating Jan 06, 2025, 09:15 PM UTC
We are currently investigating a problem with Sending/Receiving SMS messages using the cloud softphone application. Users are receiving an error 502 response. We will update as soon as possible.
-
identified Jan 07, 2025, 01:36 AM UTC
We apologize for the continued service disruption in SMS services using our cloud Softphone application. We have identified the issue to our core underlying switch provider for SMS. They have informed us they are restoring services and anticipate a full resolution by 9 AM Eastern standard time Tuesday morning. We apologize for the inconvenience and look forward to providing you a positive update in the morning.
-
resolved Jan 07, 2025, 10:13 AM UTC
CloudSoftphone SMS service has been restored.
Read the full incident report →
- Detected by Pingoru
- Nov 20, 2024, 01:55 PM UTC
- Resolved
- Nov 20, 2024, 02:53 PM UTC
- Duration
- 58m
Affected: Outgoing Calls
Timeline · 2 updates
-
investigating Nov 20, 2024, 01:55 PM UTC
We are currently investigating issues with our primary provider that have resulted in some failed or poor-quality calls. To minimize the impact, we have temporarily adjusted call routing and are actively working with the vendor to resolve the problem. We will share updates as soon as possible. Thank you for your patience.
-
resolved Nov 20, 2024, 02:53 PM UTC
Calling problems were identified as being a temporary issue which affecting multiple carriers across Canada. The issue has been reported to be resolved, and we are unable to replicate any problems at this time. We apologize for any inconvenience if you continue to experience any problems, please report them to technical support.
Read the full incident report →
- Detected by Pingoru
- Oct 29, 2024, 04:43 PM UTC
- Resolved
- Oct 29, 2024, 04:49 PM UTC
- Duration
- 5m
Affected: Shared Hosting ServicesEmail Webmail GUI
Timeline · 2 updates
-
investigating Oct 29, 2024, 04:43 PM UTC
We are currently investigating an issue causing high latency in our shared hosting environment, which may result in temporary loading delays for some hosted websites. Our team is addressing this with urgency and will provide updates as soon as possible. Thank you for your patience as we work to resolve this issue.
-
resolved Oct 29, 2024, 04:49 PM UTC
The performance issue affecting our shared hosting environment has now been resolved. All websites should be loading as expected. We appreciate your patience and understanding during this time.
Read the full incident report →