Updates

Fault 14 December 2017

This morning customers intermittently could not receive calls. We were first made aware of the issue at 9.35 AM. Service was completely restored at 10.05 AM

  • Status: Service is restored.
  • Scale: All customers, inbound only.
  • Duration: 30 minutes
  • Cause: Human error. Test code for a future upgrade of our platform was accidentally made live.

Fault 26 October 2017

Between 11.12AM and 12.07PM we experienced a full network outage. All customers experienced problems with inbound and outbound calls.

Your phones will re-register automatically. If problems persist, please reboot the affected phone.

  • Status: Service is restored.
  • Scale: All customers.
  • Duration: 55 minutes
  • Cause: The database link between our data centres dropped briefly and caused all active calls to drop. All calls were automatically re-established, which caused an overload on the servers and in turn, caused the servers to reboot.

Fault 1 February 2017

Between 10.45AM and 10.47AM we were targetted by a DDOS attack. Customers experienced problems with inbound and outbound calls, including dropped calls.

Your phones will re-register automatically. If problems persist, please reboot the affected phone.

  • Status: Service is restored.
  • Scale: All customers.
  • Duration: 7 minutes
  • Cause: DDOS Attack

Fault 9 November 2016

This morning we experienced an outage at one of our upstream providers. Some subscribers (about 40%) were not able to receive calls. Most subscribers were not able to call national numbers. The outage started at 0.09AM.
Outbound calls were restored at 9.17AM
Inbound calls were restored at 9.24AM

  • Status: Resolved.
  • Scale: 40-99% of customers.
  • Duration: 9 hours.
  • Cause: The fault was due to our upstream provider not accepting inbound calls for some national numbers, nor accepting outbound calls to national numbers.
  • Future measure: Expand monitoring tools to monitor call volume and respond sooner.

 

Fault 1 April 2016

This morning we experienced an outage at one of our upstream providers. Our customers with South African phone numbers were not able to receive calls, nor call to numbers in South Africa. The outage started at 5.07AM and was resolved at 9.04AM.

  • Status: Resolved.
  • Scale: 90% of customers.
  • Duration: 4 hours.
  • Cause: The fault was due to our upstream provider not accepting inbound calls national numbers, nor excepting outbound calls to national numbers.

Fault 1 October 2015

On the 1st of October, some of our clients were unable to receive calls. We received the first report of the fault on 9h40. The issue was resolved at 10h31.

  • Status: Resolved.
  • Scale: Approximately 30 customers.
  • Duration: 59 minutes.
  • Cause: The fault was due to our upstream provider not accepting calls to our numbers. As a result, the calls to these numbers were not forwarded to our network and therefore could not be terminated.
  • Solution: Upstream provider updated their database.

Fault 17 March 2015

On the 17th of March, an internet link with one of our upstream providers failed. Between 13h10 and 15h30 some customers could not receive calls. We were first aware of the failure at 14h27.

  • Status: Solved.
  • Scale: Approximately 30 customers.
  • Duration: 2 hours and 20 minutes.
  • Cause: Due to a failed connection with one of our ISP’s, connection to an upstream provider was lost.
  • Solution: Rerouted traffic via other ISP.
  • Future measure: Expand monitoring tools to monitor link and respond sooner.