LoopUp Outage History

LoopUp is up right now

There were 4 LoopUp outages since March 5, 2026 totaling 123h 13m 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 →

Looking to track LoopUp downtime and outages?

Pingoru polls LoopUp's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when LoopUp reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track LoopUp alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring LoopUp for free

5 free monitors · No credit card required