Checking for leaks

If you think you could have a leak on your property, see the common signs and carry out one of our simple tests to check.

Signs you may have a leak

You may have a leak if you notice:

  • an unexplained increase in your bill
  • a big drop in water pressure
  • areas of lush vegetation in your garden
  • damp patches on the ground
  • a hissing or knocking noise near your internal stop tap
  • a continuous flow from your toilet cistern.

Perform a leak test

If you have a meter

If you have a meter, you can use it to check if water is being used when you’re not using any.

Metered leak test

If you don’t have a meter

If you don’t have a meter, you can check for a hissing or knocking noise at your internal stop tap.

Unmetered leak test

How to check for toilet leaks

Water trickling down the back of the toilet pan can be silent, making toilet leaks hard to spot.

You can perform this simple test to find out if you have a leaky loo.

Toilet leak test
Image of a leaky loo strip being applied to a toilet rim

[Component Error] SsoSilent

System.NullReferenceException: Object reference not set to an instance of an object. at Ytl.Components.Auth.ViewComponents.SsoSilentViewComponent.InvokeAsync() in /home/vsts/work/1/s/src/Ytl.Components/Auth/ViewComponents/SsoSilentViewComponent.cs:line 55 at Microsoft.AspNetCore.Mvc.ViewComponents.DefaultViewComponentInvoker.InvokeAsyncCore(ObjectMethodExecutor executor, Object component, ViewComponentContext context) at Microsoft.AspNetCore.Mvc.ViewComponents.DefaultViewComponentInvoker.InvokeAsync(ViewComponentContext context) at Microsoft.AspNetCore.Mvc.ViewComponents.DefaultViewComponentInvoker.InvokeAsync(ViewComponentContext context) at Microsoft.AspNetCore.Mvc.ViewComponents.DefaultViewComponentHelper.InvokeCoreAsync(ViewComponentDescriptor descriptor, Object arguments) at AspNetCoreGeneratedDocument.Views_Partials_blocklist_external.ExecuteAsync() in /home/vsts/work/1/s/src/Ytl.Website/Views/Partials/blocklist/external.cshtml:line 16