Affected
Operational from 10:30 PM to 10:30 PM
This incident has been identified and resolved. The issue began August 14th at 4:30pm MT and was resolved at 7:45am MT on August 15th