Kong incident
Authentication issue in IN Region for Konnect Control Plane
Resolved after 38 minutes, on July 2, 2026.
The Konnect control plane in the India was incorrectly rejecting all user tokens between 08:30am UTC to 9:08am UTC. A misconfiguration of the token validation URL was deployed, noticed by our monitoring, and rolled back. No dataplane traffic or proxy behavior would have been impacted. Impacts were: - API calls, including from tools like DecK and Terraform would receive 401 responses - Users on the Konnect UI may have been logged out if the UI made any control plane calls that resulted in a 401 response
Update timeline
- resolved Jul 02, 2026, 09:51 AM UTC
The Konnect control plane in the India was incorrectly rejecting all user tokens between 08:30am UTC to 9:08am UTC. A misconfiguration of the token validation URL was deployed, noticed by our monitoring, and rolled back. No dataplane traffic or proxy behavior would have been impacted. Impacts were: - API calls, including from tools like DecK and Terraform would receive 401 responses - Users on the Konnect UI may have been logged out if the UI made any control plane calls that resulted in a 401 response
Your product runs on more than Kong
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