Hey @catspyjamas. This is where some more user friendly information would have helped. Due to the declining nature and service requirements of DSL we get Chorus to aggregate these connections to MDR. The DSL handover was directly impacted by this item of planned work.

For general understanding Voyager peer with local peering exchanges in Sydney, Auckland, Wellington and Christchurch. Within cities these are distributed over various PoPs and devices to add resilency to our peering. Where we do not have direct peering either to peering exchanges or with 3rd party networks (think Amazon, Facebook etc.) we use Global Gateway and Vocus NZ (now 2degrees) for IP Transit capacity. These are currently taken out of MDR and QST, once again on diverse edge routers. Our broadband services are aggregated into Christchurch, Wellington and Auckland, where handovers to the various providers are once again at diverse locations in order to minimise impact of any one maintenance. The principles of the engineering team, and by extension, the Voyager network, is diversity, redundancy, speed, and reliability. So in this instance it's disappointing for us as engineers to have customer impact outside the scope of what was expected. Learnings have been learned and will be integrated into future work. A good job for us is that no one notices. We also acknowledge that as we aren't one of the big players we have to differentiate ourselves in another way. For us we aim to do this through customer experience. We are very open to feedback and suggestions and definitely want to know your use cases so we can continue to improve things for you.