Kong Status
Real-time updates of Kong issues and outages
Kong status is Operational
Kong Konnect Cloud
Lior Grossman
Maker of StatusSight
I built StatusSight. Here's what I'm building next with AI.
In Lior Builds, my free newsletter, I share one story from a product I built with AI, plus short notes on the tools and models worth using: what worked, what did not, and the numbers behind it. Every week or two.
Active Incidents
No active incidents
Recently Resolved Incidents
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.
Kong Outage Survival Guide
You're checking on Kong - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Kong Components
Kong Konnect Cloud
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.