We have corrected the problem and reported this fault back to the engineers who set up these machines.  We apologise for any inconvenience caused.

VoIP Customers may experience DNS related issues if phones are configured to use 193.111.200.91 and 193.111.200.191 as their DNS Servers. DSL Customers may experience an outage where web sites cannot be reached.

Our server admin team are working on this now and will try to keep disruption to a minimum. Our apologies for any problems experienced because of this

Update 12:51: Our DNS resolvers are now back online and working correctly.  This issue will have resulted in a problem setting up calls.  We are currently bringing back other services such as control panels are working as quickly as possible to restore any affected services.

Update 13:16: Control panel access has been restored.

If you are affected by this, we would ask you to not make any changes until we have resolved this as any change made may possibly corrupt the zone file.We will post an update here as soon as possible.

We apologise for any problems this causes you.

****Update 10:26****

This issue is now totally cleared. If you are seeing any oddities or missing any zone files, please raise an incident with support and we will investigate and restore.

Our server admin team are working on this now and we will post an update here as soon as possible. Our secondary nameservers are functioning without issue.

We apologise for any problems this is causing

***Update - 15:38***

ns0 is now back up and running and resolving correctly.

Update 18:30 - This issue has now been resolved and an internal issue raised to ensure this does not occur again.  We have identified a single point of failure in our zone configuration and our server team will be working to provision backup.

Update 18:55 - One of our inbound telcos for ported numbers have cached a copy of our resource records which is incomplete.  This is causing inbound calls from this provider towards our network to fail.  We are awaiting an emergency call out from their out of hours engineers to resolve this and will update customers as soon as we have any further news.

Update: 19:30 - A technican at our inbound telco for ported numbers has restarted their DNS cluster to removed the affected DNS zone.  This has resolved the issue for inbound numbers failing.

We apologise for the extended nature of this problem, which is due in part to DNS caches not all adhering to the maximum lifespan we would like to give them.  This is a problem built into the internet by design, however, we should not have released the non-complete zone which triggered this to happen.  As a result, we will be changing the way our DNS servers are configured to try to prevent this issue from happening in the future.

Update 12:35
We have restored database connectivity.  This issue was caused by a DNS issue internally which is currently being investigated in more details to ensure that more redundancy is added to ensure this does not happen again.

We are still seeing issues with whitelabel VoIP partners’ control panels which we are investigating currently.

Update 13:45
Our partner login areas are now working normally again, this issue is related to our database, which due to being unavailable had a backlog of work, which has now cleared.  We apologise for the inconvenience this will have caused you.

Late on Tuesday evening, we will be carrying out some essential maintenance to our hosting service.

• New version of the Hosting Control Panel, adding the following features:
  • PHP 5.2 trial cluster support
  • Display which file server mailboxes are stored on
• DNS Server configuration update, to disable zone transfers for customers who want this disabled