I just got this from John at NWS Network Control (NCO):"There was a lot of chatter about this issue, and the most I got out of it was the following:"eventually we found that a routing protocol had stopped running on the GOES-R end of the traffic flow before it hits NWAVE. Once that protocol was brought up, the traffic started flowing again."How it happened, in order to keep it from re-occurring again is the current focus.Sorry I don't have more info.John"So...networking issues. He also doesn't know why they went to the backup uplink this morning. they are now having issues with the main uplink.Just another day at the NWS…Gilbert SebensteAllisonHouse, LLCOn Jul 20, 2023, at 12:01 PM, Gilbert Sebenste <address@hidden> wrote:I have confirmed that they went to the backup uplink this morning. I am attempting to find the root cause of the issue with their main uplink.GilbertOn Jul 20, 2023, at 10:04 AM, Gilbert Sebenste <address@hidden> wrote:It looks like they went over to the backup uplink at 13:15Z. That uplink always has the strongest signal and best carrier-to-noise. The signal jumped another 1 dB or so at that time.GilbertOn Jul 19, 2023, at 9:37 AM, Gilbert Sebenste <address@hidden> wrote:I just called NCO again. due to technical difficulties, a ticket was not generated last night, but one is being generated right now. I also had them add that we are still down 50% (roughly 3 dB) on the carrier to noise.GilbertOn Jul 19, 2023, at 8:54 AM, Weber, Jim <address@hidden> wrote:So it looks like on that graph that Stonie sent out it never really recovered completely. I see my signal is down roughly 2.5-3dB compared to the “normal” average I get. Are others seeing the same?
Jim Weber
Certified Broadcast Meteorologist
FOX 13 News
WTVT - TV
3213 West Kennedy Blvd.
Tampa, Florida 33609
Phone 813-870-9657
<image001.jpg>
From: Gilbert Sebenste <address@hidden>
Sent: Tuesday, July 18, 2023 11:31 PM
To: Mike Zuranski <address@hidden>
Cc: address@hidden; address@hidden; address@hidden; address@hidden; address@hidden; address@hidden; address@hidden; address@hidden; address@hidden; Weber, Jim <address@hidden>; address@hidden; address@hidden; address@hidden; address@hidden
Subject: Re: 20230718: latest 7 day summary NOAAPort Gap stats
I just called the NWS Network Control of Operations (NCO).
They were absolutely shocked when I showed them what happened today and what's happening right now. They said nobody called in about it and nobody at the NCF or the NCO noticed this. I'm literally the first person who saw it this afternoon. And I figured that something this bad would be noticed immediately. And the guy at NCO said "yes, I thought we would've noticed that too!".
I can't tell you how frustrated I am right now...
Gilbert
On Jul 18, 2023, at 9:17 PM, Mike Zuranski <address@hidden> wrote:
Evening Gilbert,
On Tue, Jul 18, 2023 at 8:38 PM Tom Yoksas <address@hidden> wrote:
Hi Gilbert,
On 7/18/23 18:41, Gilbert Sebenste wrote:
> Today, it's College Of DuPage, a cellular provider turned on
> 5G at the tower 500' feet from us and wrecked our once beautiful
> signal.
Ugh!
Michael Scott: NOoooooooo!!
By the way, it looks like all of the sites reporting summary Gap
stats had high numbers of Gap messages today:
Oh my!
The fact that everyone had high numbers means we can not conclusively say you actually need that filter, there is clearly something else going on at a larger scale. While the timing of that 5G tower going live is _super_ coincidental with your issues, today's numbers for everyone is even **more** coincidental IMO.
I'm not arguing against getting a better filter if you need to, if it improves your signal it could be worth it. But I am VERY interested to see tomorrow's numbers... It's not solar interference season, (ponders) what could have caused this??
re:
> I have begun the process of getting a much better 5G filter, and
> getting it installed.
Please share with everyone CCed specifics of the 5G filter you
go with including manufacturer, cost, relevant specs, and ordering
lead time.
Seconded, please and thank you!
Best,
-Mike
Mike Zuranski
Data Engineer II
Unidata Program Center
University Corporation for Atmospheric Research
This message and its attachments may contain legally privileged or confidential information. It is intended solely for the named addressee(s). If you are not an addressee indicated in this message (or responsible for delivery of the message to an addressee), you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments that does not relate to the official business of Fox Corporation, or its subsidiaries must be taken not to have been sent or endorsed by any of them. No representation is made that this email or its attachments are without defect.