Comment by cube00

> When Melbourne NTP was connected to the GPS card a ‘Network at Risk’ ticket should have been raised to find the real root cause of the frequent loss of the Sydney source and restore the NTP server back the intended design but this did not happen.

> At the time of the October 2025 incident, the personnel involved did not recognize the meaning of Melbourne NTP at stratum 5; that looping was already occurring in mobile core timing when an intended NTP stratum 3 server was able to become a client of one (or more) of the clients and that a circular loop was established when the stratum 2 source was lost. This anomaly was observed but not noted and no problem ticket was created for further investigation.

Two opportunities to raise tickets and nothing was raised.