Probably your BOINC client cached wrong server IP

try to restart BOINC client

Project communication failed: attempting access to reference site. Access to reference site succeeded - project servers may be temporarily down.

This can mean one of a few things:
a) The project server is down. Nothing you can do about it, except wait until it’s back up. If the project’s website is available for browsing, check the front-page news or message boards for information about outages.
b) The project server is up, but your internet connection isn’t reaching it. This is called a “black hole server”, where the line you’re following goes into a server node on the Internet and doesn't come out, usually because the node is down. Updating to a newer version of BOINC might help, especially if you’re still using v4.x or 5.4.x. Quitting and relaunching BOINC may refresh its routing information; failing that, try rebooting the computer.
c) The client is being blocked by a firewall or proxy, one that does allow pings through on port 80, but not much else by way of communication. Make sure BOINC has permission to go through the firewall and, if you’re behind a proxy, that BOINC is set up to use the correct proxy address.

The reference site that BOINC calls upon is www.google.com. Why Google? Because Google is always up. So if BOINC finds that it can reach Google but not the project, it’s not the client’s fault and the Internet connection itself is OK.

http://boincfaq.mundayweb.com/index.php?view=288&language=1

I now have over 100 work units unable to upload and now some are expiring. Since this started last Friday I'm still not sure if this is on my end or if it's part of the SSL thing on WCGs end. Frustrating

Nope, still can't upload. So what are the chances we both having issues at the same time?
I got the firewall dude combing through the logs trying to see if it's on our side.
Will know more tomorrow. *sigh*