LoopUp Outage History

LoopUp is up right now

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

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

Source: https://status.loopup.com

Minor March 23, 2026

Cloud Telephony - South Korea - Service disruption impacting inbound calls

Detected by Pingoru
Mar 23, 2026, 11:31 AM UTC
Resolved
Mar 24, 2026, 09:53 AM UTC
Duration
22h 22m
Affected: Asia-Pacific
Timeline · 2 updates
  1. investigating Mar 23, 2026, 11:31 AM UTC

    We are currently experiencing issues in South Korea, where some inbound calls may fail to connect. We are working with the relevant upstream carrier as a matter of urgency to restore normal service. Further updates will be shared as more information becomes available. If you are experiencing issues, please contact [email protected].

  2. resolved Mar 24, 2026, 09:53 AM UTC

    The issue affecting inbound calls in South Korea has now been fully resolved. Testing and monitoring confirm that services are operating normally, with calls connecting as expected. We will continue to monitor to ensure ongoing stability. If you experience any further issues, please contact [email protected].

Read the full incident report →

Minor March 20, 2026

Possible service disruption in South Korea and Israel

Detected by Pingoru
Mar 20, 2026, 09:25 AM UTC
Resolved
Mar 20, 2026, 12:29 PM UTC
Duration
3h 3m
Affected: Europe, the Middle East and AfricaAsia-Pacific
Timeline · 3 updates
  1. investigating Mar 20, 2026, 09:25 AM UTC

    We are currently experiencing issues in South Korea and Israel, where some inbound calls may fail to connect. We are working with the relevant upstream carrier as a matter of urgency to restore normal service. We will provide further updates as more information becomes available. If you are experiencing issues, please contact [email protected].

  2. identified Mar 20, 2026, 09:44 AM UTC

    The carrier has identified the issue and applied a fix. This now needs to be implemented more widely across their network. Initial testing has been successful, and calls are completing as expected. Please stand by while the fix is rolled out more broadly. We will provide further updates as more information becomes available.

  3. resolved Mar 20, 2026, 12:29 PM UTC

    The issue affecting inbound calls in Hong Kong and Israel has now been fully resolved. Testing and monitoring confirm that services are operating normally, with calls connecting as expected. We will continue to monitor to ensure ongoing stability. If you experience any further issues, please contact [email protected].

Read the full incident report →

Minor March 10, 2026

South Africa - Network Issue

Detected by Pingoru
Mar 10, 2026, 08:41 AM UTC
Resolved
Mar 10, 2026, 10:45 AM UTC
Duration
2h 3m
Affected: South Africa
Timeline · 3 updates
  1. identified Mar 10, 2026, 08:41 AM UTC

    We are currently investigating a network issue affecting services in South Africa. Inbound calls are now operating normally. However, we have observed that some outbound calls are being rejected by a downstream carrier and therefore failing over to alternate routes. Calls are still connecting, but may be routed differently than usual. We will continue to investigate and provide further updates as more information becomes available. If you have any questions, please contact us at [email protected].

  2. identified Mar 10, 2026, 08:54 AM UTC

    Our downstream carrier in South Africa has confirmed an issue affecting voice services on their network. As a result, some calls may experience intermittent disruptions. The carrier is actively escalating the issue and working to restore normal service as quickly as possible. In the meantime, calls are failing over to alternate routes. We will provide further updates as more information becomes available. If you have any questions, please contact us at [email protected].

  3. resolved Mar 10, 2026, 10:45 AM UTC

    We believe the issue has now been resolved. Testing indicates that services are functioning normally, with calls completing successfully across the network. We will continue to monitor the situation to ensure stability. If you experience any further issues, please contact us at [email protected].

Read the full incident report →

Minor March 5, 2026

Cloud Telephony - Admin Portal - Reporting Dashboard

