I am not sure that any of you have run into this problem, but we did in late December. Florida migrated PRISM to SQL 2008 R2 in July 2013. In late December of 2013, our users started receiving a "503 - Service Unavailable" error. We were fortunate that one of our support staff remembered something about this error message and IIS 7. We have to set the "Load User Profile" option for the PRISM application pool to True since we use Accumail to validate our addresses. We also use a specific Identity to allow the reports to work from the application. We had our Identity defined as domain\userid. We have been unable to determine why this started to have problems, but we changed the Identity to be userid@domain and it fixed the issue.
Here is a link to the Microsoft blog that explains the issue.