LoopUp Outage History

Started Sep 19, 2026, 08:30 AM UTC· resolved Sep 21, 2026, 09:18 AM UTC

1. investigating Sep 19, 2026, 08:30 AM UTC

   We are currently experiencing a disruption affecting outbound calls in Taiwan. We are working with our downstream carrier to restore service as quickly as possible. We apologise for the inconvenience and appreciate your patience while we work to resolve the issue. We will provide a further update as soon as more information is available.

2. identified Sep 21, 2026, 07:47 AM UTC

   Our carrier has identified the issue, and we are working with them to restore service as soon as possible. We apologise for the disruption and appreciate your patience while we work to resolve the issue.

3. resolved Sep 21, 2026, 09:18 AM UTC

   The carrier has now resolved the issue, and outbound calling in Taiwan has been restored. We are working with our partner carrier to understand what caused the disruption. Further details will be provided via your support case. We apologise for the inconvenience and thank you for your patience.

Read the full incident report →

Started Aug 25, 2026, 08:17 AM UTC· resolved Aug 25, 2026, 08:17 AM UTC

1. resolved Aug 25, 2026, 08:17 AM UTC

   Vivo has implemented an anti-spam call filtering system that is affecting call completion to Vivo mobile numbers across Brazil. This is an industry-wide issue affecting all telecom operators, not something specific to LoopUp or any single carrier partner. Impact: Customers may experience calls to Vivo mobile numbers in Brazil failing to connect or ring. What we're doing: We're monitoring the situation alongside our carrier partners and will update you if Vivo's filtering criteria change or a resolution timeline emerges. There is currently no fix timeline, as this is a unilateral change on Vivo's network. What customers can do: If a specific number needs to be reviewed, Vivo offers a business unblock request form at vivo.com.br/para-empresas/modo-seguro/anti-spam, requiring the CNPJ, company name, and the affected number.

Read the full incident report →

Started Aug 21, 2026, 09:57 PM UTC· resolved Aug 22, 2026, 12:26 PM UTC

1. identified Aug 21, 2026, 09:57 PM UTC

   We have identified an issue impacting inbound calls. Some callers may connect to our ‘Welcome to LoopUp’ prompt instead of reaching the intended call destination. We are aware of the issue and are working on it urgently. 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 Service Desk Team are available 24/7 at [email protected].

2. resolved Aug 22, 2026, 12:26 PM UTC

   The issue impacting inbound calls has now been resolved. Callers should no longer be routed to the 'Welcome to LoopUp' prompt and calls are connecting to their intended destinations as normal. We will follow up directly with affected customers to explain what happened and outline the steps we are taking to prevent a recurrence. We apologise for any inconvenience caused. Our Service Desk Team remain available 24/7 at [email protected].

Read the full incident report →

Started May 27, 2026, 02:12 PM UTC· resolved May 28, 2026, 09:32 AM UTC

1. identified May 27, 2026, 02:12 PM UTC

   We are currently investigating an issue affecting a small subset of inbound calls to UK numbers. In some cases, calls connect successfully but no audio is present, which may cause calls to disconnect shortly after being answered. We are working with the relevant carrier to identify the root cause and restore normal service as quickly as possible. Further updates will be provided as more information becomes available. If you are experiencing issues, please contact [email protected].

2. monitoring May 27, 2026, 04:07 PM UTC

   A workaround has been deployed and calls are now routing successfully with audio. The issue appears to be isolated to a specific carrier in the UK. We are continuing to escalate the issue and work with the carrier to implement a permanent resolution. Please re-test and let us know if the issue persists by contacting [email protected].

3. resolved May 28, 2026, 09:32 AM UTC

   The issue affecting a subset of inbound calls to UK numbers has now been resolved. The temporary workaround has been removed, and services are operating normally. Testing and monitoring confirm that call routing and audio are stable across the platform. If you experience any further issues, please contact [email protected].

Read the full incident report →

Started Mar 23, 2026, 11:31 AM UTC· resolved Mar 24, 2026, 09:53 AM UTC

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 →

Started Mar 20, 2026, 09:25 AM UTC· resolved Mar 20, 2026, 12:29 PM UTC

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 →

Started Mar 10, 2026, 08:41 AM UTC· resolved Mar 10, 2026, 10:45 AM UTC

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 →

Started Mar 05, 2026, 08:46 AM UTC· resolved Mar 09, 2026, 08:30 AM UTC

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 →

Started Jan 27, 2026, 09:18 AM UTC· resolved Jan 27, 2026, 04:49 PM UTC

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 →

Started Nov 20, 2025, 10:38 AM UTC· resolved Nov 20, 2025, 04:05 PM UTC

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 →

Started Nov 18, 2025, 02:36 PM UTC· resolved Nov 19, 2025, 09:04 AM UTC

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 →

Started Sep 17, 2025, 01:55 PM UTC· resolved Oct 21, 2025, 09:07 AM UTC

1. identified Sep 17, 2025, 01:55 PM UTC

   Our Chinese partners have informed us that China Telecom is conducting a risk assessment of its SIP numbers in Shanghai and Beijing. During this maintenance, some services, particularly CLI presentation, may be affected. If you require further information, please contact us at [email protected]. We will provide additional updates as they become available.

2. identified Sep 19, 2025, 10:26 AM UTC

   We’ve been informed that the ongoing maintenance may also affect other cities. Outbound calls are still being masked and should route correctly while the assessment is carried out. We expect to receive an official document from the regulator next week outlining the full impact and estimated restoration times. Further updates will be provided as soon as this information becomes available.

3. identified Sep 23, 2025, 07:43 AM UTC

   The risk assessment is still ongoing. We’ve been advised that the regulator is working to complete the required checks as quickly as possible. Unfortunately, some services remain affected. Outbound calls are still being masked as a temporary workaround. We will continue to share updates as soon as more information becomes available.

4. identified Sep 29, 2025, 08:13 AM UTC

   The regulatory assessment is nearly complete, and we are now working with our downstream partner to remove the temporary workaround and restore normal service. Full inbound functionality has been reinstated, and work is underway to restore outbound calling and CLI passthrough. In the meantime, outbound calls continue to route with a temporary CLI. If you require further information, please contact us at [email protected]. We will provide further updates as more information becomes available.

5. identified Sep 30, 2025, 02:11 PM UTC

   We have received confirmation that governmental departments have temporarily suspended all changes to the PSTN due to the upcoming National Day holiday. As a result, outbound calls are expected to remain masked until approximately mid-October. We are doing everything possible to restore normal service sooner; however, the timeline is dependent on Chinese government processes. Please note that inbound services continue to operate as normal.

6. identified Oct 13, 2025, 08:00 AM UTC

   We’ve been advised that the validation process has resumed following the end of the National Day holiday period. Our partners are working closely with the local telecom provider to lift the outbound call restrictions as soon as possible. We will provide further updates as more information becomes available.

7. resolved Oct 21, 2025, 09:07 AM UTC

   We’re pleased to confirm that the assessment has been fully completed and all functionality has now been restored. We apologize for any inconvenience this may have caused. This audit is an essential part of telephony operations in China, ensuring compliance with national standards and regulations so that our service remains trusted, robust, and compliant. Thank you for your patience and cooperation throughout this process. If you experience any further issues, please contact us at [email protected].

Read the full incident report →

Started Jun 12, 2025, 09:36 AM UTC· resolved Jun 12, 2025, 08:11 PM UTC

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 →

Started Apr 14, 2025, 09:26 AM UTC· resolved Apr 22, 2025, 07:14 AM UTC

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 →

Started Mar 27, 2025, 04:40 PM UTC· resolved Mar 31, 2025, 07:38 AM UTC

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 →

Started Mar 26, 2025, 07:42 PM UTC· resolved Mar 28, 2025, 11:13 AM UTC

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 →

Started Mar 18, 2025, 01:09 PM UTC· resolved Mar 18, 2025, 05:01 PM UTC

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 →

Started Mar 03, 2025, 05:46 PM UTC· resolved Mar 04, 2025, 08:24 AM UTC

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 →

Started Mar 02, 2025, 07:14 PM UTC· resolved Mar 03, 2025, 08:26 AM UTC

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 →

Started Feb 28, 2025, 09:34 AM UTC· resolved Feb 28, 2025, 10:40 AM UTC

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 →

Started Feb 21, 2025, 01:40 PM UTC· resolved Feb 26, 2025, 11:27 AM UTC

1. identified Feb 21, 2025, 01:40 PM UTC

   We have identified an issue today that may have impacted some calls in the EMEA region. Failover mechanisms were triggered, and calls were rerouted to the secondary SBC region. However, some calls did not transition cleanly. Our team is actively investigating with urgency. At present, the service is stable, and we continue to monitor closely. 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. identified Feb 24, 2025, 04:15 PM UTC

   We will be performing maintenance on our core network today (Monday 24th February) between 21:00-22:30 UTC, to address this issue. Please see: https://status.loopup.com/incidents/nm9llz87xktk. We have implemented measures to minimize any potential service impact. If you have any questions or concerns regarding this maintenance activity, please contact our Support Team at [email protected].

3. identified Feb 25, 2025, 09:26 AM UTC

   Following a period of monitoring and further investigation, our teams have determined that the maintenance performed on Monday 24th February has not fully resolved the issue. Consequently, calls in the EMEA region may still be impacted. We are treating this matter as a high priority and will provide updates as soon as they become available. Thank you for your continued patience, and please reach out to our team at [email protected] if you have any questions.

4. monitoring Feb 25, 2025, 10:31 AM UTC

   We believe the issue is now resolved. Ongoing testing indicates that all calls are connecting as expected. However, further investigation is required to determine the root cause. We will continue to monitor the service closely. If you experience any further issues or have any questions, please contact our team at [email protected].

5. monitoring Feb 25, 2025, 04:24 PM UTC

   Following today's disruption, we have scheduled additional maintenance to enhance the stability and resiliency of calls in the EMEA region. This work will take place tonight between 22:00-23:00 UTC. No impact to live services is expected during this time. We appreciate your patience and will provide further updates as needed. If you have any questions or concerns regarding this maintenance activity, please contact our Support Team at [email protected].

6. monitoring Feb 26, 2025, 08:35 AM UTC

   Last night's maintenance was successfully completed. Extensive testing has confirmed that all services are operating as expected. If you experience any issues, please contact [email protected], and our team will be happy to assist.

7. resolved Feb 26, 2025, 11:27 AM UTC

   Further monitoring and testing have confirmed that the issue is fully resolved, and normal service has been restored. We apologise for any inconvenience this may have caused. If you require more information, please contact [email protected].

Read the full incident report →

Started Feb 17, 2025, 05:47 PM UTC· resolved Feb 18, 2025, 08:28 AM UTC

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 →

Started Feb 17, 2025, 01:44 PM UTC· resolved Feb 17, 2025, 04:39 PM UTC

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 →

Started Feb 17, 2025, 11:27 AM UTC· resolved Feb 17, 2025, 04:40 PM UTC

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 →

Started Jan 27, 2025, 08:30 AM UTC· resolved Jan 27, 2025, 12:14 PM UTC

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 →