Thread

1. scriptsmith · 1789701187 · focus · HN ↗

   Lots of bloviating AI-prose. Here's the original report:

   <a href="https:&#x2F;&#x2F;www.telstra.com.au&#x2F;exchange&#x2F;what-we-ve-learned-from-the-external-investigation-of-our-july-o" rel="nofollow">https:&#x2F;&#x2F;www.telstra.com.au&#x2F;exchange&#x2F;what-we-ve-learned-from-...

   <a href="https:&#x2F;&#x2F;www.telstra.com.au&#x2F;content&#x2F;dam&#x2F;tcom&#x2F;dynamic-media-projects&#x2F;exchange&#x2F;TAPFindingsforTelstraOutage.pdf" rel="nofollow">https:&#x2F;&#x2F;www.telstra.com.au&#x2F;content&#x2F;dam&#x2F;tcom&#x2F;dynamic-media-pr...

   1. anitil · 1789704267 · focus · HN ↗

      They&#x27;re pretty readable, I recommend that second one (though it leaves some questions I have unanswered). It&#x27;s a good example of how latent issues with a large system can go unrecognised for a long time before a seeming unrelated change can trigger a cascading failure

      1. skissane · 1789710511 · focus · HN ↗

         One thing it doesn&#x27;t make clear – the GPS card only supported the original L1 signal, which is what causes the GPS week rollover issue. The newer L2C signal has a much longer rollover period (157 years vs 19.6 years), which means no rollover until next century. If the GPS card had supported the newer L2C signal, then likely this would not have happened even if the other misconfigurations had still occurred.

Unofficial Hacker News client; not affiliated with Y Combinator.