(21:16 UTC — Feb 19) Resolved – This incident has been resolved.
(19:16 UTC — Feb 19) Identified – We’ve identified the full issue is relating to how the new server network was reworked. The services requiring these databases failed to connect due to slight hostname changes. Most services have been restored.
(18:35 UTC — Feb 19) Investigating – We’re aware of some services unable to connect to the database. Some services may be unavailable. We’re currently investigating this issue.