LoopUp Outage History

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

There were 29 LoopUp outages since May 23, 2024 totaling 168h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.loopup.com

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 →

Major July 19, 2024

Microsoft outage affecting Remote Meetings and Operator Assisted Events

Detected by Pingoru: Jul 19, 2024, 08:22 AM UTC
Resolved: Jul 21, 2024, 07:09 PM UTC
Duration: 2d 10h

Timeline · 2 updates

identified Jul 19, 2024, 08:22 AM UTC

Microsoft is currently experiencing a global outage which is adversely affecting some of LoopUp's services: Remote Meetings customers may be unable to access meeting links, account.loopup.com and the mobile app. Outbound calls are affected. However, inbound calls are routing successfully. Operator-assisted customers may also experience some disruption. If you have a scheduled event, your operator will be in contact to arrange an alternative date and time. Cloud Telephony services are largely unaffected. Based on Microsoft's description and internal tests, presence-based mode may be affected, but calls are routing successfully, both inbound and outbound. We apologize for any inconvenience this may cause and appreciate your patience as we and Microsoft work through these issues. For any questions or further assistance, please contact us at [email protected].
resolved Jul 21, 2024, 07:09 PM UTC

We are pleased to inform you that normal service has been restored across all LoopUp services. Thank you for your patience and understanding during this time. If you have any further questions or need assistance, please do not hesitate to contact us at [email protected].

Read the full incident report →

Major July 12, 2024

Cloud Telephony / Remote Meetings - Asia-Pacific - Degraded Performance

Detected by Pingoru: Jul 12, 2024, 07:39 AM UTC
Resolved: Jul 15, 2024, 08:15 AM UTC
Duration: 3d

Affected: Asia-Pacific

Timeline · 3 updates

identified Jul 12, 2024, 07:39 AM UTC

We have identified an incident impacting our Cloud Telephony and Remote Meetings platform in the Asia-Pacific region. Affected users may experience intermittent audio issues and an inability to end their calls. This issue affects calls in both directions and is currently being investigated by our Network Operations Team as a high priority. We apologize for any inconvenience this may cause and appreciate your patience as we work to resolve it. Our Support Team is available 24/7 at [email protected] should you have any questions or need assistance.
monitoring Jul 12, 2024, 08:47 AM UTC

A fix has been implemented, and we are closely monitoring the situation. We have engaged our SBC vendor and will continue reviewing the logs with their assistance. We apologize for the inconvenience. Should you experience any further issues, please contact us at [email protected]
resolved Jul 15, 2024, 08:15 AM UTC

After monitoring over the weekend, we are now confident that the issue affecting our platform in the Asia-Pacific region is fully resolved. If you require more information, please contact us at [email protected]. Thank you for your patience and understanding.

Read the full incident report →