Blocked Drains in Peebles
Peebles has an unusual drainage challenge: most of the town runs on combined sewerage, where foul and surface water share the same pipe. When heavy rainfall occurs, combined sewers in Peebles back up, causing blocked drains and flooding in Victorian and Edwardian homes (28% of the stock in postcodes EH45–EH46). Combined with root ingress in older clay pipes and grease buildup in terraced Peebles properties, blockages are both common and complex. Understanding your Peebles property's sewer type and age is essential for effective unblocking.
Blocked drains in Peebles are often caused by combined sewer surcharge during heavy rainfall—the system backs up into Victorian and Edwardian homes. Root ingress in clay pipes and grease accumulation worsen blockages. CCTV inspection reveals the cause and guides repair in Peebles properties.
Drainage in Peebles — what local engineers know
Peebles's combined sewer network is maintained by Scottish Water and overseen by Scottish Borders Council. The system merges foul and surface water in central and older Peebles areas (particularly EH45 and EH46), creating a surcharge risk during heavy rainfall—the Scottish Borders sees significant annual precipitation. This forces water back through Peebles drains into older properties first, typically Victorian and Edwardian homes where clay pipes have degraded. Root ingress is also common in Peebles because mature trees line many streets; tree roots penetrate and collapse old clay and concrete pipes. Drainage problems in Peebles often require CCTV inspection to diagnose the exact cause.
- Soft water supply reduces limescale, but slightly acidic pH can accelerate corrosion of copper fittings and lead joints in older Peebles properties
- Combined sewerage infrastructure — common in older parts of Peebles — means foul and surface water share the same pipe, increasing surcharge risk during heavy rainfall
- Moderate flood risk in parts of Peebles — drainage systems near low-lying areas can surcharge after prolonged rain, and sump pump maintenance is advisable
- With 28% of properties built before 1920, salt-glazed clay drainage and lead-solder copper pipework are common — pipe collapse, root ingress and joint failure are recurring call-out drivers.
What happens when you call us in Peebles
- 1 Immediate dispatch. We find the nearest available engineer covering EH45/EH46 and confirm the ETA before the call ends.
- 2 On-site diagnosis — no guessing. The engineer inspects using professional-grade equipment including CCTV where needed and quotes a fixed price before work starts.
- 3 Job complete, report issued. You receive a written completion report. All work is guaranteed — same fault returns within the guarantee period, we come back free.
Who's responsible for drains in Peebles?
In Peebles, responsibility for a blocked or damaged drain depends on where the fault sits. As a homeowner you are responsible for the drains within your property boundary that serve only your home. Since the 2011 private sewer transfer, Scottish Water is responsible for shared sewers and lateral drains beyond your boundary — even where they run under private land. Road gullies and highway drainage are maintained by Scottish Borders.
This matters because it determines who pays. If our engineer's CCTV inspection shows the fault is in a shared sewer, we'll tell you — and you can report it to Scottish Water rather than paying for the repair yourself. The combined sewer layout that dominates Peebles affects where these boundaries typically fall, and our local engineers know the EH45, EH46, EH47 networks well enough to identify ownership quickly.
Blocked Drains prices in Peebles
Every Peebles job is quoted as a fixed price before work starts — what we quote is what you pay, with no call-out fee for providing the quote. The final price depends on access (an external inspection chamber is quicker than internal-only access), the pipe material and condition , and how established the blockage or fault is. Request your free quote and we'll confirm the price and your engineer's ETA in the callback.
