rucsoundings.noaa.gov down - what systems are affected?

[bpcw0001]

Hi.

I tried to do a FPLN wind update, but the request never came back.

In the logs, I can find:

2023-10-12 20:38:28 CL650[gps4000s.c:2979]: EGNOS data download successful
2023-10-12 20:38:33 CL650[gps4000s.c:2940]: WAAS data download successful
2023-10-12 20:41:23 CL650[cmu_subsys_comm_mgr.c:494]: DL[https://rucsoundings.noaa.gov/get_soundings.cgi?start=latest&data_source=GFS&airport=51.9,0.2&] SENT -> FAILED (code 502)
2023-10-12 20:43:34 CL650[gps4000s.c:2940]: WAAS data download successful
2023-10-12 20:46:10 CL650[cmu_subsys_comm_mgr.c:494]: DL[https://rucsoundings.noaa.gov/get_soundings.cgi?start=latest&data_source=GFS&airport=51.9,0.2&] SENT -> FAILED (code 502)
2023-10-12 20:46:46 CL650[cmu_subsys_comm_mgr.c:494]: DL[https://rucsoundings.noaa.gov/get_soundings.cgi?start=latest&data_source=GFS&airport=51.9,0.2&] SENT -> FAILED (code 502)
2023-10-12 20:48:35 CL650[gps4000s.c:2940]: WAAS data download successful
2023-10-12 20:53:29 CL650[gps4000s.c:2979]: EGNOS data download successful
2023-10-12 20:53:36 CL650[gps4000s.c:2940]: WAAS data download successful

Is rucsoundings.noaa.gov the culprit here? If yes, what other Challenger systems are affected by this?

Is there any other way to quickly load wind data into the FMS (e. g. from Simbrief data), other than using the Simbrief wind data and type them in manually at each waypoint?
For shorter routes, I can go with average winds instead, but for longer routes, this becomes more critical.

Edited October 13, 2023 by bpcw0001

[Pils]

2 hours ago, bpcw0001 said:

Is rucsoundings.noaa.gov the culprit here?

Yes, US government websites are not always the most reliable.

2 hours ago, bpcw0001 said:

If yes, what other Challenger systems are affected by this?

In XP 12, I think only wind uplink.

2 hours ago, bpcw0001 said:

Is there any other way to quickly load wind data into the FMS (e. g. from Simbrief data), other than using the Simbrief wind data and type them in manually at each waypoint?

No. You’ll just have to wait for NOAA to fix their server.