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
Scheduled maintenance - South Africa SIP trunking Oct 15, 2026 01:00-02:30 UTC
We will be carrying out planned maintenance on our South Africa voice platform during the window above.
What’s changing
For SIP trunks where our platform reaches your SBC by a fully qualified domain name (FQDN), SIP requests sent from LoopUp to your SBC will carry your FQDN in the Request-URI and To header, instead of the resolved IP address. This change improves interoperability with a wider range of SIP platforms.
Who is affected
Only SIP trunking customers whose trunk is configured with an FQDN destination. Trunks configured by IP address, Microsoft Teams and other LoopUp services are not affected.
Action required
Most SBCs accept requests addressed to their own FQDN without any changes. If your SBC is configured to accept requests addressed only to its IP address, please confirm it will also accept its FQDN. If you have any questions, contact servicedesk@loopup.com before the maintenance window.
Expected impact
No service interruption is expected. Service will be validated during the window, with a rollback plan in place.
We’ll post an update here once the maintenance is complete.
Posted on Oct 12, 2026 - 08:59 UTC
What’s changing
For SIP trunks where our platform reaches your SBC by a fully qualified domain name (FQDN), SIP requests sent from LoopUp to your SBC will carry your FQDN in the Request-URI and To header, instead of the resolved IP address. This change improves interoperability with a wider range of SIP platforms.
Who is affected
Only SIP trunking customers whose trunk is configured with an FQDN destination. Trunks configured by IP address, Microsoft Teams and other LoopUp services are not affected.
Action required
Most SBCs accept requests addressed to their own FQDN without any changes. If your SBC is configured to accept requests addressed only to its IP address, please confirm it will also accept its FQDN. If you have any questions, contact servicedesk@loopup.com before the maintenance window.
Expected impact
No service interruption is expected. Service will be validated during the window, with a rollback plan in place.
We’ll post an update here once the maintenance is complete.
Posted on Oct 12, 2026 - 08:59 UTC