Final Update: Friday, January 19th 2018 13:12 UTC
The issue has been mitigated.
• We performed a service update earlier today which we suspected was related to the Access Token error.
• We have since rolled back the update, which has resolved the issue.
We are continuing to investigate root cause.
Initial Update: Friday, January 19th 2018 11:22 UTC
We're investigating an issue where some Extensions may be failing with an Access Token error in all Regions.
Users may recieve a 401 response.
- Next Update: Before Friday, January 19th 2018 12:22 UTC