Our VoIP Centrex server Lon-PBX-1 has restarted due to a back-end storage timeout, customer calls will have temporarily been unavailable for customers using this server. We apologise for any inconvenience caused. Our server team have restarted the service before our backup server came into operation.
We would recommend any customers still seeing issues restart their VoIP phone equipment and contact our support team if the problem cannot be resolved.
Update: The problem occurred between 13:26 and lasted for about a minute until the server was restarted.
We have identified a mail delivery issue which will affect customers on our new mail servers, Yosemite and Denali who use Procmail. All other customers will not be affected. Email will be delivered to these mailboxes as soon as the problem has been cleared. Apologies for any inconvenience this is likely to cause. Updates will be posted via this web-site.
Update 15:06 This issue has now been resolved and assigned an internal issue number of 1772 to make changes to future servers in our new mail storage cluster. The problem was caused by recently security updates to our Procmail back-end.
A probem has been found on our v-mail-file-3 platform which was no longer acceping email from approximately 04:30 until 07:25, this problem has been cleared and new email is now being delivered to inboxes. No email will have been lost, as mail had been queued on our inbound mail servers during this time.
We are currently investigating a configuration problem with our legacy FreeBSD cluster with customers stored on our /home6 mount-point. We should be able to resolve this shortly and apologise for any inconvenience caused. This issue started at 17:00.
Update 19:00: Our server team have brought the majority of affected sites back online and will be continuing to look into the issue until we are satisfied it is resolved. We have identified a problem with some of our customer site provisioning logic and are working to improve this and make it more robust.
Update 10:00 An issue has been brought to our attention on the PHP 5.2 cluster involving some of the servers which had created incorrect site provisioning. This has now been resolved by our server team.
We have restarted the conference room server ‘v-confroom-1′ due to an unusually high utilisation rate and bad call quality which was being experiencied by customers.
Our server team have restarted a critical legacy customer storage server which was not responding.
Customers will have seen unresponsiveness over several dependent services such as web sites and shell access as a result. We apologise for this and are continuing to migrate away from this and on to our new HP/Lefthand platform.
We are currently investigating an issue which has made some of the Gradwell website unavailable.
Currently the code that serves https://www.gradwell.net/myaccount is experiencing a technical issue , this means that customer account information is currently unavailable.
A server engineer is currently investigating this issue and further updates will be posted.
Update 21:00: We have now reverted an incorrect change which was inadvertently made to the site and customer logins have been working correctly for the past half hour. We apologise for any inconvenience caused.
Our DSL Provider has issued a notification that they are currently seeing resilience issues on their core network, this is affecting BT Datastream networks only connected between their Reading Harbour POP and Bristol POP
We are unable to identify which customers are affected by this issue as this data is not available, current issues will be reduced speed and packet loss.
A fibre break near Woking has been identified as the cause of this issue and engineering teams are currently enroute to site to repair the damage.
UPDATE 12:09 - Fibre rings have now been respliced and our carrier has reported that circuits are now stable
We are seeing some problems with our speech to text service.
Some users have been seeing incorrectly converted or garbled email notifications, our engineering team are working on implementing a fix for this and hope to resume normal service as soon as possible.
Our apologies for any problems this is causing
Update: This issue was resolved by 27th May and was caused by our supplier unexpectedly changing the format of emails sent inbound to our system. We have altered our logic to support both formats in case of the unlikely event of this happening again.
We have identified a potential security issue with our pop3ftp service and have temporarily withdrawn the service for further investigation. Apologies for any inconvenience this may cause. If you require any assistance with anything related to pop3ftp, please contact our customer services team who will be happy to assist.
Update 16:34: We have now restored the POP3ftp service
