GLONASS internally runs on Moscow wall clock time, which is UTC+3. It has leap seconds. Dates are specified as day numbers starting from 1 & go up to 1461, within a four-year plan. The GLONASS n4 year number went from 6 to 7 on the 31st:https://twitter.com/GalileoSats/status/1213031666026983424 …
-
-
Show this thread
-
And the day number NT from 1461 to 1. Soviet mathematicians apparently counted from 1:https://twitter.com/GalileoSats/status/1213032041996005376 …
Show this thread -
And finally link to some outage discussions: https://mailman.nanog.org/pipermail/nanog/2019-December/105053.html … & https://lists.dns-oarc.net/pipermail/dns-operations/2020-January/019560.html …
Show this thread -
Oh and to clarify, this was not a GLONASS problem but a receiver firmware problem.
Show this thread -
And finally finally some problems appear to have started earlier than the actual rollover so perhaps it is not as simple as this.
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.