LoopUp incident
Cloud Telephony - Inbound call disruption in Australia
LoopUp experienced a minor incident on March 2, 2025 affecting Oceania, lasting 13h 11m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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].
- 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].
- 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].
- 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].