LoopUp incident

Remote Meetings - Audio Conferencing - Some Dial-In Numbers allocated to Customers migrated from PGI/Intrado platforms are failing to connect

Minor Resolved View vendor source →

LoopUp experienced a minor incident on January 27, 2025, lasting 3h 44m. The incident has been resolved; the full update timeline is below.

Started
Jan 27, 2025, 08:30 AM UTC
Resolved
Jan 27, 2025, 12:14 PM UTC
Duration
3h 44m
Detected by Pingoru
Jan 27, 2025, 08:30 AM UTC

Update timeline

  1. identified Jan 27, 2025, 08:30 AM UTC

    We've identified an issue that could potentially impact LoopUp Remote Meetings hosted by Users who were migrated from PGI/Intrado platforms. Some conference attendees cannot connect to their meetings by "dialling in" with a number and access code. Our Teams are working with the relevant carrier/s to reach a resolution, ASAP and impacted attendees should connect to their conferences via the LoopUp web client (more information about how to do that here: https://support.loopup.com/s/article/joining-a-loopup-meeting-as-a-guest?language=en_US). 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].

  2. monitoring Jan 27, 2025, 10:20 AM UTC

    Our carriers have implemented a fix and we believe that the issue has been resolved (as of 09:55 UTC). Our Team will continue to monitor and complete further testing. If you experience any new issues, please reach out to us at [email protected].

  3. resolved Jan 27, 2025, 12:14 PM UTC

    We have confirmed that all impacted service areas have now been restored. If you experience any new issues, please reach out to us at [email protected].