We are currently investigating a DNS issue across our network which will be causing a wide range of not found errors for all services.  We are working as quickly as possible to resolve this and will update customers as soon as possible.

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.

Related Posts

• No Related Post