This incident has been resolved.
The incident was caused by a configuration issue introduced during a scheduled update, which resulted in the service becoming unavailable.
·
