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 - SIP Trunking - EMEA Aug 13, 2026 00:00-01:00 UTC
We will be performing scheduled maintenance on our SIP trunking platform in EMEA on Thursday, 13 August, from 00:00 - 01:00 UTC.
This work has already been communicated to affected customers and includes enhancements to improve service reliability and performance.
Existing calls will not be affected. During the maintenance window, there may be a brief delay when establishing new sessions while DNS updates propagate. The maintenance has been carefully planned to minimise impact.
We will provide an update once the maintenance is complete. If you experience any issues during or after this period, please contact our support team at servicedesk@loopup.com.
Posted on Jul 23, 2026 - 13:26 UTC
This work has already been communicated to affected customers and includes enhancements to improve service reliability and performance.
Existing calls will not be affected. During the maintenance window, there may be a brief delay when establishing new sessions while DNS updates propagate. The maintenance has been carefully planned to minimise impact.
We will provide an update once the maintenance is complete. If you experience any issues during or after this period, please contact our support team at servicedesk@loopup.com.
Posted on Jul 23, 2026 - 13:26 UTC
P-Asserted-Identity Enforcement on SIP Trunking Aug 14, 2026 00:00-01:00 UTC
Over the next several weeks, LoopUp will be rolling out changes across its network to enforce the presence of the P-Asserted-Identity (PAI) header in all SIP INVITE messages originating from SIP trunking customers.
What's changing:
In accordance with RFC 3325, LoopUp's network will begin strictly validating that all INVITE requests include a valid P-Asserted-Identity header. INVITEs that do not include this header will be rejected with:
SIP/2.0 403 Forbidden
Reason: P-Asserted-Identity header not present
Why this is happening:
This change is required for security and regulatory compliance. PAI is used to assert the verified identity of the calling party within a trusted network boundary. Enforcing its inclusion ensures that all calls traversing LoopUp's network carry authenticated originating identity, supporting fraud prevention and telco regulations.
Action required:
As per previous communication, if you operate a SIP trunk connected to LoopUp, please ensure your equipment is configured to include a P-Asserted-Identity header in all outbound INVITE requests. Please refer to your SBC or PBX vendor documentation for configuration guidance.
If you have questions or need assistance validating your configuration ahead of the change, please contact servicedesk@loopup.com
Posted on Jul 23, 2026 - 07:45 UTC
What's changing:
In accordance with RFC 3325, LoopUp's network will begin strictly validating that all INVITE requests include a valid P-Asserted-Identity header. INVITEs that do not include this header will be rejected with:
SIP/2.0 403 Forbidden
Reason: P-Asserted-Identity header not present
Why this is happening:
This change is required for security and regulatory compliance. PAI is used to assert the verified identity of the calling party within a trusted network boundary. Enforcing its inclusion ensures that all calls traversing LoopUp's network carry authenticated originating identity, supporting fraud prevention and telco regulations.
Action required:
As per previous communication, if you operate a SIP trunk connected to LoopUp, please ensure your equipment is configured to include a P-Asserted-Identity header in all outbound INVITE requests. Please refer to your SBC or PBX vendor documentation for configuration guidance.
If you have questions or need assistance validating your configuration ahead of the change, please contact servicedesk@loopup.com
Posted on Jul 23, 2026 - 07:45 UTC