LoopUp Outage History

LoopUp had 29 outages in the last 2 years totaling 679h 11m of downtime — averaging 1.2 incidents per month.

There were 29 LoopUp outages since September 24, 2024 totaling 679h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.loopup.com

Minor December 11, 2024

Cloud Telephony - Argentina - Some calls may experience one way audio

Detected by Pingoru: Dec 11, 2024, 10:43 AM UTC
Resolved: Jan 06, 2025, 12:21 PM UTC
Duration: 26d 1h

Affected: Latin America

Timeline · 3 updates

investigating Dec 11, 2024, 10:43 AM UTC

We have identified an issue with Microsoft Teams where some calls may experience intermittent periods of one-way audio. This issue appears to be isolated to numbers in Argentina. The matter has been escalated to our Network Operations Team, and we are actively working with them and our downstream partners to resolve it as quickly as possible. Thank you for your patience and understanding. If you have any immediate questions or concerns, please don’t hesitate to reach out to us at [email protected].
monitoring Dec 12, 2024, 03:41 PM UTC

We are pleased to inform you that a workaround has been implemented, and two-way media has been restored for calls to Argentina. Our teams are continuing to investigate the root cause of the issue and will provide further updates in due course. Thank you for your patience and understanding. If you have any questions or experience further issues, please contact us at [email protected].
resolved Jan 06, 2025, 12:21 PM UTC

We are pleased to confirm that the issue has been fully resolved. Thank you for your patience and understanding. If you have any further questions or concerns, please do not hesitate to contact us at [email protected].

Read the full incident report →

Minor December 3, 2024

Remote Meetings - Audio Conferencing - Some US Toll Free Dial-In Numbers are failing to connect

Detected by Pingoru: Dec 03, 2024, 03:25 PM UTC
Resolved: Dec 04, 2024, 08:15 AM UTC
Duration: 16h 49m

Timeline · 3 updates

identified Dec 03, 2024, 03:25 PM UTC

We are currently investigating an issue impacting LoopUp Remote Meetings in the US. Some conference attendees cannot connect to their meetings using US Toll-Free Dial-In numbers. We’re aware of the issue and are working on it urgently. Impacted attendees should dial-in using an alternative Toll/Local number OR connect via the LoopUp web client (https://support.loopup.com/s/article/joining-a-loopup-meeting-as-a-guest?language=en_US) until a resolution has been reached. Please know that our teams are working hard to get everything up and running. We will provide more information as soon as it is available. We're sorry to be holding you up today. Our Support Team are available 24/7 at [email protected].
monitoring Dec 03, 2024, 05:13 PM UTC

We believe that the issue has been rectified as of 15:45 UTC, with all impacted US Toll-Free dial-in numbers now back to an operational state. Should you encounter any further problems when dialling-in to your audio conferences, please contact [email protected]. For guidance on what information to include in your email, please refer to our Support Site: https://support.loopup.com/s/article/Reporting-an-issue-to-the-LoopUp-Team?language=en_US. Thank you again for your patience and understanding.
resolved Dec 04, 2024, 08:15 AM UTC

Our monitoring phase has now been completed and we are confident that the issue affecting some of our US Toll-Free numbers is fully resolved. If you have any questions or require further information, please contact us at [email protected].

Read the full incident report →

Minor November 13, 2024

Cloud Telephony - Czechia - Domestic Outbound

Detected by Pingoru: Nov 13, 2024, 04:10 PM UTC
Resolved: Nov 14, 2024, 10:17 AM UTC
Duration: 18h 7m

Affected: Europe, the Middle East and Africa

Timeline · 2 updates

investigating Nov 13, 2024, 04:10 PM UTC

We have identified possible issues affecting outbound domestic calls in Czechia. The issue has been escalated to our downstream carrier, and we are actively working with them to resolve it. We will provide further updates as soon as possible. Thank you for your patience and understanding. If you have any immediate questions or concerns, please reach out to us at [email protected].
resolved Nov 14, 2024, 10:17 AM UTC

We believe the issue affecting outbound domestic calls in Czechia is now resolved. Please test your service, and if you experience any further issues, do not hesitate to let us know at [email protected]. Thank you for your patience and understanding.

Read the full incident report →

Minor September 24, 2024

Cloud Telephony - Microsoft Teams - Some calls may experience one way audio

Detected by Pingoru: Sep 24, 2024, 03:40 PM UTC
Resolved: Sep 25, 2024, 10:17 AM UTC
Duration: 18h 37m

Affected: North AmericaEurope, the Middle East and AfricaAsia-Pacific

Timeline · 3 updates

investigating Sep 24, 2024, 03:40 PM UTC

We have identified an issue with Microsoft Teams where some calls may experience intermittent periods of one-way audio. This issue appears to be isolated to Azure-hosted infrastructure. We have raised a high-priority escalation with Microsoft and are actively seeking further information. We will continue to monitor the situation closely. For any immediate concerns, please contact us at [email protected].
monitoring Sep 24, 2024, 04:12 PM UTC

It appears that the service has stabilized. The alarms have cleared, and our testing suggests that calls are now connecting without any media issues. We are still working with Microsoft to clarify the issue and identify the root cause. Please kindly re-test, and if you experience any further issues, do not hesitate to let us know. As always, our Support Team is available at [email protected]. Thank you for your patience and understanding.
resolved Sep 25, 2024, 10:17 AM UTC

We are continuing to work with Microsoft to clarify the issue identified yesterday. Separately, Microsoft has posted a notification regarding an unexpected spike in CPU usage affecting their Operator Connect infrastructure, which resulted in degraded performance. It is likely that the two events are linked. Thankfully, our initial diagnostics suggest that the impact on customers was minimal during the reporting period, and it’s likely that most users would not have experienced any issues at all. We will keep you updated as we receive more information. If you have any questions or need further assistance, please feel free to contact us at [email protected].

Read the full incident report →