Kong incident

Degradation in ME region impacting DevPortal, Debugger, and node listing.

Critical Resolved View vendor source →

Kong experienced a critical incident on March 18, 2026 affecting Kong Konnect Cloud, lasting 31m. The incident has been resolved; the full update timeline is below.

Started
Mar 18, 2026, 08:13 PM UTC
Resolved
Mar 18, 2026, 08:45 PM UTC
Duration
31m
Detected by Pingoru
Mar 18, 2026, 08:13 PM UTC

Affected components

Kong Konnect Cloud

Update timeline

  1. investigating Mar 18, 2026, 08:13 PM UTC

    We are investigating possible degradation in the ME region that may be impacting Debugger and node listing.

  2. identified Mar 18, 2026, 08:45 PM UTC

    We have identified the issue and are taking action to remove the affected instance.

  3. monitoring Mar 18, 2026, 08:46 PM UTC

    We have corrected the issue and are actively monitoring the situation.

  4. resolved Mar 19, 2026, 07:38 PM UTC

    This incident has been resolved.