Service history
Published incidents, including active and resolved events.
An issue has been detected on the front-end server, affecting the availability or proper operation of the user interface.
The APIs are operational, and no impact has been detected on any other connected systems or services.
Impact:
The issue is limited to the front-end component. API services and all other systems are operating normally.
Current status:
The issue has been resolved and the front-end service is now fully operational.
We have received reports indicating problems with inbound calls on certain registration SIP Trunks.
Our team is actively investigating the matter.
We have identified and resolved an issue that prevented Call Detail Records (CDRs) from being uploaded to the SFTP server.
This issue affected uploads from August 24 through September 1. We have successfully generated all missing files and uploaded them to the SFTP server. No data was lost.
We apologize for any inconvenience this delay may have caused.
At 12:30 we noticed that outbound traffic dropped.
Inbound traffic remains unaffected.
After analysing the issue we have identified the issue at 14:03 and implemented a fix at 14:15 which restored normal traffic flow.
A Cloudflare outage is affecting our web services making them unreachable.
Cloudflare has investigated the issue and is deploying a fix, recovery is underway.
More info on their statuspage.
We will advise once the issue has been resolved.
Services have started to come back online.
We are still keeping the situation monitored.
Services have been online for almost two hours.
We consider the outage resolved but will keep monitoring.
One of our transit providers had an outage that caused some reachability issues for a small portion of customers.
We immediately disconnected the affected transit provider and reachability went back to normal.
Call routing for all DSS services was broken this morning at 7:02 AM for SIP Trunks and Webex Calling.
We have since identified the issue and have deployed a fix.
As of 9:05 AM calls are being correctly routed but we are keeping the services monitored.
Service | Impact |
|---|---|
DSS | MAJOR |
Product | Impact |
|---|---|
SIP Trunk | MAJOR |
Webex Calling | PARTIAL |
08/01/2025 07:02 CET
08/01/2025 09:05 CET
Calls were not being correctly routed by the platform causing errors for both inbound and outbound calls.
The cause was a bug in a specific software version of the RTP Server that caused an OOM error.
Restarted the affected services
Update the RTP Server to permanently fix the issue
Improve our alerting system so that in the future we can take proactive action in similar cases
Change SIP Server responses to SIP OPTION so that in similar cases customer endpoints will be able to correctly fail-over to the secondary node