Previous incidents

13:15--Update--
Microsoft acknowledge the incident and create a Service Health dossier with ID TM445531. With this information we will close the incident on our side.

12:51 --Monitoring--

Today at 12:22 CEST we received multiple errors from multiple Voice365 SBCs affecting multiple customers.
The errors show that Microsoft Teams Direct Routing endpoints were not responding, also the failover Microsoft Endpoint showed the same behaviour which caused inbound issue.

We see the Mi...

We are currently investigating an issue with outbound calls: calls are being dropped or no audio after connecting.

UPDATE 13:45: The issue has been resolved. We are waiting for more details from our engineers what has caused this issue.

UPDATE 14:20: Outage details: Due to an update in our MySQL procedures concerning CallerID authorization, our REG systems were unable to run authorization procedures for CallerID. This resulted in an incorrect CallerID to be sent to our CORE ...

Customer Portal went down because of an upgrade.

In the periods between 12:20 to 12:23 and 12:31 to 12:37 we had a connectivity issue towards our operators. Both incoming and outgoing calls were affected.

UPDATE 22/09:
We have investigated the issue and came to the conclusion the issue was caused most likely by daily maintenance routines, which has triggered an unexpected lock on our databases.
We will try to reproduce the issue in a non-productional environment to find a solution for it.
For now the specific maintenance routines hav...

We have closed this incident and we will reschedule the maintenance for a later moment.