Order posts by limited to posts

5 Aug
Details
5 May 22:22:42

TalkTalk is performing essential maintenance on its internal infrastructure. This work will happen in the early hours of the 8th May 2015. This work will mean that services may be lost for up to 1 hour between midnight and 6am. This is likely to affect the following exchanges:

  • FLAX BOURTON
  • REDCLIFFE
  • WEDMORE
  • Yatton
  • Didcot
  • CHURCHDOWN
  • Cheltenham
  • SHRIVENHAM
  • STRATTON ST MARGARET
  • Swindon
  • Blunsdon
  • Cirencester
  • CRICKLADE
  • HAYDON WICK
  • PURTON
  • BATHEASTON
  • BOX
  • BRADENSTOKE
  • Chippenham
  • CORSHAM
  • CHURCHILL
  • Clevedon
  • NAILSEA
  • WRINGTON
  • LONG ASHTON
  • PILL
  • Brimscombe
  • Dursley
  • NAILSWORTH
  • TETBURY
  • Calne
  • Devizes
  • HAWTHORN
  • Melksham
  • NORTH TROWBRIDGE
  • BANWELL
  • BLEADON
  • WINSCOMBE
  • Worle
  • Weston Super Mare
  • ABSON
  • Downend
  • FISHPONDS
  • SALTFORD
  • CHEW MAGNA
  • Midsomer Norton
  • Radstock
  • STRATTON-ON-FOSSE
  • TEMPLE CLOUD
  • TIMSBURY
  • STOKE BISHOP
  • West
  • Frome
  • MELLS
  • WARMINSTER
  • BRADFORD-ON-AVON
  • LIMPLEY STOKE
  • Trowbridge
  • Westbury
  • ALMONDSBURY
  • FILTON
  • HENBURY
  • AVONMOUTH
  • PILNING
  • Portishead
  • BEDMINSTER
  • BISHOPSWORTH
  • BITTON
  • KEYNSHAM
  • Kingswood
  • CHIPPING SODBURY
  • FALFIELD
  • WINTERBOURNE
  • WOTTON UNDER EDGE
  • FAIRFORD
  • LECHLADE
  • MALMESBURY
  • SOUTH CERNEY
  • TOOTHILL
  • WOOTTON BASSETT
  • COMBE DOWN
  • Kingsmead
  • Bristol North
  • WESTBURY-ON-TRYM
  • EASTON
  • EASTVILLE
  • South
  • WHITCHURCH
  • LAVINGTON
  • MARLBOROUGH
  • PEWSEY
  • WROUGHTON
  • WANBOROUGH
  • LULSGATE
  • Glastonbury
  • OAKHILL
  • Wells
  • BERKELEY
  • THORNBURY
We apologise for any inconvenience that these works may cause you
Planned start 5 Aug by TalkTalk

Today 10:53:48
Details
Today 10:12:22
We have been encountering issues with LINX which result in some routes being "Black-holed" (i.e. going nowhere).

The system normally handles this without any problem, identifying an infeasible route and removing from the routing table to allow alternative routes a chance. However we have identified an edge case where this does not happen.

We plan to do a router upgrade today, as this issue is causing customers problems at present. This is one router and should be pretty seamless in that routing should go via other routers whilst it happens.

However, there is a small risk of some routing blips during the process.

Resolution Upgrade completed
Started Today 10:00:00
Closed Today 10:53:48
Expected close Today 17:00:00