Detected by Pingoru
Mar 05, 2026, 08:46 AM UTC
Resolved
Mar 09, 2026, 08:30 AM UTC
Duration
3d 23h
Affected: Admin Portal
Timeline · 2 updates
  1. monitoring Mar 05, 2026, 08:46 AM UTC

    We have identified an issue impacting the "Reporting" area of the LoopUp One Portal. Customers accessing their reporting summary or call detail records may not be presented with any call data after the 13th of February, 2026. Our teams are actively working to resolve this issue, and a fix has already been released. Call data will gradually start to populate for usage reports from the 13th of February. It's estimated that this sync may take a couple of days to complete. Thank you for your patience and understanding. If you have any questions, our Support Team are available 24/7 at [email protected].

  2. resolved Mar 09, 2026, 08:30 AM UTC

    We believe that all CDR data has now been restored. Will continue to monitor performance closely. If you encounter any further issues, please contact us at [email protected].

Read the full incident report →

Minor January 27, 2026

Cloud Telephony - APAC - Call failures impacting outbound calling in China

Detected by Pingoru
Jan 27, 2026, 09:18 AM UTC
Resolved
Jan 27, 2026, 04:49 PM UTC
Duration
7h 31m
Affected: Asia-Pacific
Timeline · 2 updates
  1. identified Jan 27, 2026, 09:18 AM UTC

    We have identified an issue affecting outbound calling in China, where-in some Users may experience failures when making both domestic and international calls. This issue was caused by an incident impacting an in-country carrier, from approximately 15:00 local time (07:00 UTC). Services are now being gradually restored. We're sorry to be holding you up today and appreciate your patience. If you have any questions, our Support Team are available 24/7 at [email protected].

  2. resolved Jan 27, 2026, 04:49 PM UTC

    We believe that all impacted service areas are now operational. Should you require additional information or wish to report a new issue, please contact our Support Team at [email protected].

Read the full incident report →

Notice November 20, 2025

Cloud Telephony - Intermittent load issues impacting the LoopUp Admin Portal (admin.loopup.com and one.loopup.com)

Detected by Pingoru
Nov 20, 2025, 10:38 AM UTC
Resolved
Nov 20, 2025, 04:05 PM UTC
Duration
5h 26m
Affected: Admin Portal
Timeline · 4 updates
  1. identified Nov 20, 2025, 10:38 AM UTC

    We are currently investigating an issue impacting access to the LoopUp Cloud Telephony Admin Portal (admin.loopup.com) and LoopUp One (one.loopup.com). Users may experience intermittent issues and delays when attempting to navigate/sign-in to these portals. Some Users may be presented with an "Unable to load this page" error message or load a blank page. Our Teams are investigating, and we will provide more information as soon as it's available. Should you need any immediate assistance, our Support Team are available 24/7 at [email protected].

  2. identified Nov 20, 2025, 01:23 PM UTC

    Our Teams are still investigating, and we hope to have more clarity on the underlying cause very soon. We apologise for the disruption. The LoopUp Support Team are available 24/7 at [email protected], if you need any assistance.

  3. monitoring Nov 20, 2025, 02:28 PM UTC

    Services have now been restored. We will continue to monitor the situation closely and provide updates as additional information becomes available.

  4. resolved Nov 20, 2025, 04:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 18, 2025

Cloudflare Outage Impacting LoopUp Admin Portal

Detected by Pingoru
Nov 18, 2025, 02:36 PM UTC
Resolved
Nov 19, 2025, 09:04 AM UTC
Duration
18h 27m
Affected: Admin Portal
Timeline · 2 updates
  1. identified Nov 18, 2025, 02:36 PM UTC

    We are currently experiencing an issue affecting access to LoopUp One. Administrators are unable to log in and manage telephony services. Our engineering team has identified the root cause as a widespread Cloudflare outage, and we are actively working with our partners to restore services as quickly as possible. For real-time updates, please visit: https://www.cloudflarestatus.com. We will share further information and updates as soon as they become available. If you require immediate assistance, our Support Team is available 24/7 at [email protected].

  2. resolved Nov 19, 2025, 09:04 AM UTC

    Our monitoring indicates that the Cloudflare issue affecting LoopUp One has now been resolved and full service has been restored. If you experience any further issues, please contact us at [email protected].

