It would seem that your connection pool isn't clearing out dead/idle connections, or something spawned to many concurrent connections and the limit was reached.

Wasn't any changes to the app yesterday or something was disabled which used to clear out the connection pool or restart IIS, or something along them lines.

A new process which occurs in the app at around the time of the errors? which needs multiple connections?