Resolved

As of TIME_STAMP UTC, the issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

Began at: