| 12:34 am on Jan 30, 2008 (gmt 0)|
| 1:12 am on Jan 30, 2008 (gmt 0)|
Yes. Their certificate expired, or someone pulled a practical joke thinking they were about to get laid off.
Other theory: No one has been monitoring the Publisher web app.
| 4:50 am on Jan 30, 2008 (gmt 0)|
Yes, I was having the same problem today.
| 5:38 am on Jan 30, 2008 (gmt 0)|
Still seeing it ;)
| 4:14 pm on Jan 30, 2008 (gmt 0)|
Yes, this is causing me problems. I have an automatic script that checks the balance throughout the day. Won't accept the expired certificate! Argg.
PS It always amazes me that large multi-$ companies let things like this happen. Who's running the show?
| 5:51 pm on Jan 30, 2008 (gmt 0)|
Just read in the news that Y! is laying off 1,000 employees. An expired certificate is probably the least of their worries now.
| 6:17 pm on Jan 30, 2008 (gmt 0)|
Poor Yahoo worker lets the certificate expire, next day loses their job.
| 11:17 pm on Jan 31, 2008 (gmt 0)|
Glad to see others were having an issue. I was afraid that it was on my end or getting spoofed.
| 3:34 pm on Feb 1, 2008 (gmt 0)|
It's all fixed now!