All Systems Operational
About This Site
This page displays performance data for the LoopUp Cloud Telephony network and its associated applications. Any service interruptions or planned maintenance updates will be posted here.
Cloud Telephony
Operational
Admin Portal
Operational
North America
Operational
Latin America
Operational
Europe, the Middle East and Africa
Operational
South Africa
Operational
Asia-Pacific
Operational
Oceania
Operational
India
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
SIP signalling update for TLS-encrypted SIP trunks in EMEA region Nov 18, 2026 04:00-04:30 UTC
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
Posted on Nov 05, 2026 - 18:42 UTC
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
Posted on Nov 05, 2026 - 18:42 UTC