(24) (5) (44) (45) (35) (7) (6) (2) (58)We are currently investigating an issue on our inbound sip routers which will be stopping inbound calls to our network. We are working with the highest priority to clear the issue and we apologise for any inconvenience caused.
UPDATE: This issue has now been cleared by our system admins.
We are currently seeing issues with two of our PBX servers, lon-pbx-5 and lon-pbx-2. Our system admins are looking into these problems now.
We apologise for any inconvenience caused.
Update: This issue has now been cleared by our system admins and we will continue to monitor the situation.
Users may be seeing some issues with calls on lon-pbx-7.
Our server admin team are restarting this server now and we will update once it is stable.
We apologise for any problems this is causing
**Update**
This issue was cleared at 15:25, we have been monitoring lon-pbx-7 since and it is now reporting as stable.
If you are still seeing any problems, please contact support.
We have restarted the VoIP Centrex Server lon-pbx-11 due to load-related issues which the server was experiencing, which woul have resulted in extended call setup times and difficultly transfering calls or registering extensions. We apologise for any inconvenience caused.
We are currently experiencing an intermittent issue with one of our back-end storage servers which handles some of our internal scheduled tasks. This server is being checked at the moment and we have been alerted to a possibility that this is causing legacy FreeBSD-hosted sites to not respond in a timely manner. We are working to bring this server back up as quickly as possible and move the data to an alternative server.
Update 21:48: We have brought this server back online and are continuing to migrate all data from it, as this serever remains at risk. Our internal monitoring systems show that lon-web-1 and lon-web-2 have now recovered.
Update: June 30th 23:00: We have now migrated enough from our legacy system ‘Azure’, to mark our new HP/Lefthand copy active and do not expect any more outages with Azure to to affect back-end scripts from running and we therefore consider this issue closed.
Since 10:50 One of our legacy ESX servers has experienced an issue communicating with our legacy storage servers which has stopped several servers operating correctly. The only remaining server experiencing an issue is v-mail-file-10, which holds 12 mailboxes which are the only mailboxes not yet migrated on to our HP/Lefthand storage. This server has been brought back up on an alternative host and is currently undergoing a file-system test before being brought back online. We apologise for any inconvenience caused.
Update: This issue was fully resolved at 12:30
18:50 We are currently experiencing an issue with one of the servers which provides our NNTP/usenet feeds and our server team is investigating.
Update: This issue has been resolved since 21:30 hours.
Update: Apologies for some additional DNS resolution issues which were encountered after this this point which delayed resolution of the service. The service was restored by 22:50.
Our VoIP Centrex server lon-pbx-12 has just been restarted due to excessive load preventing the server for responding in a timely manner. This issue is being investigated internally and we apologise for any inconvenience caused.
One of our PBXs - lon-pbx-11.gradwell.net swapped to its backup server just after 12:00 .
We have now restarted lon-pbx-11 and it has now taken over from the backup and is passing calls correctly. We apologise for any issues you may have experienced whilst this changeover took place.
If you are experiencing any problems after this changeover, please reboot your VoIP device to enable it to re-register.
We are currently investigating an inbound mail delay to hosted domains and email forwarding. This issue has been narrowed down to a firewall configuration issue and is being worked on by our on-call server engineers. We apologise for any inconvenience caused.
Update 23:30: The root cause of this issue has now been corrected and mail queues are being cleared down, which is likely to last around half an hour.
Update 00:47: An additional issue has been found with delivery to local mailboxes from the affected inbound servers and has now been corrected.
Update: This issue was resolved by 02:00.
