Kong Status Page

May 26, 2026 · resolved May 26

The incident has been resolved. The cause is still being investigated and will be posted when available.

May 20, 2026 · resolved May 20

This incident has been resolved.

May 19, 2026 · resolved May 19

The control plane in US continues to remain operational. The incident has been resolved.

May 11, 2026 · resolved May 11

The issue affecting Analytics in the AU (ap-southeast-2) region has been resolved. The problem was caused by an incorrect node configuration, which has now been corrected and deployed. All services have recovered, and analytics data is returning as expected. No other regions were impacted.

May 8, 2026 · resolved May 8

Kong proactively deployed an updated license to control planes ahead of an upcoming expiration to avoid any customer disruption. As a side effect of this update, data plane nodes were incorrectly displayed as out-of-sync in the Konnect UI. The data planes themselves continued operating normally with a valid configuration throughout. The team performed a progressive rollout that triggered a full configuration sync, which cleared the inaccurate status. All nodes returned to an in-sync state shortly after. No traffic was impacted at any point. Data planes continued routing requests normally and would receive configuration updates. The only customer-visible symptom was the inaccurate out-of-sync indicator in the UI. The full configuration sync step has been added to the standard runbook for license updates, so future license rotations will not produce this false positive. Engineering is also improving the out-of-sync detection logic to reduce false positives going forward.