Read the full incident report →

Notice June 12, 2025

Cloud Telephony - Thailand Call Disruption

Detected by Pingoru
Jun 12, 2025, 09:36 AM UTC
Resolved
Jun 12, 2025, 08:11 PM UTC
Duration
10h 35m
Affected: Asia-Pacific
Timeline · 2 updates
  1. identified Jun 12, 2025, 09:36 AM UTC

    We’ve received reports of call failures affecting some users in Thailand. SBC traces show that the calls are not reaching our network. We’ve engaged our partner carrier to investigate and clarify the root cause. The extent of the issue is not yet known, and further testing is currently underway. We’ll continue to provide updates as more information becomes available. Thank you for your continued patience.

  2. resolved Jun 12, 2025, 08:11 PM UTC

    The issue was identified and resolved earlier today by our partner carrier. Initial tests are showing positive results, and services appear to be operating normally. We are continuing to monitor. If you experience any further issues, please contact us at [email protected].

Read the full incident report →

Notice April 14, 2025

Direct Routing - Call Disruption in China

Detected by Pingoru
Apr 14, 2025, 09:26 AM UTC
Resolved
Apr 22, 2025, 07:14 AM UTC
Duration
7d 21h
Affected: Asia-Pacific
Timeline · 4 updates
  1. identified Apr 14, 2025, 09:26 AM UTC

    We are aware of an issue affecting some of our services in China, where users may experience disruptions when making or receiving calls. The issue has been identified as a downstream network problem, and our carrier is currently working to resolve it. If you are experiencing any issues, please contact us at [email protected]. We’re sorry for the disruption and appreciate your patience as we work to restore normal service.

  2. identified Apr 15, 2025, 04:19 PM UTC

    The issues affecting call services in China are ongoing. We’ve been informed that the disruptions are related to anti-harassment and anti-fraud measures implemented by the Chinese Ministry of Industry and Information Technology (MIIT). Our carrier is actively working with local carriers to restore service as quickly as possible. We’ll continue to provide updates as more information becomes available. Thank you for your continued patience.

  3. identified Apr 16, 2025, 09:43 AM UTC

    It appears that an upstream carrier has been directly impacted by the enhanced anti-harassment and anti-fraud measures implemented by the Chinese Ministry of Industry and Information Technology (MIIT). We are continuing to escalate the issue with our partner; however, we do not yet have an estimated time for full service restoration. We appreciate your patience and will share further updates as soon as we have more information.

  4. resolved Apr 22, 2025, 07:14 AM UTC

    Over the weekend, our partner carrier successfully restored services in coordination with the Chinese Ministry of Industry and Information Technology (MIIT). We’ve since confirmed with impacted customers that all services are now operating normally. If you experience any further issues, please contact us at [email protected]. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Notice March 27, 2025

Calls to French Mobile Numbers

Detected by Pingoru
Mar 27, 2025, 04:40 PM UTC
Resolved
Mar 31, 2025, 07:38 AM UTC
Duration
3d 14h
Affected: Europe, the Middle East and Africa
Timeline · 3 updates
  1. identified Mar 27, 2025, 04:40 PM UTC

    We've identified an issue causing domestic call failures to certain French mobile numbers. The problem has been traced to our downstream carrier, and we're actively working with them to resolve it. We will provide updates as soon as more information becomes available. Thank you for your patience and understanding. For immediate assistance, our Support Team is available 24/7 at [email protected].

  2. monitoring Mar 27, 2025, 05:58 PM UTC

    The carrier has made corrective changes and we haven't observed any further failures. However, we acknowledge that French working hours have now concluded. If you encounter any new issues or require immediate assistance, please let us know by emailing [email protected].

  3. resolved Mar 31, 2025, 07:38 AM UTC

    Further monitoring concludes that the incident is fully resolved and normal service has been restored. If you experience any further disruption, please contact [email protected]. Thank you for your patience and cooperation.

