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.

Uptime over the past 90 days. View historical uptime.
Cloud Telephony Operational
90 days ago
100.0 % uptime
Today
Admin Portal Operational
90 days ago
100.0 % uptime
Today
North America Operational
90 days ago
100.0 % uptime
Today
Latin America Operational
90 days ago
100.0 % uptime
Today
Europe, the Middle East and Africa Operational
90 days ago
100.0 % uptime
Today
South Africa Operational
90 days ago
100.0 % uptime
Today
Asia-Pacific Operational
90 days ago
100.0 % uptime
Today
Oceania Operational
90 days ago
100.0 % uptime
Today
India Operational
90 days ago
100.0 % uptime
Today
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.

No incidents or maintenance related to this downtime.

Sep 4, 2026

No incidents reported today.

Sep 3, 2026

No incidents reported.

Sep 2, 2026

No incidents reported.

Sep 1, 2026

No incidents reported.

Aug 31, 2026

No incidents reported.

Aug 30, 2026

No incidents reported.

Aug 29, 2026

No incidents reported.

Aug 28, 2026

No incidents reported.

Aug 27, 2026

No incidents reported.

Aug 26, 2026

No incidents reported.

Aug 25, 2026

Call completion issues to Vivo network numbers in Brazil
Resolved - 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.
Aug 25, 08:17 UTC
P-Asserted-Identity Enforcement on SIP Trunking
Completed - The scheduled maintenance has been completed and PAI is now enforced globally.

Thank you for your cooperation in complying with this regulatory requirement.

If you have any further questions, please contact servicedesk@loopup.com
Aug 25, 08:02 UTC
Scheduled - 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
Jul 23, 07:45 UTC

Aug 24, 2026

No incidents reported.

Aug 23, 2026

No incidents reported.

Aug 22, 2026

Cloud Telephony – Inbound Call Routing – Partial Service Degradation
Resolved - The issue impacting inbound calls has now been resolved. Callers should no longer be routed to the 'Welcome to LoopUp' prompt and calls are connecting to their intended destinations as normal.

We will follow up directly with affected customers to explain what happened and outline the steps we are taking to prevent a recurrence.

We apologise for any inconvenience caused. Our Service Desk Team remain available 24/7 at servicedesk@loopup.com.
Aug 22, 12:26 UTC
Identified - We have identified an issue impacting inbound calls. Some callers may connect to our ‘Welcome to LoopUp’ prompt instead of reaching the intended call destination. We are aware of the issue and are working on it urgently.

Please know that our teams are working hard to get everything up and running. We will provide more information as soon as it is available.

We're sorry to be holding you up today. Our Service Desk Team are available 24/7 at servicedesk@loopup.com.
Aug 21, 21:57 UTC

Aug 21, 2026

← Incident History Powered by Atlassian Statuspage