Hosepipe ban

Following months of unprecedented dry weather, repeated heatwaves and forecasts for further hot conditions, we have introduced a temporary hosepipe ban.

Hosepipe ban is now in place

Updated: 18 August 2026

Following a period of record breaking heatwaves and lower-than-average rainfall, our water supply network is under increasing pressure.

We've seen record levels of demand for water and with more hot weather to come and no significant rain forecast, we've made the difficult decision to introduce a hosepipe ban.

The hosepipe ban started on Tuesday 18 August at 00:01hrs. Customers must not use a hosepipe for activities covered by the restrictions.

Frequently asked questions

We have answered a range of questions about the hosepipe ban in our FAQ Hub.

Hosepipe ban exemptions

Check if you are exempt from the hosepipe ban.

Check if it applies to your area

The ban applies to all customers in our region who we supply with water.

Why a ban is needed

A hosepipe ban, also known as a Temporary Use Ban (TUB), restricts the use of hosepipes for certain non-essential activities to help conserve water during periods of drought or water shortage.

We have introduced one because water resources are under significant pressure due to prolonged dry weather and demand throughout the summer has been significantly higher than normal.

It’s been 50 years since water restrictions were last needed in the Wessex Water region, but they are necessary to help protect water supplies, safeguard the environment and ensure enough water is available for essential use by customers and businesses.

Who is affected

The hosepipe ban applies to all customers in our region who we supply with water.

Customers with a valid exemption are not affected by the ban.

Check if you are affected by the hosepipe ban

Water use restrictions

You must avoid using a hosepipe for:

  • watering a garden
  • cleaning a private motor vehicle
  • watering plants on domestic or other non-commercial premises
  • filling or maintaining a domestic swimming pool or paddling pool
  • drawing water for domestic recreational use
  • filling or maintaining an ornamental fountain
  • cleaning walls or windows of domestic premises
  • cleaning paths or patios
  • cleaning other artificial outdoor surfaces

For more information about the restrictions, please see our FAQs.

What you can still do

This ban does not impact everyday essential household use, such as showering and washing.

You can also still:

  • water plants with a watering can
  • use water from your water butt
  • fill up a bucket for car washing.

What we're doing

We know we have a part to play as well. That’s why we are working hard to ensure there is enough water for customers and the environment.

All available resources are going into fixing leaks. In July alone, we have increased the number of leaks we have found and fixed by a third.

We have also been using our one-of-a-kind water supply grid to redistribute water from areas where there is a surplus to where it is needed most.

How to save water

Small changes make a big impact.

You can help to save water and reduce the pressure on our network by:

  • taking shorter showers
  • only running washing machines and dishwashers with full loads
  • reusing water from washing up to water your plants
  • letting your lawn go brown
  • reporting leaks on our network promptly.

If you suspect water misuse

Stop and think: Could the person you're reporting have an exemption? Please refer to our list of exemptions if you're not sure.

Legal notice document download

For more information about the ban, please see our legal notice.

  • [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