GPS Sync Outage

[lists at packetflux.com (Forrest Christian (List Account))]

One of my hats is to design/manufacture/sell GPS third party timing
receivers for Cambium Radios.    It seems like something happened around
2PM MST today which caused (at a minimum) certain Globaltop/Sierra Wireless
GPS modules to quit receiving signals from the GPS constellations.
 Because these modules are pretty well respected as far as the quality of
the timing signal (normally) and relative low cost, they tend to be
integrated in a lot of devices, including my products, the official Cambium
Products, and I understand the gear from other manufacturers.

So far, a power cycle/reset of the GPS module seems to solve the problem.

I haven't had enough time to process all of the data I have to know more
details yet, but I can confirm the widespread nature of this event.

On Tue, Dec 31, 2019 at 5:39 PM Jared Mauch <jared at puck.nether.net> wrote:

>
>
> > On Dec 31, 2019, at 5:32 PM, Andreas Ott <andreas at naund.org> wrote:
> >
> > On Tue, Dec 31, 2019 at 05:08:17PM -0500, Matt Hoppes wrote:
> >> Is anyone else seeing GPS timing source outages across the U. S. In the
> last two hours?
> >
> > On what hardware/firmware are you seeing this?
> >
> > Nothing unusual in the Bay Area so far, in other words "All Quiet on the
> > Western Front". I am seeing receivers synced to at least 6 or 7 sats. Two
> > different locations; one Garmin 18LVC, one uBlox 6M hardware. There is
> > also no chatter about it on the time-nuts list where I would suspect to
> > see it first.
>
> Thereâ??s a fair amount of hardware that uses GPS sync for wireless and Iâ??m
> guessing this is likely a vendor bug w/ UBNT hardware, but itâ??s also good
> to know if itâ??s broader than that.
>
> I know thereâ??s some interesting java bugs related to the switchover for
> 2020 as well, eg:
>
> https://twitter.com/NmVAson/status/1207820284268597249
>
> I know of at least once place that was hit by this.
>
> - Jared
>
>

-- 
- Forrest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20191231/4f878d0d/attachment.html>