pascom ONE had 12 outages in the last 2 years totaling 3956h 38m of downtime — averaging 0.5 incidents per month.
There were 12 pascom ONE outages since August 12, 2025 totaling 3956h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.
Due to API errors on the backend transcriptions are failing ATM.
The transcription backend API responds successfull again, issue solved.
One proxy server died, assigned endpoints will have dropped calls, some clients will also start to reconnect on healthy proxy. Should recover soon.
Services on that proxy recovered, all operational again. Assuming HW failure at the moment, will start investigating on the cause now to improve stability.
Investigating, my.pascom.net is currently not available.
my.pascom.net is available agian, outage was due to a temporal internal DNS failure.
We experienced a short interruption of some endpoint and some third party trunk registrations, most likely due to some network problem somewhere. It disappeared without manual interaction within five minutes. Due to retry timeouts, clients or trunks may have been unregistered a bit longer.
Resolved
Some hardware endpoints are losing their SIP registrations.
The issue was caused by a load balancer configuration change that was supposed to be invisible. Only a small number of pbxes were affected. After rollback of the change, the service has been restored for all customers.
We see some SBCs (handling VoIP Registration and calls) dropping calls, investigating.
Services recovered, still investigating what caused the connection drops on our SBCs
Some stuck TCP Connection caused high load over all SBCs simultaneously. Will continue to investigate and taking countermeasures accordingly. Closing this issue for now since all service are operating.
my.pascom.net is currently not available due to a host outage. Service should recover soon.
Service up and running again.
Today’s WhatsApp messages can not be delivered due to a broken connection. A connection reset has to be done tonigh between 22-23 pm. We expect messaged to be delivered afterwards (so they should not be lost). We are also working on a more reliable connection and are sorry for the inconvenience.
Connection restored.
We see high latency on a lot of requests.
We see latency recovering and found the cause. We will update the component that leads to this slow experience tonight to fully solve it, because it will cause a short reconnect of the clients. Due to less load on the afternoon we do not expect that latency becomes that high again.
We se some connection drops, investigating.
Found a service crash causing the connection drops. Service is healthy again and improvements to prevent future crashes on that service are planned.