this post was submitted on 10 Jul 2026
22 points (100.0% liked)

Australia

5087 readers
102 users here now

A place to discuss Australia and important Australian issues.

Before you post:

If you're posting anything related to:

If you're posting Australian News (not opinion or discussion pieces) post it to Australian News

Rules

This community is run under the rules of aussie.zone. In addition to those rules:

Banner Photo

Congratulations to @Tau@aussie.zone who had the most upvoted submission to our banner photo competition

Recommended and Related Communities

Be sure to check out and subscribe to our related communities on aussie.zone:

Plus other communities for sport and major cities.

https://aussie.zone/communities

Moderation

Since Kbin doesn't show Lemmy Moderators, I'll list them here. Also note that Kbin does not distinguish moderator comments.

Additionally, we have our instance admins: @lodion@aussie.zone and @Nath@aussie.zone

founded 3 years ago
MODERATORS
top 4 comments
sorted by: hot top controversial new old
[–] pHr34kY@lemmy.world 12 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

The significance of the date was that the system used a week counter up to 1,023 weeks, and the default date went back 19.6 years – as with the Telstra issue.

This is a very well documented thing that anyone running a time server should be well aware of.

https://en.wikipedia.org/wiki/GPS_week_number_rollover

What's strange is that the last rollover was in 2019. How did it go this long before failing?

In 2006, the government changed the daylight saving start date to work better during the Commonwealth Games. Telstra misses the memo, and the clock on every phone in Victoria (and possibly NSW) was out by an hour. Their solution? Wait a week unti DST lined up with their unpatched system.

Telstra must really, really hate preventative maintenance work.

[–] SteveTech@aussie.zone 4 points 2 weeks ago* (last edited 2 weeks ago)

What's strange is that the last rollover was in 2019. How did it go this long before failing?

It probably wasn't the week counter rolling over, but rather it forgetting that it had rolled over in 2019.

They previously said this was caused by a software update, so I guess that update may have reset that rollover counter.

[–] timmytbt@sh.itjust.works 2 points 2 weeks ago

Not sorry enough tbh

[–] Salvo@aussie.zone 1 points 2 weeks ago

Jeff Gerling had been researching and experimenting with time servers recently. He has a brief explanation on the best theory on what happened.

https://youtu.be/1T9xQy-dsQo