Is LoopUp Down?

Microsoft has confirmed the global outage is resolved. LoopUp’s own platform and voice services were not affected at any point. Email intake and case submission are now working normally. --- [2026-11-13T13:00:52.718Z] (monitoring) Microsoft services appear to be slowly recovering. We’re seeing signs that email intake is starting to work again. Voice services have remained unaffected throughout. We’re continuing to monitor the situation closely. If you need urgent support, please call us. Microsoft’s updates are at https://status.cloud.microsoft. --- [2026-11-13T09:52:12.797Z] (identified) We’re aware of an ongoing service outage affecting a number of Microsoft 365 services. We’ve run thorough tests across our platform, and LoopUp voice services appear to be unaffected. Inbound and outbound calling through our platform remains functional. However, please note the following: - Ticketing: Our email service is affected by the outage, so we may not receive tickets sent by email or LoopUp One. If you need help, please call us instead using the details below. - Teams Admin Center: We’ve seen some disruption in the Teams Admin Center, particularly when making changes. We recommend holding any non-urgent configuration changes until Microsoft confirms the issue is resolved. For the latest on the incident, please follow https://status.cloud.microsoft/ If you have any issues, please call one of our regional support numbers: https://support.loopup.com/s/contact-support

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. --- [2026-09-21T07:47:35.036Z] (identified) 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. --- [2026-09-19T08:30:06.837Z] (investigating) 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.

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.

This maintenance activity has been rescheduled for Thursday 19th November at 04:00 UTC. A reminder that no customer impact is expected, but If your equipment is specifically configured to require sips: URIs, please contact us before 19th November. If you experience any call issues after the change, please contact LoopUp at servicedesk@loopup.com --- [2026-11-05T18:42:59.906Z] (scheduled) What’s changing On Wednesday 18th November at 04:00 UTC, we’ll apply a standardisation update to EMEA SIP trunks that connect to LoopUp over TLS. Currently, the SIP messages we send to your equipment use a mix of sip: and sips: in their address headers. After the change, they’ll consistently use sip: Why we’re making this change Some endpoints rejects calls where these address fields are inconsistent. This change makes our signalling consistent and aligned with current SIP standards (RFC 5630), improving compatibility across varying customer environments. Impact No customer impact is expected, and no action is needed. Signalling stays encrypted with TLS, and media encryption is unchanged. If your equipment is specifically configured to require sips: URIs, please contact us before 18th November. If you experience any call issues after the change, please contact LoopUp at servicedesk@loopup.com