Read the full incident report →

Notice March 26, 2025

Outbound Calls from Luware Nimbus Services

Detected by Pingoru
Mar 26, 2025, 07:42 PM UTC
Resolved
Mar 28, 2025, 11:13 AM UTC
Duration
1d 15h
Affected: Europe, the Middle East and Africa
Timeline · 3 updates
  1. identified Mar 26, 2025, 07:42 PM UTC

    We have identified an issue affecting outbound calls from Luware Nimbus services, where calls may fail intermittently. This has been escalated to Luware and Microsoft, who are actively investigating. In the meantime, affected users can still place outbound calls directly from the Microsoft Teams client. Please use this workaround while we work with Luware and Microsoft to resolve the issue.

  2. identified Mar 28, 2025, 10:11 AM UTC

    The issue has been identified and isolated to the Luware Nimbus software. Luware’s engineers are actively working on a hotfix and will provide further updates soon. If you have any questions, please contact us at [email protected].

  3. resolved Mar 28, 2025, 11:13 AM UTC

    We're closing this particular incident while Luware continues it's investigation. If you would like to stay informed, please visit and follow https://status.luware.cloud/incident/1341765 for more updates.

Read the full incident report →

Minor March 18, 2025

Verizon European VoIP network outage

Detected by Pingoru
Mar 18, 2025, 01:09 PM UTC
Resolved
Mar 18, 2025, 05:01 PM UTC
Duration
3h 51m
Affected: Europe, the Middle East and Africa
Timeline · 3 updates
  1. identified Mar 18, 2025, 01:09 PM UTC

    We have been made aware of a Verizon European VoIP network outage with the potential to impact some Cloud Telephony and Remote Meetings Customers in Europe. Users may experience issues when placing calls to European DDI's/dial-in numbers on relevant routes. Verizon is actively investigating this issue, and our carriers are prioritizing efforts to resolve it. Our teams have been monitoring the issue and currently assess it to be low impact. We will provide updates as more information becomes available. If you have any questions, please contact our Support Team: https://support.loopup.com/s/contact-support?language=en_US.

  2. monitoring Mar 18, 2025, 03:23 PM UTC

    The Verizon outage has now been resolved. Our teams are now completing testing to confirm that all impacted service areas are operational. We will continue to monitor and share updates. If you have any questions or experience any new issues, please contact our Support Team: https://support.loopup.com/s/contact-support?language=en_US.

  3. resolved Mar 18, 2025, 05:01 PM UTC

    We're confident that all impacted service areas have been restored. If you experience any new issues, please contact our Support Team: https://support.loopup.com/s/contact-support?language=en_US.

Read the full incident report →

Notice March 3, 2025

TM1022107 - Users may experience failures when placing calls to Microsoft Teams provisioned auto attendants and call queues

Detected by Pingoru
Mar 03, 2025, 05:46 PM UTC
Resolved
Mar 04, 2025, 08:24 AM UTC
Duration
14h 38m
Affected: North AmericaLatin AmericaEurope, the Middle East and AfricaSouth AfricaAsia-PacificOceania
Timeline · 2 updates
  1. monitoring Mar 03, 2025, 05:46 PM UTC

    Microsoft has published TM1022107, advising that users may experience call failures when attempting to reach Microsoft Teams auto attendants and call queues. To stay updated, please log in to https://admin.microsoft.com/ and check for updates under Service health. Alternatively, admins can log in to https://admin.loopup.com/ and set up a conditional forward to an external number by navigating to Phone Numbers > Number Management > Forward to. If you would like assistance, please contact us on [email protected].

  2. resolved Mar 04, 2025, 08:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2025

Cloud Telephony - Inbound call disruption in Australia

