Thursday 01 November 2012, 13:44
We are working on locating the error and making sure it will not happen again soon
We suspect the error was at K-Net somewhere, since the WiFi did work properly and the “old” system did not have any downtime.