From CWOP News Page: (http://www.wxqa.com/news.html)
“Jan 6, 2007 - The Tier 2 APRS-IS server operators have apparently decided to discontinue their support of CWOP. This has affected the APRS-IS server traffic. If this is affecting your data flow, then you should consider changing to the 5th, 6th, or 7th possibility listed under item # 2 here.”
Sounds like someone got Ticked off from the flame war that has been going on in the Weather Data Quality mailing list 
-Bob
Message: 6
Date: Sat, 06 Jan 2007 23:15:29 +0000 (GMT)
From: [email protected]
Subject: [wxqc] CWOP server status
To: [email protected]
Message-ID: [email protected]
Content-Type: text/plain; charset=us-ascii
As of a few hours ago, the Tier 2 operators abruptly withdrew support
for CWOP traffic through their servers. We’re sorry for any
inconvenience this causes CWOP members, but you will have to change the
server designation in your local software. More details at
http://www.wxqa.com/news.html
Russ
Message: 7
Date: Sat, 6 Jan 2007 18:43:56 EST
From: [email protected]
Subject: [wxqc] No Data
To: [email protected], [email protected],
[email protected], [email protected]
Message-ID: [email protected]
Content-Type: text/plain; charset=“iso-8859-1”
Warning: No data received for more than 30 minutes.
Please be certain your weather client is connected to the core servers
before asking for assistance.
To do this, change your upload server to “rotate.aprs.net” on port 14580.
Information on how to do this is in item 1 on this page
(http://www.wxqa.com/activecwd.html) .
CWOP CW Packet Checking
so… the saga continues… in the ftp log file, after changing to the suggested aprs tier 3 I get this
there are 1 more things to do
Aprs data sending now…
11004: [11004] Valid name, no data record (check DNS setup)
APRS Connecting to: rotate.aprs.net
11004:
APRS timer time out…
Finshed email agenda
Finished email agenda, no ftp items to do…
Doing abort procedure/program close…
Will stay connected.
And I just got this email from the mailing list…
There were two programs running on the four tier two servers that courted CWOP data. The port 23 programs were used for CWOP data, these have been turned off on three of the four machines. Whether the fourth will follow that lead remains to be seen. None of those servers turned off their APRS users on other ports, just the CWOP users on port 23.The core servers absorbed a third of the CWOP users immediately
without any strain and are fully able to to handle the full load as
CWOP users change their configuration to feed directly to the core.Steve K4HG
FWIW, since I switched servers my data has been flowing w/o problems…
-Bob
I changed my server to rotate.aprs.net at 14580 for the port and I am not getting any data down the pike. Hold the phone… I think it is now working.
Well, this sucks… two loses in one day. Locally Sinclair communications pulled FOX with our local cable company … Mediacom. Now I will never see if Bart Simpson successfully reaches puberty and on top the APRS thing.
Oh… and the local Jeep dealership went out of business and moved out to BF Egypt… Poop.
Funny…
I just got this on the mailing list…
If 14580 isn't working for you, it may be a firewall problem. Port 23 is fine as well.Steve K4HG
-Bob
What are the settings for Weather display that I need to correct.
So far I have left
other HUB server to use: ahubwest.net :default
use this hub server instead: not selected
server rotation setup
server to rotate to: rotate.aprs.net port 14580
2nd server to rotate to: indiana.aprs2.net port 23 :default
are these the correct settings
David
What good is that, the steering wheel is on the wrong side of the car. 
an option or a new weather station. hmmmm choices, choices, choices…
Do they still make those?
Just got this on the mailing list, to make things more interesting…
> There were two programs running on the four tier two servers that > courted CWOP data. The port 23 programs were used for CWOP data, > these have been turned off on three of the four machines. Whether the > fourth will follow that lead remains to be seen. None of those > servers turned off their APRS users on other ports, just the CWOP > users on port 23.The fourth will be gone later this evening. In place it will accept CWOP
connects on port 14580, which is compatible with the 3 Main Core servers.This list of servers will be available soon.
Dick, KB7ZVA
APRSWest
-Bob
Yes have one and love It
Coyote
You can see the status of the servers here:
http://www.wxqa.com/checkservers.html
Notice the Tier 2 servers stats…
Looks like Arizona decided to come back online.
Just got this mailing from the QC mailing list…
[quote]From: Russ Chadwick [email protected]
What you describe below is
just a note for users of WD’s free aprs version:
you can change the server to use, i.e to the rotate server, but not the port (i will have to add that), but port 23 will still work with the rotate server, yes?
also, though, without changing anything, my data is now working (when it was not before)… but its been a bit corrupted at times…?
What I currently have (v. 1.1.6) as the default for VPLive is to send first to rotate.aprs.net port 14580 (the core rotation). If that fails, it sends to rotate.aprs.net port 23 (this covers users whose firewalls block high numbered ports). If that fails, then it tries a few of the tier 2 servers on port 14580.
Port 23 on the core servers works, but it consumes excess bandwidth, so 14580 is preferred.
The rotate.aprs.net works well. They have their DNS record TTL (time to live) set at 1 minute, so each time your software sends a CWOP packet, it should hit the DNS server and get a fresh IP address.
I may in the future, especially after Russ’ recent post, try the core rotation first, and then try several core servers specifically if the one returned by the rotation happens to be down. My trust for the tier 2 servers has been negatively impacted by the past few day’s events.