Kong Outage History

This incident has been resolved. The Konnect UI has recovered, and users should no longer experience application errors when accessing product areas in Konnect. The issue was only affecting a very small set of Konnect users. We will continue to monitor the service to ensure ongoing stability.

Customers were unable to access the Konnect UI. Upon loading the interface, an error message reading "Could not fetch user session data - Please reload the page to try again" was displayed, preventing access to the platform. This issue affected all regions globally. Control plane configurations and data plane payloads using direct API access were not impacted during this time.

This incident has been resolved.

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

This incident has been resolved.

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

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.

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.

This incident has been resolved.

Customers running 3.13 and below who use the OIDC plugin with `tls_client_auth_ssl_verify` unset would have seen this value change to `false` if they updated the config after the rollback of new defaults following the 3.14 release. The rollback incorrectly flipped the oidc plugin tls_client_auth_ssl_verify to false as a default, which was not one of the items recently switched to default true and has instead been defaulted true for some time. We have rolled out a fix to prod to change this default back to true. Updates to the OIDC plugin should once again keep this value set to true if not specifically defined.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

From 15:25z to 15:35z, the Konnect Control Plane saw an increase in dropped connections and re-connections in the US region from connected dataplanes. Dataplanes automatically re-connect when a connection is dropped, so there should be no observed impact, but customers may have noticed an increase in log volume if re-connections were occurring during this window.

The issue has been resolved. Delivery is now operating as expected.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.