Detected by Pingoru
Mar 02, 2025, 07:14 PM UTC
Resolved
Mar 03, 2025, 08:26 AM UTC
Duration
13h 11m
Affected: Oceania
Timeline · 4 updates
  1. investigating Mar 02, 2025, 07:14 PM UTC

    We've identified an issue affecting inbound calls in Australia, where some INVITE requests are not reaching our downstream SBC. The issue has been escalated to our Network Operations Team, and we are working to resolve it as quickly as possible. We appreciate your patience and will provide further updates as soon as we have more information. If you have any immediate concerns, please contact us at [email protected].

  2. identified Mar 02, 2025, 08:12 PM UTC

    We believe we have identified the issue and are working with our internal teams to resolve it as quickly as possible. We're sorry for slowing you down today and appreciate your patience. If you have any questions, please contact us at [email protected].

  3. identified Mar 02, 2025, 08:51 PM UTC

    Although the underlying issue has been resolved, we have identified a further issue where Microsoft is not responding to inbound invites. Testing confirms this is isolated to Operator Connect calls. We appreciate your patience and will provide further updates as soon as we have more information. If you have any immediate concerns, please contact us at [email protected].

  4. resolved Mar 03, 2025, 08:26 AM UTC

    A fix was implemented at 22:02 UTC last night, and normal services were gradually restored afterward. We are currently investigating the root cause with Microsoft, but inbound Operator Connect calls to Australian numbers are now functioning correctly. If you are still experiencing issues, please contact us at [email protected].

Read the full incident report →

Minor February 28, 2025

Cloud Telephony - Service disruption in ZA

Detected by Pingoru
Feb 28, 2025, 09:34 AM UTC
Resolved
Feb 28, 2025, 10:40 AM UTC
Duration
1h 6m
Affected: South Africa
Timeline · 2 updates
  1. investigating Feb 28, 2025, 09:34 AM UTC

    We've identified an issue in South Africa where the local carrier is rejecting outbound call attempts. While our failover mechanisms ensure calls are terminating successfully, there may be an impact on CLI presentation. We have escalated the issue to our carrier and are working closely with them to resolve it as quickly as possible. We appreciate your patience and will provide further updates as soon as possible. If you experience any ongoing issues, please contact us at [email protected].

  2. resolved Feb 28, 2025, 10:40 AM UTC

    The issue has now been resolved, and all outbound calls in South Africa are successfully routing through our domestic carrier. We can confirm that CLI presentation is functioning as expected, and normal service has been fully restored. We apologize for any inconvenience this may have caused. If you experience any further issues, please contact us at [email protected].

Read the full incident report →

Major February 17, 2025

Cloud Telephony - Admin Portal [Load Issues impacting admin.loopup.com]

Detected by Pingoru
Feb 17, 2025, 05:47 PM UTC
Resolved
Feb 18, 2025, 08:28 AM UTC
Duration
14h 41m
Affected: Admin Portal
Timeline · 3 updates
  1. identified Feb 17, 2025, 05:47 PM UTC

    We are currently investigating a load issue impacting the Cloud Telephony Admin Portal. Admins will experience issues when attempting to load admin.loopup.com and may see an "unable to load this page" error message. We’re aware of the issue and are working on it urgently. If you have any critical or time-sensitive administrative requests that we can help with, our Support Team are available 24/7 at [email protected].

  2. monitoring Feb 17, 2025, 06:00 PM UTC

    Normal service has been restored, as of 17:45 GMT/UTC. If you experience any further disruption when attempting to access the Cloud Telephony Admin Portal, please contact [email protected].

  3. resolved Feb 18, 2025, 08:28 AM UTC

    After further monitoring, we can confirm that this issue has been resolved. If you experience any new issues, don't hesitate to get in touch with us at [email protected].

Read the full incident report →

Notice February 17, 2025

Operator Connect - EMEA - Possible service disruption

