During planned maintenance on November 10, 2026 in the Konnect US region, a bug in AI Gateway versions 2.0.x, 2.1.x, and 2.2.x caused self-managed hybrid data planes to stop retrying reconnection after being briefly disconnected, leaving them unable to receive new configuration updates. Affected data planes continued serving traffic using their last known configuration but appeared disconnected in Konnect for approximately 7.3 hours. The issue was resolved by restarting affected data planes, with an upgrade to AI Gateway 2.3.0 or later recommended to prevent recurrence.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
On November 10, 2026, starting at approximately 09:20 UTC, Kong performed planned maintenance in the Konnect US region to improve platform performance and scalability. During this work, data planes were briefly disconnected from Konnect and were expected to reconnect automatically.
An issue in AI Gateway versions 2.0.x, 2.1.x and 2.2.0 caused some self-managed (hybrid) data planes to stop attempting to reconnect. These data planes would have continued processing traffic using the last configuration they received, but they would not have received new configuration changes and no longer appeared as connected in Konnect.
Dedicated Cloud Gateways and data planes running AI Gateway 2.3.0 or later are not affected.
We apologise for any inconvenience this may have caused.
Recommended Action:
To check whether you are affected, review the data plane nodes for your AI Gateway control planes in Konnect. If any nodes you expect to see are missing or shown as disconnected, they may be affected by this issue.
To resolve the issue immediately, please restart the affected data planes. They will reconnect to Konnect and receive the latest configuration.
To prevent this issue from recurring, we also recommend upgrading to AI Gateway 2.3.0 or later, which includes a fix.
If you have any questions or need assistance with these steps, please contact Kong Support.
We are continuing to monitor for any further issues.
Customers running 2.0.x, 2.1.x and 2.2.x dataplanes may see logs indicating they have disconnected from Konnect and have stopped attempting to retry. These dataplanes must be restarted in order to restart the connection attempts.
This is caused by reconnection logic which was changed in 2.3, that will cause the DP to give up retrying after some connection attempts. When Konnect performed a routine maintenance and connections dropped briefly, some of these 2.0-2.2 dataplane versions may have stopped attempting to reconnect.
Restarting and disconnected dataplanes should allow the reconnection.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with