The platform has been restored to its original state. All services are up and running. We will continue to closely monitor the platform.
Posted Jan 23, 2020 - 17:05 CET
In order to resolve the issue, we need to perform some emergency maintenance. This maintenance will potentially cause a series of short service interruptions.
Gateway 2 (18.104.22.168) will go offline, please switch to Gateway 1 (22.214.171.124).
Start: 12:30 UTC Duration: Approx. 1 hour
Next update: 13:00 UTC
Posted Jan 23, 2020 - 13:27 CET
We managed to get call traffic flowing again, but reliability cannot be guaranteed at the moment.
Posted Jan 23, 2020 - 09:01 CET
More research into the effects now shows that most of our customers will not be able to call via this platform. The cause has been found and we are working on a resolution.
Posted Jan 23, 2020 - 08:51 CET
It seems like something is wrong with the hardware located in Johannesburg, ZA, causing some Virtual Machines that are part of the Voice Outbound Platform to have stopped. These VMs are running in groups, split over separate hardware, so it's unclear whether this problem actually affects traffic. First tests allow us to place calls on the platform, but customers might experience problems. We are investigating both the cause and the effects.
Posted Jan 23, 2020 - 08:41 CET
This incident affected: Voice (Outbound Gateway Johannesburg (ZA)).