We've identified the two-fold cause of bad database URLs and bad configuration setting. Both have been rectified and the service is operating normally.
Posted Aug 16, 2017 - 18:46 PDT
Investigating
Currently the Participate flow is broken due to an internal server error, possibly caused by a deploy configuration change. Currently investigating the source of the error.