We are aware that some leased line circuits in the midlands and north of the country are currently down. A network issue is currently being investigated urgently and we will update shortly.
We are aware that some leased line circuits in the midlands and north of the country are currently down. A network issue is currently being investigated urgently and we will update shortly.
Swift Internet NOC 
We have 4 circuits which are affected by this issue.
The circuits affected have IP’s 178.16.238.* and 178.16.239.*
The circuits can be pinged from within the TTB network, but not from outside the TTB network, so this appears to be a TTB routing issue.
TTB are investigating.
Sorry for the delay in getting this issue resolved. The issue is with the TTB IOC Team and has now been escalated to management level.
Update from TTB. The job has been escalated to the TTB IP access team.
Update from TTB.
This is not a simple config issue, and is currently under investigation by our IP access team, who would have carried out any changes overnight, we are not seeing anything which should have affecting the routing of that range. But we will continue to investigate until it is resolved.
Regards
Assurance Escalation Manager
TTB have escalated the issue to the head of assurance and the managers for the IOC and IP Access teams to expedite
We are pressing TTB for an update.
The circuits affected appear to be back online, although we do not yet have official confirmation that the issue is resolved.
This issue is resolved. Further investigations between one of the senior TTB engineers and an engineer in TTB’s IOC managed to link the issue to planned works happening around the time (CRQ000000101125 – “Migrate and enable layer2/3 routing for core services on new-core01.thw”).
They called out the on-call INE to investigate. He advised that when upgrading core devices in THW, they did not include the route on the new router.
He has resolved this and has tested, confirming the route is now visible externally.