Detected by Pingoru
Feb 17, 2025, 01:44 PM UTC
Resolved
Feb 17, 2025, 04:39 PM UTC
Duration
2h 54m
Affected: Europe, the Middle East and Africa
Timeline · 2 updates
  1. identified Feb 17, 2025, 01:44 PM UTC

    We are investigating reports of intermittent call failures in the EMEA SBC region between 12:00-12:30 UTC. Some users may have experienced issues when attempting outbound calls. Following internal testing, we can confirm that the service is now operating normally. However, we are continuing to monitor while investigating the root cause. If you are still experiencing any issues, please contact us at [email protected].

  2. resolved Feb 17, 2025, 04:39 PM UTC

    The service has remained stable, and no further issues have been identified. We have determined the root cause and are working on a permanent fix. In the meantime, additional safeguards have been implemented to prevent any recurrence. Thank you for your patience. If you have any concerns, please contact us at [email protected].

Read the full incident report →

Major February 17, 2025

Operator Assisted Events - Replay Service

Detected by Pingoru
Feb 17, 2025, 11:27 AM UTC
Resolved
Feb 17, 2025, 04:40 PM UTC
Duration
5h 13m
Timeline · 2 updates
  1. investigating Feb 17, 2025, 11:27 AM UTC

    We are currently investigating an issue affecting the Event Replay service, preventing users from connecting. At this time, there is no known workaround. Our team is working diligently to resolve the issue as quickly as possible. If you have any questions, please contact us at [email protected]. We appreciate your patience and understanding.

  2. resolved Feb 17, 2025, 04:40 PM UTC

    Normal service has been restored and Event Replay is now fully functional. We have monitored since applying the fix and no further issues have been observed. If you have any questions, please contact us at [email protected]. We appreciate your patience and understanding.

Read the full incident report →

Minor January 27, 2025

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

Detected by Pingoru
Jan 27, 2025, 08:30 AM UTC
Resolved
Jan 27, 2025, 12:14 PM UTC
Duration
3h 44m
Timeline · 3 updates
  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].

Read the full incident report →

Minor January 21, 2025

Cloud Telephony - Thailand

Detected by Pingoru
Jan 21, 2025, 10:12 AM UTC
Resolved
Jan 21, 2025, 05:59 PM UTC
Duration
7h 46m
Affected: Asia-Pacific
Timeline · 2 updates
  1. investigating Jan 21, 2025, 10:12 AM UTC

    We have identified an issue affecting some local services in Thailand. Our team is actively working with the carrier in question to restore service as quickly as possible. Thank you for your patience and understanding. If you have any immediate questions or concerns, please do not hesitate to contact us at [email protected].

  2. resolved Jan 21, 2025, 05:59 PM UTC

    The carrier has confirmed that service in Thailand has now been restored. If you experience any issues, please do not hesitate to let us know at [email protected]. Thank you for your patience and understanding.

Read the full incident report →

Minor December 19, 2024

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

Detected by Pingoru
Dec 19, 2024, 05:37 PM UTC
Resolved
Jan 06, 2025, 12:20 PM UTC
Duration
17d 18h
Affected: Latin America
Timeline · 2 updates
  1. identified Dec 19, 2024, 05:37 PM UTC

    We have identified an issue with Microsoft Teams calls to Brazil numbers, where users may experience periods of one-way audio. Our investigation confirms that we are successfully receiving and sending media in both directions. As a result, the issue has been escalated to our downstream carrier for further resolution. Thank you for your patience and understanding as we work to resolve this matter. If you have any immediate questions or concerns, please contact us at [email protected].

  2. resolved Jan 06, 2025, 12:20 PM UTC

    Remedial action was implemented last week, and we have been closely monitoring the situation since. We are pleased to confirm that the issues have now been resolved. Thank you for your patience and understanding during this time. 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 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
  1. 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].

  2. 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].

  3. 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
  1. 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].

  2. 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.

  3. 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 →