Resolved on August 27, 2025.
Today, from 11:08am ET to 11:26am ET, a misconfiguration in our feature-flagging tool caused all customer apps to default to the Next-Gen experience only. During this time, attempts to access Classic URLs resulted in errors. At 11:27am ET, the issue was fully resolved, and all access has returned to normal: - Customers with Classic-only access now have Classic-only access restored. - Customers with Next-Gen-only access now have Next-Gen-only access restored. - Customers with both Next-Gen and Classic access now have both restored. We apologize for the disruption and appreciate your patience.
Update timeline
- resolved Aug 27, 2025, 03:58 PM UTC
Today, from 11:08am ET to 11:26am ET, a misconfiguration in our feature-flagging tool caused all customer apps to default to the Next-Gen experience only. During this time, attempts to access Classic URLs resulted in errors. At 11:27am ET, the issue was fully resolved, and all access has returned to normal: - Customers with Classic-only access now have Classic-only access restored. - Customers with Next-Gen-only access now have Next-Gen-only access restored. - Customers with both Next-Gen and Classic access now have both restored. We apologize for the disruption and appreciate your patience.
Your product runs on more than Knack
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services